[SOLVED] Server 2016 corruption, can't update (it's a DC and I NEED wu to be able to migrate the CA role)

rama_p

New member
Joined
Nov 29, 2023
Posts
3
Hi Team,
I have a 2016 server that I've been trying for days and days to repair, trying everything under the sun to get this working but so far have been unsuccessful.

The current stat is that I was not even able to run SFC due to "pending operations" that would never complete, so I have had to remove the pending.xml file just go get sfc to run.

I have completed all the steps required in the posting rules and have attached the files.

Please help, you are my last resort.

The components scanner did say this:

Parsing loaded hive, please wait...
Sequence numbers do not match! Hive is dirty and the transaction logs should be reviewed for relevant data!
Hive parsed successfully - found 262,857 keys and 788,519 values
Starting corruption scan
Sequence mismatch! Primary = 41592. Secondary = 41591
Scanning CanonicalData\Catalog for corruptions
Scanning CanonicalData\Deployments for corruptions

However... the final output shows no corruption..
 

Attachments

I have had a dig around on the other posts on this forum and I also have another 2016 server that I have pilfered a few files from to hack up this fix... hopefully its correct, but I have put this together and have run it (attached). I am now doing another dism scan, will update on how it goes.

PS. this is what I could see in the cbs.log to bring me to the conclusion this was broken:
"(p) CSI Manifest Corrupt amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3"
Total Detected Corruption: 1
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 1
CSI Metadata Corruption: 0
CSI Payload Corruption: 0
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True
 

Attachments

Hi Team, just confirming this can be closed! After another long wait for SFC and DISM (using another new server I have just built as the "source") I have managed to get this repaired.
 
Hi and welcome to Sysnative,

Thanks for letting us know and glad you have managed to resolve this issue.
 

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

Back
Top