[SOLVED] Windows Update Keeps Rolling Back [Server 2019]

baldy27

Member
Joined
Sep 10, 2023
Posts
14
I have 2 servers, one is 2012 R2 and consistantly rolls back after installing KB5029312

And another is Server 2019 and constantly rolls back after installing KB5029242

I have done the usual rubbish SFC scan and DISM.
 
Last edited by a moderator:
Hi and welcome to Sysnative,

Please provide the CBS logs for your Server 2019 system in this thread, you can use WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free to upload the ZIP-file with all the logfiles to share the downloadlink here.

I would suggest to start a new thread for your 2012 R2 server, just to avoid any confusion.
 
Last edited:
You have posted the CBS logs of the 2012 (6.3.9600.21111) server into this thread instead of the CBS logs of the 2016/2019 server...
 
I've changed the title for this thread so it's clear I provide fixes for your Server 2019....

Question: Do you have another server 2019 running, to look if the following directory exists...
Code:
C:\Windows\WinSxS\amd64_microsoft-windows-dhcpserverruntime_31bf3856ad364e35_10.0.17763.4492_none_7694e802695aebbe
 
Step 1. Download
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 SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-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.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Great, please attempt to update again. If it fails attach a new copy of the CBS logs.
 
Thanks. I can't do this in hours so will attempt tonight and update you tomorrow.
 
Thank you!

Patch has installed fine now.

If you dont mind, can you please advise the process of what you was looking for in logs and what fixed the issue in particular.
 
Hi,

You're welcome. Glad to hear the update installed without any issues this time.

Let's take a look at the component of which you have provided a copy:
Rich (BB code):
C:\Windows\WinSxS\amd64_microsoft-windows-dhcpserverruntime_31bf3856ad364e35_10.0.17763.4492_none_7694e802695aebbe\dhcpssvc.dll

Rich (BB code):
2023-09-27 03:38:59, Info                  CSI    000017bc Hashes for file member [l:12]'dhcpssvc.dll' do not match.
 Expected: {l:32 ml:4096 b:82f0a9ffce6b6ef9157fa553dc075fbc79a6f5485fb191d448737cc5640db061}.
 Actual: {l:32 b:61948db088f92842598829f00c8157ce70961b76a01c979be763f0b5d10ee827}.

As we can see the payload file has the wrong hash value, so I have replaced all the payload files which have the expected hash value...
 
Brilliant, so i can use the same files to do this in the future and and all hashes will be rewritten to the correct ones.
Would this just be for dhcpssvc.dll or all values in the amd64 folder?
 
Most of these servers are also in place upgrades from 2012 to 2019, could this of caused the issue
 
Yes, you can use files from a healthy server as replacement, see also this public tutorial on how to fix such kind of issues.
The hash value in the example above is just for dhcpssvc.dll.

No this was not an upgrade issue, it was a hydration issue.
Rich (BB code):
2023-09-27 03:38:59, Error                 CSI    000017b7 (F) Hydration failed with original error NTSTATUS_FROM_WIN32(ERROR_INVALID_DATA) . Delta Type: 0 , IntegrityState Valid: true , RetrievedChecksum: 461230020 , ComputedChecksum: 461230020[gle=0x80004005]
2023-09-27 03:38:59, Error                 CSI    000017b8@2023/9/27:02:38:59.845 (F) onecore\base\wcp\deltahydrator\deltahydrator.cpp(60): Error 800f0985 [Warning,Facility=15 (0x000f),Code=2437 (0x0985)] originated in function DeltaHydrator::`anonymous-namespace'::GetPsfxSpecificError expression: ((SCODE) (((unsigned long)(1)<<31) | ((unsigned long)(15)<<16) | ((unsigned long)(0x985))) )
[gle=0x80004005]
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top