Main Forum > General Computer Support
System File Check For Windows 10
Roy Whitethread:
Boggin,
I ran the two Dism commands. The first one completed successfully, but the second one ended by saying it was unable to locate the source file, so I still need someone to help with that for Win 10 please.
Regarding the partition letters, I should have realized that when I ran the bcdedit |find "osdevice" command the reason the command prompt window showed 2 partition letters is that I have Win 7 Pro 64 bit on one SSD and Win 10 Pro 64 bit on another, (I purchased licenses for both) so I don't know what command to use to get the second Dism command to run in Safe Mode for Win 10.
The most important thing I need to know is how to locate the source file for Win 10.
I await further help.
Thanks and regards, Roy
Boggin:
To simplify matters can you disconnect the Win 7 SSD then redo the steps of booting up with the Win 10 disk to run the offboot sfc /scannow ?
During the navigation to the RE it will do a search for OSs which you would select to repair as in that article I'd linked.
As you are booted up outside of both SSDs, the bcdedit cmd could see both Win 7 and Win 10, so in the search for OSs you would need to note the location of Win 10 and click on that before clicking on Next - but with just the one OS, it will default to Win 10, in which case if you miss the search, the bcdedit cmd will default to the Win 10 partition letter for the sfc /scannow.
I suppose you could redo the dism cmd after disconnecting the Win 7 SSD and then see what it reports.
Roy Whitethread:
Boggin, I'm afraid I'm not comfortable with opening the PC case and doing what you suggest, but thanks anyway for the suggestion.
Since all the corrupt files seem to relate to Edge, and to be minor, and bearing in mind that Edge is a work in process, I am going to forget about attempting to repair those files.
I have another problem. I ran the Tweaking.com repair tool in Safe Mode and one Reparse Point error was found. It referred to an infinite loop and mentioned the type was Junction, and I believe it concerned C:\Program Data, but I couldn't see all the path as the window wasn't wide enough.
I used the repair Reparse Point option, but after the repair function completed the same Reparse Point error was shown. I ran the repair Reparse Point option again, several times, but it made no difference.
I then ran the repairs option, but after over 6 hours the repair was still stuck on the first repair, Reset Registry Permissions. Could this be because the repair Reparse Point did not work?
Please advise what I should try next.
Thanks and regards, Roy
Boggin:
I was under the impression that any Reparse errors didn't affect the WR process.
Are you able to stop WR and post a log to show the error message as I think Shane will need to see that to see what is going wrong.
I've just noticed Julian's thread which may have something to do with the Reparse problem, especially if it's compounded with another error you have.
http://www.tweaking.com/forums/index.php/topic,3497.0.html
Roy Whitethread:
Boggin, I'm sorry to say that I'm now confusing myself over which operating system I ran the repairs on. Having said that today I ran the repair tool with Windows 7 running, (I know that isn't recommended) and all 52 items selected completed successfully.
To clear up any confusion I will run the repair tool on Windows 10, and will report back.
Sorry to be a nuisance.
Regards, Roy
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version