Quote: Originally Posted by Amadeus
Tried the SFC /scannnow from c:\ and c:\windows\system32. Interesting response in both instances. "There is a system repair pending which requires reboot to complete. Restart Windows and run SFC again."
Now the question is how do I initiate the repair? Rebooted four times with no change.
Found this, and the way I interpret it is:
When you booted from DVD, you were not booting a 'real' Windows 7 installation --
you are "booting" an image-file. ie, like a Zip file, that has to be "unpacked" to
execute Windows 7 commands.
The Cmd-prompt is one of those unpacked cmds, run from the image-file.
When you attempted to run C:\win\sys32\sfc.exe, the 'unpacked-cmd-prompt' KNOWS
that it is running from a .wim image-file,
i.e.: You cannot use the System File Checker tool to verify or to repair Windows Vista if Windows Vista is in a mounted image file or in a bootable WIM file
You cannot use the System File Checker tool to verify or to repair ...
This process will take some time. There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again.
So much for that.
This also implies that the only 'trusted
' programs (running from the .wim image file) are those found on DVD, or, if booted successfully to the bootmgr screen (Select an OS), those manually put on C:\Recovery for that express purpose.
The recovery tools put on C:\Recovery are not automatically placed on that menu.
Which brings us to Antman
's link, posted above, and siw2
's write-up on how this is done.
Once accomplished, it will simply be a copy of the recovery-tools on the DVD, but loaded from the C: HDD instead.
Since none of these worked for you from the DVD, there's not much sense in putting a menu entry in bootmgr to accomplish the same thing.
The menu entry is surely "booted" from an image-file also, like the DVD.
Unless others who have "been-there, done-that" could jump in here, I'd try the DVD repair/restore functions another time or two from DVD, then go for the format/install route. I'd NOT do a 'Quick' format, though...
I would personally also try a thing or 2, 'off-the-wall' (and quasi-rational) such as running BCDEdit,
and say, change the displayed 'label' by putting the identical same entry where it currently is,
in the hopes that he'll write exactly what he began with, with the original being saved as a .BAK file. This way, the "new" BCD-store file will be on a different physical place on the disk.
Or, because I sometimes do stuff like this, is use 'diskpart' to create a 30 GB .vhd file and install Windows 7 (ULTIMATE only) into that. There's an excellent tutorial on "installing to a vhd" on this board.
This takes time to format the .vhd, install, etc. but I just might do it, just for grins.
This would leave you with still only 1 partition, but with 2 installations: the bad one in C:\Windows and another in a .vhd file. Theoretically
, the .vhd would be bootable as the first entry in Bootmgr with the bad install as the second entry.
OTOH, it might not work...
The only thing you could gain from this is to have a "real" functional bootable Windows 7 (vice .wim image file), I think, which might
allow you to do troubleshooting on the misfit C:\Windows.
Sort of a "BartPE" on the same HDD, contained as a single .vhd file...
Kind of gutsy, and, wandering into the unknown... Also, there are some limitations on vhd installations.
There's still the option to 'squeeze' the one partition down, creating new space for a 2nd partition, and a 2nd installation put there, as you were pondering before.