Well this is absolutely maddening!!!!!!!!!!!!!!!!!!!!
I saw this page about DISM Error 14:
Fix Not enough storage available to process this command error on Windows 10
I tried the first suggestion: Increase IRPStackSize.
I increased it twice, once to 30 (decimal) and rebooted, and again to 40 (decimal) and rebooted.
Both times, the result was the same: error 14. Except that instead of bombing at 92.2%, now it goes to 100%, sits there for 2 to 3 minutes... and then bombs. Whoooohoo!!!
Code:
C:\Windows\System32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.14393.4169
Image Version: 10.0.14393.4169
[==========================100.0%==========================]
Error: 14
Not enough storage is available to complete this operation.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
C:\Windows\System32>
Alas I am not skilled in the ways of DISM.LOG.
So I am attaching an updated copy of DISM.LOG so you can see what it did with IRPStackSize at 30 and 40.
dism.log
Meanwhile I'm going to delete IRPStackSize and reboot to get it back to the way it was before.
So I have a question:
Since this seems to be a network issue, what if I did the DISM off a local known good source? So I have another Server 2016 system (it's really a PC with Server 2016 on it) that passes both SFC and DISM. Now when I do the DISM on the bad system in safe mode, it can't find the Source. What do I need to copy off the good system onto a flash drive to do an offline DISM on the bad system against the good source? And what is the correct /Source switch? Also I used Rufus to create a server 2016 bootable flash drive. Can I use that, and what is the correct /Source switch?
Please help. Thanks.
