[SOLVED] Integrity violations that cannot be repaired - Windows Server 2012 R2 Standard [LAMARR]

[soj4trade]

Hello!

I am running into a file verification issue with a Windows Windows Server 2012 R2 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 other endpoints with this issue, so to prevent confusion with eerily similar titles, I've included the endpoint name in the title within brackets. Hope that's OK!

Thank you in advance! :)

Unfortunately, it seems like there are so many corruptions that the summary was never printed in CBS.log, it just kind of cuts off:

(p)    CSI Payload Corrupt            amd64_cpu.inf_31bf3856ad364e35_6.3.9600.20144_none_4ebd9172dc555eb8\processr.sys
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_cpu.inf_31bf3856ad364e35_6.3.9600.20173_none_4e9c2164dc6e9934\intelppm.sys
Repair failed: M
2022-08-03 14:24:22, Info                  CBS    SQM: CheckSur: hrStatus: 0x800f0906 [CBS_E_DOWNLOAD_FAILURE], download Result: 0x800f0941 [CBS_E_WU_MAPPING_UNAVAILABLE]
2022-08-03 14:24:22, Info                  CBS    Count of times corruption detected: 1
2022-08-03 14:24:22, Info                  CBS    Seconds between initial corruption detections: -1
2022-08-03 14:24:22, Info                  CBS    Seconds between corruption and repair: -1

This line is at the top:

2022-08-03 14:09:08, Info                  CSI    0000000a@2022/8/3:18:09:08.840 Starting corruption detection (InnerFlags=5)
2022-08-03 14:23:36, Info                  CSI    0000000b@2022/8/3:18:23:36.755 Corruption detection complete. numCorruptions = 1922 (0x0000000000000782), Disp = 1.

 

[Maxstar]

Hi,

Are you still needing help with this one, or did you get the problem resolved?

 

[soj4trade]

Hey Maxstar, I think this one is fixed now! Thank you!

 

[Maxstar]

Hi,

Thanks for letting us know, this thread must been have overlooked...