Windows 10: Windows Resource Protection found corrupt files.

Hi,

just wanted to know what should one do if one gets the error and how does one troubleshoot it properly?

I looked up the log on my system but it's just a really big lump of text.

:)

 

Windows Resource Protection found corrupt files but was unable to fix some of them.

DISM will stop and say the operation completed successfully or will give an error if it did not complete. I have noticed if you click inside the windows while dism is running it seems to stop .If it is still running exit the command prompt and try again.
Open command prompt and either type or copy and past into admin command line and push enter on your keyboard.

DISM /Online /Cleanup-Image /RestoreHealth

Are you running an antivirus or malware program other than defender? You may want to disable them for now and possibly uninstall them. Make sure to deactivate and write down the license code if they are not free and download a current version to reactivate
.Turn on Defender for now while you try to fix your errors.

Here are some similar issues .

Sfc /scannow issue - [Solved] - Windows 10 - Tom's Hardware

It can also be due to outdated drivers.

Do you have an arch bluetooth mouse? Are you running a linux duo boot system?

Error when installing Arch Linux rootfs on Windows 10 Fall Creators Update · Issue #69 · RoliSoft/WSL-Distribution-Switcher

How to Fix Arc Touch Bluetooth Mouse Not Working after Windows 10 Creators Update | Driver Talent

 

Windows Resource Protection found corrupt files but was unable to fix some of them.

Thanks, Mike P. I tried your suggestion. I had to record the commands on paper because when I booted into the repair environment, I couldn't change directory to the C:\ drive. But the commands ran fine. DISM produced a successful completion message.
But when I ran SFC, I got the same error message. Some files are corrupt and SFC could not repair them.

 

If sfc/scannow found corrupt files, run the DISM command and then run the sfc command again. sometimes you need to run sfc 3 times to clean things up. This is from the tutorial forum. https://www.tenforums.com/tutorials/7...-10-image.html .

 

Please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.

 

Before running sfc / dism delete everything from %windir%\logs\cbs (sfc) and %windir%\logs\dism directories to get rid of old logs.

Once you have run sfc you can use this command to strip out all the boring stuff leaving just the errors - it makes it much more readable. Code: findstr /c:"[SR]" %windir%\logs\cbs\cbs.log > "%userprofile%\desktop\sfc.txt"[/quote] dism logs are much shorter - you can generally just go to the bottom and scroll up a page or so. Alternatively you can search for 0x

 

dism logs are much shorter - you can generally just go to the bottom and scroll up a page or so. Alternatively you can search for 0x[/quote] Here you go, there is a bunch of errors in the middle of the file and just before end as well. Note that I've had some issues and Brink did recommend a re-install of Windows 10 but I just have this feeling: meh.

sfc.txt

 

Code: 2015-11-14 16:19:44, Info CSI 000057b8 [SR] Cannot repair member file [l:22{11}]"fdeploy.dll" of Microsoft-Windows-fdeploy, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-11-14 16:19:44, Info CSI 000057ba [SR] Cannot repair member file [l:14{7}]"fde.dll" of Microsoft-Windows-fde, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-11-14 16:19:44, Info CSI 000057bc [SR] Cannot repair member file [l:20{10}]"gpedit.dll" of Microsoft-Windows-GroupPolicy-Admin-Gpedit, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-11-14 16:19:44, Info CSI 000057be [SR] Cannot repair member file [l:20{10}]"gptext.dll" of Microsoft-Windows-GroupPolicy-Gptext, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-11-14 16:19:46, Info CSI 00005806 [SR] Cannot repair member file [l:22{11}]"fdeploy.dll" of Microsoft-Windows-fdeploy, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-11-14 16:19:46, Info CSI 00005807 [SR] This component was referenced by [l:248{124}]"Microsoft-Windows-UserAccounts-WOW64-shell-Package~31bf3856ad364e35~amd64~~10.0.10240.16384.b571b1397b12d9a8fbd6aa3a403d12ef" 2015-11-14 16:19:46, Info CSI 00005808 [SR] This component was referenced by [l:362{181}]"Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-shell~31bf3856ad364e35~amd64~~10.0.10240.16384.Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-shell-Deployment" 2015-11-14 16:19:46, Info CSI 0000580b [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:22{11}]"fdeploy.dll"; source file in store is also corrupted 2015-11-14 16:19:46, Info CSI 00005820 [SR] Cannot repair member file [l:20{10}]"gpedit.dll" of Microsoft-Windows-GroupPolicy-Admin-Gpedit, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-11-14 16:19:46, Info CSI 00005821 [SR] This component was referenced by [l:350{175}]"Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-ds~31bf3856ad364e35~amd64~~10.0.10240.16384.Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-ds-Deployment" 2015-11-14 16:19:46, Info CSI 00005824 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:20{10}]"gpedit.dll"; source file in store is also corrupted 2015-11-14 16:19:46, Info CSI 00005828 [SR] Cannot repair member file [l:20{10}]"gptext.dll" of Microsoft-Windows-GroupPolicy-Gptext, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-11-14 16:19:46, Info CSI 00005829 [SR] This component was referenced by [l:350{175}]"Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-ds~31bf3856ad364e35~amd64~~10.0.10240.16384.Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-ds-Deployment" 2015-11-14 16:19:46, Info CSI 0000582c [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:20{10}]"gptext.dll"; source file in store is also corrupted 2015-11-14 16:19:46, Info CSI 00005843 [SR] Cannot repair member file [l:14{7}]"fde.dll" of Microsoft-Windows-fde, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-11-14 16:19:46, Info CSI 00005844 [SR] This component was referenced by [l:248{124}]"Microsoft-Windows-UserAccounts-WOW64-shell-Package~31bf3856ad364e35~amd64~~10.0.10240.16384.b571b1397b12d9a8fbd6aa3a403d12ef" 2015-11-14 16:19:46, Info CSI 00005845 [SR] This component was referenced by [l:362{181}]"Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-shell~31bf3856ad364e35~amd64~~10.0.10240.16384.Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-shell-Deployment" 2015-11-14 16:19:46, Info CSI 00005848 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:14{7}]"fde.dll"; source file in store is also corrupted[/quote] Please try following command in admin command prompt
Code: DISM /Online /Cleanup-Image /RestoreHealth[/quote] If there are problems with RestoreHealth, please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - Tutorial