DISM error 0x800f081f source not found / SFC error Windows Resource Protection could not perform the request...

DenilsonTobal

New member
Joined
Feb 7, 2025
Posts
1
Hi folks!
Our Win2k19 was not doing updates. After some CBS.log... doing that procedure to reset windows update... some updates was installed fine... now I am trying to install Cumulative update KB5050008, but it wont install. This server was with Windows update... and I already have tried CHKDSK... no sucess... when I run DISM, in the CBS.log I see these errors bellow. I tried to do the repair downloading the KB with these files... point DISM to that sources... but no sucess. I am sending my CBS log folder, and ComponentsScanner. Please, help! I will contribuite for sure!!! :)

025-02-07 12:10:00, Info CSI 00000007 Hashes for file member [l:27]'MSFT_MpComputerStatus.cdxml' do not match.
Expected: {l:32 ml:4096 b:250a58b9ec6c327e7d165cecbdbae0b1fdca203cd342dba12616527b47a44486}.
Actual: {l:32 b:cbfca6cb14b5a84f5bd30cbc9b05f008f4916e54a33a513fcedf8bff90002f5d}.
2025-02-07 12:10:00, Info CSI 00000008 Warning: Unable to repair payload file ([l:27]'MSFT_MpComputerStatus.cdxml') for component ([l:99 ml:140]'amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.5830_none_311d57717347d139') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2025-02-07 12:10:00, Info CSI 00000009 Hashes for file member [l:19]'MSFT_MpThreat.cdxml' do not match.
Expected: {l:32 ml:4096 b:ae595236832a3884d2aa3f913454ac6ff4c735f55e819c7f391c94b653281f92}.
Actual: {l:32 b:dd2decdbc6ec0357ddbd952ad3c29c0a05fc7368badb377648bb8f0964eedeec}.
2025-02-07 12:10:00, Info CSI 0000000a Warning: Unable to repair payload file ([l:19]'MSFT_MpThreat.cdxml') for component ([l:99 ml:140]'amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.5830_none_311d57717347d139') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2025-02-07 12:10:00, Info CSI 0000000b Hashes for file member [l:26]'MSFT_MpThreatCatalog.cdxml' do not match.
Expected: {l:32 ml:4096 b:106d459542c3ec7dd9b7e545d74a4a98f0ad74c7db6a1333cfcd9168e2a3c076}.
Actual: {l:32 b:ff8bbde3d74745abc4b8bef6278c46bd9bba05c2e61f0eb033787443cde80f44}.
2025-02-07 12:10:00, Info CSI 0000000c Warning: Unable to repair payload file ([l:26]'MSFT_MpThreatCatalog.cdxml') for component ([l:99 ml:140]'amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.5830_none_311d57717347d139') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2025-02-07 12:10:00, Info CSI 0000000d Hashes for file member [l:28]'MSFT_MpThreatDetection.cdxml' do not match.
Expected: {l:32 ml:4096 b:a19bf000eb950ddd8438c30562c0fa6f3c0848432f55a219ef3d79b302aa6cf1}.
Actual: {l:32 b:3c082a55cd0e2d835764bb55c35292277b3c3a7a909543123a9b75bddf7ef20f}.
2025-02-07 12:10:00, Info CSI 0000000e Warning: Unable to repair payload file ([l:28]'MSFT_MpThreatDetection.cdxml') for component ([l:99 ml:140]'amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.5830_none_311d57717347d139') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2025-02-07 12:10:00, Info CSI 0000000f Hashes for file member [l:23]'MSFT_MpPreference.cdxml' do not match.
Expected: {l:32 ml:4096 b:8bbe2742d4284d6a9578cada99243b282e6be6df9a6f796d19e6e72eafa1e382}.
Actual: {l:32 b:dd557986b51074f3e4b7d5c0923903bf10ba919a1235605f5cba8a49b05ef07d}.
2025-02-07 12:10:00, Info CSI 00000010 Warning: Unable to repair payload file ([l:23]'MSFT_MpPreference.cdxml') for component ([l:99 ml:140]'amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.5830_none_311d57717347d139') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2025-02-07 12:10:00, Info CSI 00000011 Hashes for file member [l:17]'MSFT_MpScan.cdxml' do not match.
Expected: {l:32 ml:4096 b:a27630566684ee79af41ac68dc70bbdbffc968b2489aa16be0d0fa0e0eccf0c8}.
Actual: {l:32 b:52a143a0bcb954c7ec8b35044ef9284055c75e7e2fe316cbaa120d665c06b1a7}.
2025-02-07 12:10:00, Info CSI 00000012 Warning: Unable to repair payload file ([l:17]'MSFT_MpScan.cdxml') for component ([l:99 ml:140]'amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.5830_none_311d57717347d139') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2025-02-07 12:10:00, Info CSI 00000013 Hashes for file member [l:20]'MSFT_MpWDOScan.cdxml' do not match.
Expected: {l:32 ml:4096 b:80ddeca09c6c85cde406bd9352c24cb6ca58ab17062159713f0591c46fa7b9fd}.
Actual: {l:32 b:064d8c62e1d613524ab6f414d4906ba77d8eefc4ba2bae3ac796b3332b1681ec}.
2025-02-07 12:10:00, Info CSI 00000014 Warning: Unable to repair payload file ([l:20]'MSFT_MpWDOScan.cdxml') for component ([l:99 ml:140]'amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.5830_none_311d57717347d139') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2025-02-07 12:10:00, Info CSI 00000015 Hashes for file member [l:22]'MSFT_MpSignature.cdxml' do not match.
Expected: {l:32 ml:4096 b:dbb84a0489a5dfeecb4e850412aabb72e725e5f89319d9e158a8baa9be6470da}.
Actual: {l:32 b:956a869d006ef2b477e146835befea9e9da6af260506389e79ce8a669906f0b3}.
2025-02-07 12:10:00, Info CSI 00000016 Warning: Unable to repair payload file ([l:22]'MSFT_MpSignature.cdxml') for component ([l:99 ml:140]'amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.5830_none_311d57717347d139') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2025-02-07 12:10:00, Info CSI 00000017 Hashes for file member [l:13]'Defender.psd1' do not match.
Expected: {l:32 ml:4096 b:1b1971fcbdc0abc871748d7409c696bb509c4ede12b0c748af0af96e629961b7}.
Actual: {l:32 b:b096112fba4e3abcde87ad6dfc843c7e2d74fb469125a00404e12fbe5f054ecb}.
2025-02-07 12:10:00, Info CSI 00000018 Warning: Unable to repair payload file ([l:13]'Defender.psd1') for component ([l:99 ml:140]'amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.5830_none_311d57717347d139') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2025-02-07 12:11:20, Warning CBS Current tick count: 800 lower than last tick count: 1160. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2025-02-07 12:11:20, Error CSI 00000019@2025/2/7:15:11:20.918 (F) Attempting to mark store corrupt with category [l:18 ml:19]'CorruptPayloadFile'[gle=0x80004005]
2025-02-07 12:11:20, Info CSI 0000001a@2025/2/7:15:11:20.975 Corruption detection complete. numCorruptions = 9, Disp = 1.
2025-02-07 12:11:21, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2025-02-07 12:11:21, Info CSI 0000001b@2025/2/7:15:11:21.390 CSI Transaction @0x286bdba0f70 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000000 and client id 'TI5.31160690_331873224:1/'
 

Attachments

Hi @DenilsonTobal,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team
 
Hi and welcome to Sysnative,

Step 1. Download
67139f7e69a58-SFCFix-ico.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.
67139f52b3c1e-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

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

Back
Top