Windows 10: Windows Resource Protection found corrupt files.

  1.    13 Nov 2015 #1

    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.
      My ComputerSystem Spec


  2. Posts : 3
    Dual Boot 10 Pro v1607 10 Pro rs2 build 14971
       13 Nov 2015 #2

    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 .
      My ComputerSystem Spec


  3. Posts : 13,350
    Windows 10 Pro
       14 Nov 2015 #3

    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.
      My ComputersSystem Spec

  4.    14 Nov 2015 #4

    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"
    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
      My ComputerSystem Spec

  5.    14 Nov 2015 #5

    lx07 said: View Post
    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"
    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
    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
      My ComputerSystem Spec


  6. Posts : 13,350
    Windows 10 Pro
       14 Nov 2015 #6

    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
    Please try following command in admin command prompt
    Code:
    DISM /Online /Cleanup-Image /RestoreHealth
    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
      My ComputersSystem Spec


 

Related Threads
Program files (.exe) which are not installed (and so don't have a shortcut) are not being found by Windows search. Shortcuts, help files, folders etc with the same name all show up. 43172 Indexing is complete and .exe is defined (as default)...
Windows 10 SFC Unable to fix corrupt files in Performance & Maintenance
Ok After cleaning Malware , the SFC is finding corrupt files , since this I have took the following steps Update to windows 10 using Windows 10 ISO , within windows 10 operating system while keeping apps and documents SFC / scannow ( many...
Solved SFC Corrupt Files in Performance & Maintenance
Windows search doesn't work. I ran SFC /scannow and there is corrupt files, the log is attached.
Hello, I ran "SFC /scannow" and got an error saying the System File Checker found errors but couldn't fix them. Afterwards I ran "DISM /Online /Cleanup-Image /RestoreHealth" and DISM threw the error 0x800f081f saying that the source files could...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 01:36.
Find Us