# Solution for Windows admins: ERROR_NO_SYSTEM_RESOURCES error 1450 running DISM — retained record

> Retained reddit record from reddit:sysadmin.

Canonical: https://highsignal.app/data/records/a92cb4616255cf0b

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:sysadmin)  published 2026-11-03 16:07 ingested 2026-11-04 02:40

[original source ↗](https://www.reddit.com/r/sysadmin/comments/1xmx0jg/solution_for_windows_admins_error_no_system/)

## retained text



```
I had a strange problem over the weekend, and I only found [one source](https://www.sysnative.com/forums/threads/components-hive-is-like-2-gigs-like-how.43769/) that clued me in to the solution. If you're an admin in the future and you've found this post through searching, maybe this will help. This is the information that would've saved me many hours if it was all in one place.

**Problem**: An unstable Windows Server. In this case, it was Server 2016. It would just stop responding altogether. Reboots bought us time, but the problem would shortly resurface. I found nothing notable in the system event logs. This weekend, I ran `dism /online /cleanup-image /restorehealth` in preparation for running `sfc /scannow`, but the DISM command failed with `ERROR_NO_SYSTEM_RESOURCES`. The system resources were fine!

**Finding**: The components registry hive located in `C:\Windows\system32\config\` grew beyond its [2GB limit](https://learn.microsoft.com/en-us/windows/win32/sysinfo/registry-storage-space). This is strange, because there's a built-in Scheduled Task in Windows to automatically prune this hive, called [StartComponentCleanup](https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/clean-up-the-winsxs-folder?view=windows-11). I checked the task and it was in an error state: `The system cannot find the file specified. (0x80070002)`.

To fix this, I clearly had to reduce the size of the components hive. You'll find a few different methods provided by Microsoft. One way is a [hotfix and a hive migration using another machine](https://techcommunity.microsoft.com/blog/askperf/unable-to-restart-server-due-to-registry-bloat-over-2gb/375507), another involves [booting into Windows PE to try and compress the hive](https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/compress-bloated-registry), and another tells you to [check the RegistrySizeLimit value in the registry](https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/compress-bloated-registry). These solutions either didn't apply or couldn't be executed, because the server can't be offline for any extended period of time. I needed to do this live.

**Solution Part 1 - manually prune the components hive**:

* Mount the components registry hive: `reg load HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS`
* Dump the list of old updates into a text file: `reg query HKLM\COMPONENTS\DerivedData\VersionedIndex > old-updates.txt`
* Use that list to forcefully delete every single one except the last five. The command should look this: `reg delete "HKLM\COMPONENTS\DerivedData\VersionedIndex\10.0.14393.5771 (rs1_release.230213-1720)" /f.` Obviously, you replace what's in the quotes with what's in your text file dump. One at a time.
* Make sure the `Windows Modules Installer` service is stopped: `net stop trustedinstaller`
* Unmount the components hive: `reg unload HKLM\COMPONENTS`

*The components hive will still be 2GB+ though!* It needs shrinking. Sysinternals to the rescue.

**Solution Part 2 - manually consolidate the components hive**:

* Download the SysInternals tool [Registry Usage](https://learn.microsoft.com/en-us/sysinternals/downloads/ru)
* We'll use it with the -h flag on the hive, which recalculates it and then compresses it: `./ru64 -h C:\Windows\System32\Config\COMPONENTS`. This can take a long time. Trust the process.

When this completes, your components hive will be less than 2GB. It may even be cut in half to 1GB. Progress! You aren't done yet.

**Solution Part 3 - manually consolidate the components hive even more**:

* Run `dism /online /cleanup-image /restorehealth` and wait for it to complete
* Run `sfc /scannow` and wait for it to complete
* Reboot the server
* Go into Task Scheduler, browse to `\Microsoft\Windows\Servicing`, and manually start the `StartComponentCleanup` task. Wait for it to complete. You may be waiting several days. This is okay. Trust the process.
* When `StartComponentCleanup` finally finishes, reboot

Your components hive is no longer corrupt and is much smaller than 2GB. In my case, it's less than 600MB. Now you can run Windows Update successfully on your stable server. Cheers.
```



document fetched 2026-11-04 00:36 · canonical https://reddit.com/r/sysadmin/comments/1xmx0jg/solution_for_windows_admins_error_no_system
