[SOLVED] Not possible to install monthly CU Windows updates on Server 2019

Freggel

Member
Joined
Oct 11, 2024
Posts
8
Hi,

I have a Windows update problem with a Windows 2019 Server (Version 10.0.17763.1879). It's a virtual machine running on a VMWare ESXi 7 host. The last version of vmware tools are installed. All of our other servers (2016/2019/2022 on VMware ESXi or Azure VM) don't have these problems.

The monthly Windows CU updates are getting installed, but after the reboot while finalizing the update, the following message appears: "We couldn't complete the updates. Undoing changes.". The update is gets uninstalled again.

It seems there is a lot of "Windows Update troubleshooting knowledge on this forum. So i try to ask some help here:
  1. SFC scan: No errors.
  2. DISM. After DISM reaches 100% it gives error message 0x800f081f. It can be network related. The server is behind a corporate firewall.
    If i mount a Server 2019 ISO and try "DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:E:\Sources\Install.wim:1 /LimitAcces" I get the same error message.
  3. Component.txt is attached
  4. CBS.zip is attached.



    Hopefully someone can help me. Many thanks in advance.
 

Attachments

Rich (BB code):
2024-10-17 00:28:18, Info                  CBS    Failed installing driver updates [HRESULT = 0x8007000d - ERROR_INVALID_DATA]

Hi and welcome to Sysnative,

Upload the setupapi.dev.log file
  • Open Windows Explorer and browse to the C:\Windows\INF folder.
  • Right-click on the file setupapi.dev.log and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
657716925b62b-setup-api-dev-folder.png

  • Attach the file setupapi.dev.zip in your next reply.
 
Hi Maxstar.
Thanks for looking in to it.

I uploaded the zip file. FYI: I removed VMWare tools recently and installed it again today.
The update problem persisted after removing VMWare tools.
 

Attachments

Hi,

VMWare Tools is not the issue indeed, some registry keys are corrupted.

Export registry key as hive file.
  • Open the Start menu of Windows and type CMD.
  • When you see Command Prompt on the list, select the option Run as administrator.
  • Copy and paste the following command into the command prompt and press enter.
Code:
reg save "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services" "%userprofile%\Desktop\Services.hiv"
  • Once done, a file will appear on your desktop, called Services.hiv.
  • ZIP this file and attach it to your next reply.
 
Download
6530fbb0f4101-56f31e53c97da-SFCFix.PNG
SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
650ef5dbdfd06-62151e1bebac4-SFCFix-Txt-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.

Afterwards attempt to update. If it fails attach a new copy of the CBS logs and a copy of the Setupapi.dev.log.
 

Attachments

It seems like the updates get installed this time.
But the reboots with the running percentages go very slow. Much slower than other servers with the same problem. It's at 100% right now (for 25 minutes); and it took a long time to get tot 100%. I'll have to go now. Tomorrow i can check te status again.

SFCfix succeeded. I checked the log.
If we "broke" the server it's no problem. I cloned the VM to an isolated network (internet only) and applied the fix to the clone. I'm not allowed to disrupt the production server outside of maintenance hours.

Can you shortly explain the registery change from the SFCFix?

Thank you, and i'll get back tomorrow with the result of the update.
 
It's at 100% right now (for 25 minutes); and it took a long time to get tot 100%.
This should be normal when the update process is running a cleanup task, but I will see the result tomorrow... (y)

an you shortly explain the registery change from the SFCFix?
That's quite difficult to explain in a few words, also because there's no general fix for such problems and differ in each case!
 
Unfortunatly. 18 hours later the update proces is still at 100%.
I rebooted (reset) the server already, but it continues with the "Working on updates, 100% complete-screen".
Any ideas before i restore the backup?
 

Attachments

  • Schermafbeelding 2024-10-25 080051.webp
    Schermafbeelding 2024-10-25 080051.webp
    7.8 KB · Views: 1
Hi,

If the update resumed after a forced reboot, I would just wait and see if it will complete successfully this time.
 
Maxstar!!. Your are amazing.
It took al long time (even after the reset). But the server is alive again. And t looks like it is ok again.

I'll ask a key user to test check application + database.
If all is OK, we are going to plan a maintenance window to fix the real server.

I saw the changes in the registry
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\pciide
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\pciide\StartOverride
But it isn't exactly clear what it is for.

If you have a link to some reading material which explains this i would be gratefull. I try to understand wat we changed.

Many thanks. I really appreciate your effort. It saved me a lot of work.
 
Hi,

That's great news, glad to hear the update installed successfully.

I've replaced that key with a known good copy, this because the following value was missing.
Code:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\pciide
    Owners    REG_MULTI_SZ    mshdc.inf
 
You're welcome. And marking a thread as solved is not a specific mod-task, each user can mark their threads as solved.. (y)
 
Back
Top