Boot Parttion Corruption - Almost fixed just need a little more help

Never mind:

On a Legacy install to MBR disk, confirm the Partition Marked Active is the 100mb System Reserved (preferred if you have it) or Windows 7 partition (if you don't), run Startup Repair repeatedly up to 3 separate times with reboots in between each - no matter what it reports. If both the System Active and Win7 partitions are on the same hard drive then unplug all other drives to do these repairs.

On some PC's the Recovery partition or an earlier installed OS used in a Dual Boot will hold the Active flag. If another partition than System Reserved or C holds the Active flag and you know this is how it was set up, then go ahead with the repairs. If not skip to Step 9 to get more help since Win7 will not repair unless the correct partition is Set Active. Only the System partition booting the OS should be marked Active.

Yes, you've got it. Plugging it into DISK0 is even better since then it will be in a position where no repair can derail the System boot again.

OK I did as asked, as soon as I selected Country "US" it searches for Windows install(s), stated had errors, repair/start (this is because the second HDD 150 no longer found, I did as asked. I ran repair 3 times with reboots after each run as directed.

This did not work comes up with "Starting Windows" no logo and hangs...

Check out the snap shots I took, pay close attention to the date and TIMES of the boot files, in most cases it does not change either date/time, and 1 is really funky, it is the snapshot with the clock visible.

Enjoy:









So I am screwed, I have no viruses no adware because these are the firsts steps to check using several utilities.

2 questions please, as we know the partition was and still is Active, should I have run diskpart and deactivated the drive before I did the repair? and what if I where to boot off the DVD and copied the GOOD boot partition to the BAD? Would that work? Of course I would copy all file & folder (on the BAD part) into a new delete folder then run xcopy cmd.

After which I would immediately run the repair again and hope that it would take care of the Attribs and any hiding of files.

If this does not work or I am told I cannot do it, my next step is to try an in-place repair (again) the only problem is that I am going to have to have the 150 drive plugged in and booted into the 300gb, will this fix the bad part? who knows!!!

Please let me know what you think, Thanks Steve

..

I would abandon the unnecessarily large 16gb boot partition to move the bootmgr into C so it boots itself.

Plug the old drive back in to where it will start, then move Bootmgr - Move to C with EasyBCD
to let free EasyBCD automate the procedure. Then power down to change the boot drive back to C to check if it will start. If not then Mark C Partition Active and run Startup Repair - Run 3 Separate Times.

I finally was able to get back to this and have fixed the issue, see here:

[SOLVED] Windows 10 destroyed Windows 7 - Sysnative Forums