Main Forum > General Computer Support
System File Check For Windows 10
Roy Whitethread:
Boggin, yes I did.
I ran the dism /online /cleanup-image /restorehealth command with Windows 10 running, and again the source file could not be found. I also ran the sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows command, but that didn't work, neither did dism.exe /online /cleanupimage /startcomponentcleanup. (When I tried the latter command I got Error 6800-the function attempted to use a name that is reserved for use by another transaction).
I ran bcdedit |find "osdevice" and 2 drives were listed-F which was the Win 7 disk, which I formatted before running any of these commands, and C , the Windows 10 disk, plus Macrium Reflect's ramdisk recovery option.
I booted from the Windows 10 DVD, went to repair my PC, opened command prompt and ran the various commands again, with the same results.
Regarding the formatted Win 7 disk, I suppose I should have deleted the formatted partition before running any commands. (I have now restored Win 7 from a Macrium Reflect backup image).
Since the sfc /scannow errors all seem to relate to Edge, and that these may be fixed by future Win 10 updates, I propose to forget about them, unless you or Shane have any other ideas.
Boggin:
I haven't come across anyone reporting any sfc / Edge errors, but no one may have had the need to run a sfc /scannow in Win 10.
What did the Win 10 offboot sfc report ?
Perhaps Shane could run a sfc /scannow on his Win 10 to see what he gets.
Julian:
uninstall this update kb3081436 then reinstall the update with the direct download and manual update msu file.
http://download.windowsupdate.com/c/msdownload/update/software/secu/2015/08/windows10.0-kb3081436-x64_4f2d2481f0f3364635a185a20605aa8190c6c951.msu
your sfc scan is references this update 3 times so it may be the trouble maker.
Roy Whitethread:
Boggin, I tried to run the Win 10 offboot sfc scan, but it didn't work. (I tried so many different commands that I can't remember what the problem was).
Good news at last however. I installed the latest build-10252-of Windows 10 Pro x 64, which is working well, and when I ran sfc /scannow no integrity violations were found.
Thanks for all your help.
Best regards, Roy
Julian:
--- Quote from: Roy Whitethread on August 19, 2015, 11:57:21 am ---Boggin, I tried to run the Win 10 offboot sfc scan, but it didn't work. (I tried so many different commands that I can't remember what the problem was).
Good news at last however. I installed the latest build-10252-of Windows 10 Pro x 64, which is working well, and when I ran sfc /scannow no integrity violations were found.
Thanks for all your help.
Best regards, Roy
--- End quote ---
well i'm glad that an update fixed your issue ;)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version