Windows Resource Protection found corrupt files.


  1. BorisTheAnimal
    Posts : 382
    Windows 10 Home
       New #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 Computer
    Quote Quote

  3. JohnC
    Posts : 0
    Dual Boot 10 Pro v1607 10 Pro rs2 build 14971
       New #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 Computer
    Quote Quote

  4. axe0
    Posts : 14,903
    Windows 10 Pro
       New #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 Computers
    Quote Quote

  6. lx07
    Posts : 5,478
    2004
       New #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 Computer
    Quote Quote

  7. BorisTheAnimal
    Posts : 382
    Windows 10 Home
    Thread Starter
       New #5

    lx07 said:
    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 Computer
    Quote Quote

  8. axe0
    Posts : 14,903
    Windows 10 Pro
       New #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 Computers
    Quote Quote

 

  Related Discussions
Windows Resource Protection found corrupt files that it was unable to fix. What should I do? Windows 10 Pro version 10.0.19042 Build 19042 Error log 2020-11-28 15:46:17, Info CBS TI: --- Initializing Trusted Installer...
Ran SFC , found some errors . How to proceed ? 210310 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...
When shutting down, after the drive light has stopped, the power button continues to blink requiring a forced off holding down the power button. Although possibly coincidence, when the laptop is started and later shutdown while on battery vs....
This Win10 Pro 1903 desktop began to display signs of instability. SFC /SCANNOW indicated problems. I ran these commands as suggested in another TenForums discussion: dism /online /cleanup-image /scanhealth dism /online /cleanup-image...
Hello, I have tried to run sfc/ scannow and it gives me the notification that: WIndows resource protection has found some corrupt files but is unable to fix some of them. Details are included in the CBS.log. Is it ok to post the log here so...
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 23:35.
Find Us




Windows 10 Forums