Server 2016 Update Issues

[dbdan22]

Hi,

Windows Server 2016 Version 1607 (OS Build 14393.4283)
Physical machine with GUI
Intel Xeon E3-1240 v6 Kaby Lake

Been having various update and other related problems that come and go.

Right now it says Windows is up to date, and
it passes sfc /scannow

But - - -

- When I shut down or reboot, it goes into a "Getting Windows ready, don't turn off your computer" loop. Doesn't mention anything about updates, mind you. Just "Getting Windows ready". Once I let it run to completion, but then it happened again on the next reboot, and I had to get the server back up so I hit the power button. Boots up OK, everything seems to be working, but the problem remains.

- Dism gets an error:

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[===========================92.2%=====================     ]
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>

CBS and DISM logs are here:
Server2016LOGS.zip

Please help.

Thanks in advance.

 

[dbdan22]

Ran it again,

DISM fails again at the same spot - 92.2%.

C:\Windows\System32>sfc /scannow && dism /online /cleanup-image /checkhealth

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

The component store is repairable.
The operation completed successfully.

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

[===========================92.2%=====================     ]
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

Updated cbs & dism.log:
Server2016Logs2.zip

 

[dbdan22]

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!!!

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.

 

[dbdan22]

2 months?

 

[dbdan22]

Can someone please help me?

 

[dbdan22]

Do you need me to reupload anything since it's been awhile?

 

[dbdan22]

So it's been awhile since I first posted, so I'd like to refresh this.

This is the situation:

Windows Server 2016 Version 1607 (OS Build 14393.4467)

- Not pulling in Windows Updates automatically, I have to check for updates manually. Sometimes it finds the updates, sometimes it doesn't. Hit or miss.

- Can't make up its mind whether 2021-06 Cumulative Update KB5003638 installed successfully. First it says it failed, then it says it installed successfully, without a reboot in between.

- Says "Your device is up to date". What about 2021-07 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5004238), which it isn't finding ??? That's the one with the PrintNightmare fix.

- sfcfix doesn't find anything wrong.

- sfc works but dism does not, same error as before:

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Windows\System32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

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>

Fresh copies of the CBS and DISM logs:
Server2016Logs3.zip

Can someone please help me?

Thanks in advance.

 

[dbdan22]

So as far as I can tell, these two posts also have the same DISM error.

Error: 14
Not enough storage is available to complete this operation.

- This post (April 18th)
- This post (June 2nd)

Plus there's a post on Experts Exchange about it too.

Hmmmmm..... free trial?

3 months now.

Time flies.