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:
- Ran sfc /scannow which showed error "Windows Resource Protection found corrupt files but was unable to fix some of them."
- Ran Dism /Online /Cleanup-Image /ScanHealth which reported "The component store is repairable."
- 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."
- Mounted the W10 Techbench ISO and ran Dism /Online /Cleanup-Image /RestoreHealth /wim:G:sourcesinstall.wim:1 /limitaccess which reported successfully "The restore operation completed successfully."
- Ran sfc /scannow wich completed successfully with report "Windows Resource Protection found corrupt files and successfully repaired them."
Please advise:
- Why would sfc /scannow fail on a newly updated installation which ran sfc /scannow error free immediately before the upgrade?
- 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?
- How can I configure my PC so it has the correct install.wim file for the Dism command to work properly?
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.
Please advise:
- Why would sfc /scannow fail on a newly updated installation which ran sfc /scannow error free immediately before the upgrade?
- 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?
- How can I configure my PC so it has the correct install.wim file for the Dism command to work properly?
- 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 blog), the errorcan be ignored.- 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 (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:WindowsLogsCBS (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.- How can I configure my PC so it has the correct install.wim ...
see # 2
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
CBS.zip
Thanks. Yes - there was an opencl.dll error reported as [SR] Could not reproject corrupted file [l:23 ml:24]"??C:WINDOWSSysWOW64"[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.
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?
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:WindowsSystem32Recovery 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)?
