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

soj4trade

soj4trade

Well-known member
Joined
Jul 14, 2022
Posts
133
Location
US East
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! :)
 

Attachments

Hi and welcome to Sysnative,

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

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.
 

Attachments

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

Attachments

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

Attachments

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

Attachments

Last edited:
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
 
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! :)
 
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.
 
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?
 
I'm getting:

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

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!
 
No problem, take your time to perform te reboot, I will see the result on Monday...

And for now! - Have a nice weekend...
 
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!
 
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.
 
Hi,

Please post a new copy of the CBS log, the error 0x80070002 means in most situations that there are certain files missing.
 
The most recent CBS.log file contains pretty much nothing, but the persist logs do. I've uploaded all of them: CBS.zip

In an effort to prevent confusion, here's what I've done so far:
  1. Importing of all donor component files succeeded (thanks again for those).
  2. DISM succeeded.
  3. SFC succeeded.
  4. Rebooted.
  5. Automatic patching failed.
  6. Attempt to manually install KB5007206 failed.
  7. Deleted user "Unknown Account" as per some article I found online.
  8. Rebooted.
  9. Attempt to manually install KB5007206 failed.
  10. Rebooted.
  11. Attempted to install KB4594442, but haven't had a chance to reboot yet. This is what I'll do later tonight. Odds are it'll fail as well.
The theory behind these steps is that, since the server is so out of date (build 17763.1577), I wanted to install the next patch released by Microsoft (17763.1579), which is KB4594442.
 
Hi,

Rich (BB code): 
2022-08-10 00:09:35, Info                  CBS    Doqe: [Forward] Staging driver updates, Count 80
2022-08-10 00:09:35, Info                  CBS            STAGE index: 56, phase: 1, result 0, inf: oposdrv.inf
2022-08-10 00:09:35, Info                  CBS            STAGE index: 110, phase: 1, result 0, inf: miradisp.inf
2022-08-10 00:09:35, Info                  CBS            STAGE index: 142, phase: 1, result 2, inf: RDCameraDriver.inf
2022-08-10 00:09:35, Info                  CBS    Doqe: Recording result: 0x80070002, for Inf: RDCameraDriver.inf
2022-08-10 00:09:35, Info                  CBS    DriverUpdateStageUpdates failed [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-08-10 00:09:35, Error                 CBS    Doqe: Failed staging driver updates [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

  • Open Windows Explorer and browse to the C:\Windows\INF folder.
  • Right-click on the file setupapi.dev 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.
618e949e09fef-CBS-Folder.png

  • Attach the file setupapi.dev.zip in your next reply.
 
You must log in or register to reply here.

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

Back
Top