Since updating my laptop with the Windows 10 November update, a component of my Component Store seems to have gone corrupt that neither using the media utility to reinstall the update nor running sfc /scannow is able to resolve. Whenever I execute the sfc /scannow command, I get the following error:

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

I do not know how to read the log file, and it is extremely large (~100,000 lines since I've run it so much), so I do not want to put the entire thing on Pastebin. If someone knows what to look for or what I should pull from the log to post, I can do so.

  • Delete the log file first. Run sfc again. Search for the word "failed" in the log file. Also see if you have any "CSI Payload Corrupt" entries there. – AnT Nov 19 '15 at 1:17
  • Searching for "failed" and "CSI Payload Corrupt" did not return anything. I've uploaded a copy of the log file to Dropbox since Chrome does not seem to appreciate me trying to copy the entire text from the log file in to Pastebin. dropbox.com/s/p4dfyordknwf5aj/CBS.log?dl=0 – DavidB Nov 19 '15 at 1:51
  • Hm... That's strange. I don't see anything in your log file that would justify "found corrupt files but was unable to fix" message from sfc. Entries like "duplicate ownership..." are rather innocent - we all have this. The rest are "directory not owned...", which are innocent as well. All your log entries are "Info" entries, not "Error" entries, which means that there's noting out of ordinary in your CBS.log. – AnT Nov 19 '15 at 1:55
  • @AnT So the duplicate ownership issue should not be causing the "corrupt file" message in the console? – DavidB Nov 19 '15 at 2:05

The 32Bit OpenCL.dll is damaged:

Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

Since Windows 8, you can use the a new DISM command to repair corrupted files:

DISM /Online /Cleanup-Image /RestoreHealth

This will download the clean file from Microsoft server.

If this fails, download the Version 1511 ISO, mount the ISO into a virtual DVD drive and run this command:

Dism /Online /Cleanup-Image /RestoreHealth /source:wim:D:\sources\install.wim:1 /limitaccess

(where D: is your mounted Win10 ISO)

  • The DISM command just outputs the following: Error: 0x800f081f The source files could not be found. Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log DISM Log: dropbox.com/s/qczd6ash8n007yx/dism.log?dl=0 – DavidB Nov 19 '15 at 11:19
  • @DavidB - The reason DISM couldn't repair the file is because it isn't in the WInSxS folder. This is because you installed the update, and the folder, was adjusted and any irrelevant packages were removed. In other words unless you need this feature you can ignore it. The actual package isn't even compatible with Windows 10. – Ramhound Nov 19 '15 at 12:57
  • @Ramhound Can I just browse to the location of the file and delete it then? – DavidB Nov 19 '15 at 13:47
  • 1
    Good solution - serverfault.com/a/741491/288323 – 23W Dec 30 '15 at 0:42
  • 1
    Agree with @23W that serverfault.com/a/741491/288323 is good solution ... but also make sure you use the correct ISO source as recommended there by 23W (microsoft.com/en-us/software-download/techbench) on another (lower-rated) answer to that question. My newest MSDN image gave the infamous 0x800f081f error, but correct ISO source worked. Insufficient rep to comment over there :-( – Ian W Mar 10 '16 at 17:20

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.