repairing windows 7

C01D4X

Honorable
Dec 27, 2013
18
0
10,510
does something like
DISM /Online /Cleanup-Image /RestoreHealth /Source: d:\sources\install.wim /LimitAccess
exist for windows 7 ?
sfc /scannow returns an error after 6% saying Windows Resource Protection could not perform the requested operation.

[After the windows logo computer stops on a black screen for a while before showing users, and then after login i receive different errors like unresponsive windows services etc. I would like to salvage this windows 7 installation if possible.]
 
Solution
1st - you should check health of your drive with HDtune health (post screenshot).
2nd - run chkdsk on your drive to fix file system errors if any are present.

After that you can boot from windows 7 installation media and choose upgrade option. It basically does the same thing as that command in your post.
You can make image of your windows partition before installation, if you're worried, that it could mess something up.
Edit: Also you'll need to reinstall all windows security updates after that.
1st - you should check health of your drive with HDtune health (post screenshot).
2nd - run chkdsk on your drive to fix file system errors if any are present.

After that you can boot from windows 7 installation media and choose upgrade option. It basically does the same thing as that command in your post.
You can make image of your windows partition before installation, if you're worried, that it could mess something up.
Edit: Also you'll need to reinstall all windows security updates after that.
 
Solution
yes the cause is bad clusters and chkdsk couldn't repair them. Idea is to change the drive after image capture is possible, right now vhd stops at around 6%.

Installed version is win 7 pro sp1 x86. I had the same idea and tried to upgrade to ultimate but it didn't let me for some reason. Will try it again if it's the only way to rewrite system files ..

Edit: I think instead of booting from the installation media, I have to log in to the windows I am upgrading which is proving troublesome
 
I knew the problem came from bad clusters on the drive, but after some times trying to repair the bad clusters i had given up, and turned to repairing windows. Turns out SeaTools for DOS actually works if the drive isn't in really bad shape. After the repair windows was exactly as before, so solved..