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 sfc /scannow again a day or so later and it finds errors all over again. Any idea what the issue is? Thanks
Last edited by T0mmy1977; 13 Mar 2017 at 16:53.
Ya know, we can't see what you see.
View Only the "SFC" Scan Results from the CBS.LOG
Attach sfcdetails.txt on your next post
See: Upload and Attach a File or Image into a "Go Advanced" Post
Thanks
Thank you for your helpful reply, but I am going back to Windows 7 Pro until MSFT cleans up Windows 10. I also get the 'BAD_POOL_Blah_Blah' BSOD, etc. I have updated drivers for all of my hardware/devices and the most recent version of all my software. Windows 7 Pro runs smoothly and I do not get a single error/crash with it.
Last edited by T0mmy1977; 13 Mar 2017 at 16:53.
Do you have nVidia graphics card?
Many users have stated that sfc shows errors when that graphics card is installed - my laptop does, checked with dism & no errors found.
The opencl.dll issue is not only with Nvidia, although it is probably the most common.
T0mmy1977's machine has other things going wrong that would most likely be resolved by a Clean install.
Many people refuse to let Windows 10 do what it is very good at doing. Hardware drivers should come from MS - they test them extensively and then put new ones in the update chain.
Old habits die hard - many issues are caused by going to an OEM for the latest and greatest driver.
Although many issues are also caused by upgrades - same sort of thing though, old software carried over.
A user need only go to an OEM for drivers if it is flagged in Device Manager or if the installed driver is causing issues and there is a fix for that issue documented in the OEM release notes.
A Clean install forces new software - although, some people just put the old stuff back on using 5 or 10 y/o discs
Quote