Integrity violations that cannot be repaired - Windows Server 2019 Standard [AECSS19]

soj4trade · Aug 2, 2022

Hello!

I am running into a file verification issue with a Windows Server 2019 Standard operating system. When I run "SFC /SCANNOW" it confirms that integrity violations exist, but Windows was unable to repair some of them. Furthermore, "DISM /Online /Cleanup-Image /RestoreHealth" says that the source files could not be found.

I have a few servers with this issue, so to prevent confusion with eerily similar titles, I've included the server name in the title within brackets. Hope that's OK!

Thank you in advance! :)

Maxstar · Aug 3, 2022

Hi and welcome to Sysnative,

Step 1. Download

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.

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

soj4trade · Aug 3, 2022

My apologies — the "browscap.ini" file was already in the "C:\Windows\WinSxS\amd64_microsoft-windows-iis-aspbinaries_31bf3856ad364e35_10.0.17763.1_none_7d4a382cbf9e3429\" folder. I reviewed the CBS.log file that I sent you yesterday, and I realized that the operation seemed to abort/fail before a summary could be presented in CBS.log. I just re-ran DISM /Online /Cleanup-Image /RestoreHealth and captured a complete CBS.log file, which I've attached.

Just so there's no surprises:

Code:

2022-08-03 13:08:28, Info                  CBS    Summary:
2022-08-03 13:08:28, Info                  CBS    Operation: Detect and Repair
2022-08-03 13:08:28, Info                  CBS    Operation result: 0x800f081f
2022-08-03 13:08:28, Info                  CBS    Last Successful Step: Entire operation completes.
2022-08-03 13:08:28, Info                  CBS    Total Detected Corruption:    1148
2022-08-03 13:08:28, Info                  CBS        CBS Manifest Corruption:    0
2022-08-03 13:08:28, Info                  CBS        CBS Metadata Corruption:    0
2022-08-03 13:08:28, Info                  CBS        CSI Manifest Corruption:    0
2022-08-03 13:08:28, Info                  CBS        CSI Metadata Corruption:    0
2022-08-03 13:08:28, Info                  CBS        CSI Payload Corruption:    1148
2022-08-03 13:08:28, Info                  CBS    Total Repaired Corruption:    0
2022-08-03 13:08:28, Info                  CBS        CBS Manifest Repaired:    0
2022-08-03 13:08:28, Info                  CBS        CSI Manifest Repaired:    0
2022-08-03 13:08:28, Info                  CBS        CSI Payload Repaired:    0
2022-08-03 13:08:28, Info                  CBS        CSI Store Metadata refreshed:    True
2022-08-03 13:08:28, Info                  CBS   
2022-08-03 13:08:28, Info                  CBS    Total Operation Time: 2489 seconds.

Maxstar · Thursday at 3:14 AM

Hi,

I've made 6 batches with replacement files, here is the first one. Don't run DISM or other commands before we applied all the batches with SFCFix.

Download

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.

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.

soj4trade · Thursday at 12:54 PM

So far so good! :)

Here's the log output. Looks like it was successful!

Maxstar · Thursday at 12:58 PM

Great, here is the next batch.

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.

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.

soj4trade · Thursday at 1:06 PM

Here's the log output. Looks like this one was also successful!

Maxstar · Friday at 3:52 AM

Hi,

And the third fix.

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.

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.

Maxstar · Friday at 4:23 AM

It looks like we are in another timezone so I will post the next batches as well. Some are too big to attach, so I've uploaded them to WeTransfer.

SFCFix batch 4 - SFCFix.zip
SFCFix batch 5 - SFCFix.zip
SFCFix bacth 6 - SFCFix.zip

soj4trade · Friday at 10:21 AM

Thank you! All six batches seem to have executed successfully; not a single error message in any of the logs. That's great!

My gut tells me to run "DISM /Online /Cleanup-Image /RestoreHealth", but I'd rather not get myself into trouble until I hear back from you. Awaiting further instructions! :)

Maxstar · Friday at 10:25 AM

You're welcome.

Yes, please run the DISM /Online /Cleanup-Image /RestoreHealth command and let me know the result. If it fails attach a new copy of the CBS log.

soj4trade · Friday at 10:45 AM

Now here's a message that I don't see too often...

Code:

The restore operation completed successfully.

Sweet!! Now, my next step is to run SFC /SCANNOW, yes?

Maxstar · Friday at 10:50 AM

Yes, please run that command as well and post the result.

soj4trade · Friday at 11:03 AM

I'm getting:

There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again.

I can't reboot the domain controller in the middle of the day, so I'll need to wait until around 6 PM (EST). Odds are you'll be asleep, so I'll reply to this and we'll likely follow up on Monday!

Maxstar · Friday at 11:08 AM

No problem, take your time to perform te reboot, I will see the result on Monday...

And for now! - Have a nice weekend...

soj4trade · Monday at 1:07 PM

Just wanted to let you know that CBS found no integrity violations! I'm running Windows Updates now, but I won't know if those will be successful until tomorrow. More to come soon!

soj4trade · 2022-08-09T18:19:12-0400

Hate to say it, but the server still won't patch. Every Windows Update (be it automatic or manual from the Microsoft Catalog) fails to install with error code 0x80070002

I've already reset Windows Update components (Windows Update - Additional resources - Windows Deployment) to no avail. DISM and SFC succeed with no problems.

I don't know. Any other thoughts? I might have to call Microsoft again.

Integrity violations that cannot be repaired - Windows Server 2019 Standard [AECSS19]

Member

Attachments

Sysnative Staff, Windows Update Analyst, Security Analyst

Attachments

Member

Attachments

Sysnative Staff, Windows Update Analyst, Security Analyst

Attachments

Member

Attachments

Sysnative Staff, Windows Update Analyst, Security Analyst

Attachments

Member

Attachments

Sysnative Staff, Windows Update Analyst, Security Analyst

Attachments

Sysnative Staff, Windows Update Analyst, Security Analyst

Member

Sysnative Staff, Windows Update Analyst, Security Analyst

Member

Sysnative Staff, Windows Update Analyst, Security Analyst

Member

Sysnative Staff, Windows Update Analyst, Security Analyst

Member

Member