1.    09 Jul 2016 #1
    Join Date : Jun 2015
    UK
    Posts : 2,160
    Windows 10 Home x64 (Laptop), Windows 10 Pro x64 (Desktop)

    SFC /SCANNOW Errors After Update


    I've just updated a Windows 8.1 Pro PC to Windows 10 using the Techbench ISO which updated without any problems. However, I've just run sfc /scannow and it found errors it could not repair. I have managed to get sfc /scannow to run without errors - see what I did below:

    1. Ran sfc /scannow which showed error "Windows Resource Protection found corrupt files but was unable to fix some of them."
    2. Ran Dism /Online /Cleanup-Image /ScanHealth which reported "The component store is repairable."
    3. Ran Dism /Online /Cleanup-Image /RestoreHealth which failed with 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."
    4. Mounted the W10 Techbench ISO and ran Dism /Online /Cleanup-Image /RestoreHealth /source:wim:G:\sources\install.wim:1 /limitaccess which reported successfully "The restore operation completed successfully."
    5. Ran sfc /scannow wich completed successfully with report "Windows Resource Protection found corrupt files and successfully repaired them."


    Please advise:
    1. Why would sfc /scannow fail on a newly updated installation which ran sfc /scannow error free immediately before the upgrade?
    2. Why did I have to use install.wim from the Techbench ISO at step 4 above for Dism /Online /Cleanup-Image /RestoreHealth to work and will I have to use install.wim from the Techbench ISO every time I need to run this Dism command?
    3. How can I configure my PC so it has the correct install.wim file for the Dism command to work properly?
      My ComputersSystem Spec
  2.    09 Jul 2016 #2
    Join Date : Oct 2013
    NW Florida
    Posts : 9,643
    Windows 10 Pro and Windows 10 Pro Insider

    Sometimes you have to reboot and run sfc again. The repairs it does actually happen on a reboot. After the reboot you may have to do it again up to 3 times with reboots in between.

    I can't answer why it doesn't find the install.wim, but it is fairly common.
      My ComputersSystem Spec
  3.    09 Jul 2016 #3
    Join Date : Oct 2013
    Penns Forrest
    Posts : 3,506
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3

    Quote Originally Posted by Steve C View Post
    Please advise:
    1. Why would sfc /scannow fail on a newly updated installation which ran sfc /scannow error free immediately before the upgrade?
    2. Why did I have to use install.wim from the Techbench ISO at step 4 above for Dism /Online /Cleanup-Image /RestoreHealth to work and will I have to use install.wim from the Techbench ISO every time I need to run this Dism command?
    3. How can I configure my PC so it has the correct install.wim file for the Dism command to work properly?
    1. Why would sfc /scannow fail on a newly updated installation ...
      In addition to what essenbe said .... there is a known issue re: opencl.dll - it's been around for a while. If it is opencl.dll (follow SFC Command - Run in Windows 10 - Windows 10 Forums), the error can be ignored.

    2. Why did I have to use install.wim from the Techbench ISO ...
      I'm not sure, but it seems to indicate that the Component Store cannot be found (resolved). I think this would cripple your system though instead of only showing up in DISM.
      Try the Windows Update Troubleshooter (TS) in Control Panel - then try https://support.microsoft.com/en-us/...troubleshooter (I'm not sure if they are the same, but why would MS offer a diag cab separate from the built-in TS?

      Please copy the C:\Windows\Logs\CBS (the entire folder) into a compressed folder on your desktop and attach the zip folder to a post. If it is too large, copy just the CBS.log file into a compressed folder and attach that.

    3. How can I configure my PC so it has the correct install.wim ...
      see # 2
      My ComputerSystem Spec
  4.    09 Jul 2016 #4
    Join Date : Oct 2013
    Penns Forrest
    Posts : 3,506
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3

    I looked at a few pages in a search

    If KB3022345 is installed - uninstall it

    Is .NET 3.5 enabled in Programs and Features - try disabling it, restart, try DISM
      My ComputerSystem Spec
  5.    09 Jul 2016 #5
    Join Date : Jun 2015
    UK
    Posts : 2,160
    Windows 10 Home x64 (Laptop), Windows 10 Pro x64 (Desktop)
    Thread Starter

    CBS.zip

    Thanks. Yes - there was an opencl.dll error reported as [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted.

    This is now fixed as mentioned in post 1. I enclose the CBS log folder for those who understand these things. KB3022345 is not installed. I have some elements of .NET 3.5 installed (see enclosed). I'm wary of removing it unless it affects something else.

    Click image for larger version. 

Name:	NET.JPG 
Views:	20 
Size:	59.8 KB 
ID:	89184

    I ran reagentc /info and found the recovery image was pointing to the old Windows 8.1 image I had configured. I've now configured this to use install.wim from the Techbench ISO - would that explain the problem?
      My ComputersSystem Spec
  6.    09 Jul 2016 #6
    Join Date : Oct 2013
    Penns Forrest
    Posts : 3,506
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3

    Yeah, sometimes I miss things - thanks for pointing that out

    KB3022345 not installed - OK (the reference was probably to a previous version of Windows). It never hurts to check.

    .NET looks OK

    reagentc should really point to a Win10 winRE.wim either in the Recovery partition or in the C:\Windows\System32\Recovery folder
    But no I don't think that would cause DISM to fail the way it did.

    You could easily test that by running DISM ..... /RestoreHealth without the source parameter - if it fails, then reagent was not the issue.

    Did you run the troubleshooter(s)?
      My ComputerSystem Spec

 


Similar Threads
Thread Forum
Solved SFC /scannow - errors
Hey all! I recently upgrade to Windows 10 2 weeks ago and for kicks I decided to run an SFC /scannow .. and It found a whole slew of errors! It's weird because I don't see anything wrong with the OS but I know there are according to the scanner....
Performance & Maintenance
SFC /ScanNow Finds Errors Every Time
I run sfc /scannow and it finds errors and cannot fix them. I then run dism /online /cleanup-image /restorehealth /source:wim:x:\sources\install.wim:1 /limitaccess and that succeeds. I run sfc /scannow again and it is able to fix the errors. I run...
Performance & Maintenance
sfc /scannow errors
I had a problem with chrome on windows 10, uninstalled it, new installer had malware on it. fixed it all up. system runs fine no problems. Decided to check sfc /scannow and got the corrupt files message "Windows Resource Protection found corrupt...
Performance & Maintenance
Solved Running sfc /scannow shows that there are errors
Things are not going well for me. Multiple system issues are being reported in the Reliability Monitor although these are not obvious while using the OS. One of the things I have now tried is sfc /scannow from a command prompt in both normal and...
Performance & Maintenance
Solved sfc /scannow found errors
I ran "sfc /scannow" just for the heck of it and it found the following errors. 32091 32090 Can anyone decipher the issue(s) it's pointing to? And perhaps know how to resolve it?
Performance & Maintenance
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 07:36.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums