[SOLVED] SFC /SCANNOW fails on Windows Server 2016 standard 10.0.14393

[Dingus]

Hello,

I'm experiencing an issue which trying to run the System file checker on virtualized Windows Server 2016 standard 10.0.14393
It ends at 72% saying that Windows Resource Protection could not perform the requested operation.

I searched the CBS log and I found following issue:

2023-06-21 16:41:56, Info CSI 00009e59 [SR] Cannot repair member file [l:16]'ServiceModel.mof' of NetFx4-ServiceModel_mof_files, version 4.0.15744.970, arch amd64, versionScope neutral, pkt {l:8 b:b03f5f7f11d50a3a} in the store, hash mismatch

DISM /Online /cleanup-image /restorehealth completed sucessfully, but SFC /SCANNOW still fails

I ran SFC /VERIFYONLY

I found one more issue when I checked the new CBS

2023-06-22 14:37:03, Info CSI 00005372 [SR] Repairing corrupted file \??\C:\Windows\ELAMBKUP\WdBoot.sys from store


Unfortunately I have no idea how to fix this

My plan is to schedule a maintenance window and to try to repair volumes (chkdsk) and to try to repair framework

Any better idea how to fix this would be very appreciated

 

[Dingus]

Just forgot to upload CBS.log and DISM.log

 

[Dingus]

Perhaps some more detail which I got form the CBS log:

2023-06-21 16:26:44, Info CSI 00004f37 Hashes for file member \SystemRoot\WinSxS\Temp\InFlight\3c1eb9674ca4d90163a00000040f400f\amd64_netfx4-servicemodel_mof_files_b03f5f7f11d50a3a_4.0.15744.970_none_514e7886b3099f5e\ServiceModel.mof do not match actual file [l:16]'ServiceModel.mof' :
Found: {l:20 vwD8XgKq0jAwnL1KRG8b1R9E9Kg=} Expected: {l:20 4fQRiIlG8/xB4dva5Ho2HXROQGc=}
Found: {l:32 3Zbd6SiomfyAX0dEh4FaKyPnA0IAnCkGfwLwx5Kvt3I=} Expected: {l:32 +f7HcsANt6IRSnyoZ/XX15k1uCXosWFuZrIpZNPfnOg=}

 

[Dingus]

I found the way how to fix it manually. I found another windows system with the same version of corrupted file. C:\Windows\WinSxS\amd64_netfx4-servicemodel_mof_files_b03f5f7f11d50a3a_4.0.15744.970_none_514e7886b3099f5e\ServiceModel.mof

I took the ownership. configured full access and I replaced it with the working version.

The file checker was able to finished the rest