Every command executed on a computer takes into account a number of files and space for the code in the background to be executed. But sometimes due to various limitations or poor allocation of memory or various other reasons a computer might encounter the Not enough storage is available to process this command error on Windows 10 or Windows Server operating systems.
Not enough storage is available to process this command
The following method has proven to be effective to fix the Not enough storage is available to process this command error on Windows 10 and Windows Server:
- Using the Registry Editor.
- Delete Temporary Files.
- Use DISM.
1] Using the Registry Editor
The IRPStackSize DWORD is responsible to define the memory range allocated for the tasks and commands to be executed. We need to extend this range.
Open the Run prompt (WINKEY + R), type regedit and hit Enter when logged in with a User Account with Administrator Privileges.
Once Registry Editor opens, navigate to the following key-
Look for the DWORD named IRPStackSize.
If not found, right-click on the free space and select New > DWORD (32-bit) Value.
Name it as IRPStackSize.
Double click on it and set its Value data to be great than what was entered already. The maximum value allowed is 0xc and the range starts from 0x1.
Click on OK.
Reboot your computer for the changes to take effect.
2] Delete Temporary files
3] Use DISM
There can be chances that a third-party software could have intervened and misconfigured the System Files of your operating system. For that, you need to run the DISM commands.
If you boot into Advanced Startup Options, you can select Command Prompt directly and proceed with the steps.
Alternatively, you can get your computer into the Clean Boot State or boot with an external bootable installation media.
Open Command Prompt (Admin)and enter the following command and hit Enter:
Dism /Online /Cleanup-Image /RestoreHealth
Let this DISM command run and once done, restart your computer and try again.
If it fails maybe you need to use the /StartComponentCleanup parameter:
Dism /Online /Cleanup-Image /StartComponentCleanup
This should definitely fix the error.