[SOLVED] Windows Server 2019 DISM/SFC Corruption

Simoniuks

Simoniuks

New member
Joined
Jul 22, 2022
Posts
3
Hello,

I've been troubleing to install latest cumulative update into server.
Found that SFC Scan and DISM restore health (ISO or Online) not working with following errors
SFCFix is crashing also.
ComponentsScanner did not find any errors.


SFC Scan error
Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 74% complete.

Windows Resource Protection could not perform the requested operation.


DISM error
C:\WINDOWS\system32>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1697

Image Version: 10.0.17763.1817

[===========================92.6%===================== ]
Error: 0x800f0954

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

Attaching COMPONENTS AND CBS.log maybe you will be able to help me.
 

Attachments

Rich (BB code): 
2022-07-22 11:08:40, Info                  CSI    000045f2 Hashes for file member [l:27]'MSFT_MpComputerStatus.cdxml' do not match.
 Expected: {l:32 ml:4096 b:250a58b9ec6c327e7d165cecbdbae0b1fdca203cd342dba12616527b47a44486}.
 Actual: {l:32 b:cbfca6cb14b5a84f5bd30cbc9b05f008f4916e54a33a513fcedf8bff90002f5d}.
2022-07-22 11:08:40, Info                  CSI    000045f3 [SR] Cannot repair member file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2022-07-22 11:08:40, Info                  CSI    000045f4 Hashes for file member [l:19]'MSFT_MpThreat.cdxml' do not match.
 Expected: {l:32 ml:4096 b:ae595236832a3884d2aa3f913454ac6ff4c735f55e819c7f391c94b653281f92}.
 Actual: {l:32 b:dd2decdbc6ec0357ddbd952ad3c29c0a05fc7368badb377648bb8f0964eedeec}.
2022-07-22 11:08:40, Info                  CSI    000045f5 [SR] Cannot repair member file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2022-07-22 11:08:40, Info                  CSI    000045f6 Hashes for file member [l:26]'MSFT_MpThreatCatalog.cdxml' do not match.
 Expected: {l:32 ml:4096 b:106d459542c3ec7dd9b7e545d74a4a98f0ad74c7db6a1333cfcd9168e2a3c076}.
 Actual: {l:32 b:ff8bbde3d74745abc4b8bef6278c46bd9bba05c2e61f0eb033787443cde80f44}.
2022-07-22 11:08:40, Info                  CSI    000045f7 [SR] Cannot repair member file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2022-07-22 11:08:40, Info                  CSI    000045f8 Hashes for file member [l:28]'MSFT_MpThreatDetection.cdxml' do not match.
 Expected: {l:32 ml:4096 b:a19bf000eb950ddd8438c30562c0fa6f3c0848432f55a219ef3d79b302aa6cf1}.
 Actual: {l:32 b:3c082a55cd0e2d835764bb55c35292277b3c3a7a909543123a9b75bddf7ef20f}.
2022-07-22 11:08:40, Info                  CSI    000045f9 [SR] Cannot repair member file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2022-07-22 11:08:40, Info                  CSI    000045fa Hashes for file member [l:23]'MSFT_MpPreference.cdxml' do not match.
 Expected: {l:32 ml:4096 b:8bbe2742d4284d6a9578cada99243b282e6be6df9a6f796d19e6e72eafa1e382}.
 Actual: {l:32 b:dd557986b51074f3e4b7d5c0923903bf10ba919a1235605f5cba8a49b05ef07d}.
2022-07-22 11:08:40, Info                  CSI    000045fb [SR] Cannot repair member file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2022-07-22 11:08:40, Info                  CSI    000045fc Hashes for file member [l:17]'MSFT_MpScan.cdxml' do not match.
 Expected: {l:32 ml:4096 b:a27630566684ee79af41ac68dc70bbdbffc968b2489aa16be0d0fa0e0eccf0c8}.
 Actual: {l:32 b:52a143a0bcb954c7ec8b35044ef9284055c75e7e2fe316cbaa120d665c06b1a7}.
2022-07-22 11:08:40, Info                  CSI    000045fd [SR] Cannot repair member file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2022-07-22 11:08:40, Info                  CSI    000045fe Hashes for file member [l:20]'MSFT_MpWDOScan.cdxml' do not match.
 Expected: {l:32 ml:4096 b:80ddeca09c6c85cde406bd9352c24cb6ca58ab17062159713f0591c46fa7b9fd}.
 Actual: {l:32 b:064d8c62e1d613524ab6f414d4906ba77d8eefc4ba2bae3ac796b3332b1681ec}.
2022-07-22 11:08:40, Info                  CSI    000045ff [SR] Cannot repair member file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2022-07-22 11:08:40, Info                  CSI    00004600 Hashes for file member [l:22]'MSFT_MpSignature.cdxml' do not match.
 Expected: {l:32 ml:4096 b:dbb84a0489a5dfeecb4e850412aabb72e725e5f89319d9e158a8baa9be6470da}.
 Actual: {l:32 b:956a869d006ef2b477e146835befea9e9da6af260506389e79ce8a669906f0b3}.
2022-07-22 11:08:40, Info                  CSI    00004601 [SR] Cannot repair member file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2022-07-22 11:08:40, Info                  CSI    00004602 Hashes for file member [l:13]'Defender.psd1' do not match.
 Expected: {l:32 ml:4096 b:1b1971fcbdc0abc871748d7409c696bb509c4ede12b0c748af0af96e629961b7}.
 Actual: {l:32 b:b096112fba4e3abcde87ad6dfc843c7e2d74fb469125a00404e12fbe5f054ecb}.
2022-07-22 11:08:40, Info                  CSI    00004603 [SR] Cannot repair member file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

Rich (BB code): 
2022-07-22 11:19:21, Info                  CBS    (p)    CSI Payload Corrupt    (n)            wow64_networking-mpssvc-svc_31bf3856ad364e35_10.0.17763.2237_none_f2031c8fce033fdd\r\FirewallAPI.dll
2022-07-22 11:19:21, Info                  CBS    Repair failed: Missing replacement payload.
2022-07-22 11:19:21, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-settingsynchost_31bf3856ad364e35_10.0.17763.2989_none_cd3687bdf523cfba\r\SettingSyncHost.exe
2022-07-22 11:19:21, Info                  CBS    Repair failed: Missing replacement payload.
2022-07-22 11:19:21, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-security-spp-ux_31bf3856ad364e35_10.0.17763.2028_none_a9705e467088ba29\r\DeviceReactivation.dll
2022-07-22 11:19:21, Info                  CBS    Repair failed: Missing replacement payload.


Hi and welcome to Sysnative,

Step 1.
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 System File Checker and post the result. If it fails attach a new copy of the CBS log.
Code: 
SFC /Scannow
 

Attachments

Last edited:
Hi,

Step 1.
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 SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
62151e1bebac4-SFCFix-Txt-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 System File Checker again and post the result. If it fails attach a new copy of the CBS log.
Code: 
SFC /Scannow
 

Attachments

After second script
Sfc finished 100%
C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag

C:\WINDOWS\system32>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1697

Image Version: 10.0.17763.3165

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully


Updates succesfully isntalled, thank you for help
 
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