Chkdsk was not needed as windows had found no errors
I ran sfc /scannow in an elevated command prompt with the result
Corrupted files found but cannot repair
reading CBS.log I found 4 cases of cannot repair al of which contained the similar detail at
all referring to DataOracleClientPerfCounters.......hashmismatch
I have been have similar problems, here is a resume of what has happens so far.
The reason for trying to repair is that in spite of following procedures I cannot get AutoPlay to work on this machine which was updated from W7 Pro using Windows update. I had even worse problems with a W7 laptop which I had to revert to W7 and then upgraded using a W10 disc, that now performs perfectly.
I ran DISM /online /Cleanup-image /scanhealth
which said repairable
I then ran restorehealh on it's own and /source:wim:e:\sources\install.wim:1 and the same with/limitaccess
All returned the error cannot find source file although I had checked that te file was there on the Windows 10 disc created from an ISO file
After reading "configure a Windows repair Source" I looked at Group policy but within Computer configuration\administrative templates\system Specify setting for optional component installation and component repair did not exist but specify Windows Installation file did and is not configured
I do wish that I had reverted to 7 in the allowable time and used a disc to upgrade instead of windows update there are no problems on machines where I used this method
As a matter of interest I do have a Windows old file on a clone of my C drive, can I copy this back and revert even though the month has passed?
I have in the past completed a Windows 7 install which did not affect existing data & programs, if I recall by using "Upgrade" does anyone know if this is available for Windows 10?
Last edited by Albyefield; 19 Sep 2015 at 10:36.
I think you're looking for this option though, try it and if it doesn't help, open a new thread of your own - thanks.
Refresh Windows 10 - Windows 10 Forums
My apologies I did think the thread was appropriate, Many thanks for you help.
I'm on Windows 10 Pro, the November Update, Version 1511, (OS Build 10586.3).
I was getting the error"0x800f081f the source file could not be found..." over and over again, trying to run "sfc /scannow" and "dism......" commands. I was trying to use the iso I downloaded directly from the Microsoft Upgrade link via the MediaCreationToolx64. No go, time after time, over the span of a couple days. I even re-downloaded a couple times. I even tried tools to convert esd to wim - nada.
I finally downloaded the 1511 iso from TechBench. I "mounted" the image and ran the following:
"Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:H:\sources\install.wim:1 /limitaccess"
(H:\ being my mounted iso drive. I think "LimitAccess" prevents DISM from going online to Windows Update to download the files. Oh! And notice the "/Source:wim:H:....." part in the path. Some websites are omitting that bolded italicized part of the path.)
Anyway, after downloading and "mounting" the TechBench ".wim" version, everything completed successfully and the component store, etc, was cleaned up nicely. Rebooted and ran "sfc /scannow" again. No integrity errors found.
Don't know why the download via Microsoft Upgade wouldn't work. And yes, I even tried using the path that would be correct for the "install.esd" in place of ".wim". It just wouldn't work . Only the TechBench iso download worked. I suspect there may be something missing, or some kind of corruption in the Microsoft Upgrade direct iso - don't know, just a guess.
In any event, Happy Camper now!
Hope this helps someone.
Last edited by poud; 19 Nov 2015 at 20:08.
Actually, I've noticed the same thing on several installs of Win10. The TechBench iso files work fine whereas the .esd ones are often problematic.Only the TechBench iso download worked. I suspect there may be something missing, or some kind of corruption in the Microsoft Upgrade direct iso - don't know, just a guess.
Same thing when installing using iso files having an install.esd instead of an install.wim. The former often return corruption errors whereas the latter often don't.
No idea why though, just an observation.
Then you need to Download NEW Windows 10 Setup Media... ie Source
I appreciate your input, but there does appear to be something amiss with the primary MS download links. Is why I ended up doing what I did. I have at least 4 iso's I downloaded from Microsoft direct that will not work as the Source for DISM - the only one that does is the TechBench version.