After Interrupted HD Repair Windows 10 wont boot

Night Hawk · 16 Sep 2015

I hate to say this BUT! you may have to choose between the upgrade to repair type install or simply call it a day and slap a "Reset PC" on the system there! That option will be in the Advanced Recovery options while booted live from the 10 media if unable to get into the F8 boot options.

I had some fun trying to build a new BCD store on the second system when knocking out the original 7 Pro primary to move the clean installed 10's second forward and no results at making the drive bootable again until the second clean install got it all together!

That's the sure fire way to get back into 10 without spinning in circles as well as having the need to put everything back on fresh from start again.

That would be the "Windows.old" folder some blog writers say can be renamed to "Windows.personal" or "Windows.backup" to secure personal files in a folder that won't be as easy to dump! The problem is that even after the renaming of that the Disk Cleanup or some 3rd party ware like the "crap cleaner" might end up nuking it anyways!

"all my files are gone!"

JUANNY · 16 Sep 2015

buzzbuzz said:

hi so i ran the start up repair and got this each time
Attachment 37792

i also ran the "bootrec /rebuildbcd" and it wanted to add the old windows 7 install (old.windows )i think the folder was called)

so no luck as yet
:/

Buzz

In theory Startup Repair should be sufficient to repair boot code corruption however in practice ive seen it fail to do that. From your post you only tried the BCD store repair-did you try the full reapir with mbr and boot code if not here is a good starting place Site to do it multiple tries-also with BCD repairs you have to strip attributes from the BCD store because it is a SYSTEM READ ONLY HIDDEN file so bef repair use command attrib BCD -s -h -r -after repair restore the attributes by attrib BCD +s +h +r

Night Hawk · 17 Sep 2015

The usual advice is to run the Startup Repair tool three times while often I was finding that running a second time for refreshing things following a hard boot was needed since a single run of the tool simply wouldn't do the job on it's own. Some have had to run it three or four times in a row in order to get results.

Hopefully what wasn't seen was what happened when I simply went ahead and wiped the first and original primary off of one drive on a second system here to move the second with 10 having a seen a clean install forward and then expanded out to fill the drive in. The first had everything boot related there and the initial efforts to make the second active and build a new BCD store didn't work out.

The problem there is that 8.1 when checking the drive automatically may have nuked all that leaving the drive unbootable as had been seen here when intentionally nuking the first. If anything since the upgrade was incomplete from 7 to 10 booting up with the 7 dvd might hold a better change with 7's Startup Repair option being that it was 7's mbr and BCD information changed or lost. The 10 media wouldn't generally correct any other version's boot loader only see it replaced during the installation of the newer version.