BootMgr Missing after Easus Repart of C - No Repair Tool is Working

Hello all, I hope someone can help me.

This is a neighbor's desktop (now in my possession to fix): HP Premier Slimline 1TB EFI/GPT Partitioned like this:

C (OS-W764) 100GB
D (Hidden HP Recovery Part 2GB)
E (DVD ROM)
F Pictures 200GB
G Another... 200GB
H Misc.... 500GB

She wanted to take 100GB from G and add it to C. So I used Easus to do that. All went well moving it from G to F, but then when adding the unallocated space to C, instead of Easus intercepting the reboot, the Windows Recovery routine kicked in and said it needed to repair Windows... when it rebooted it went into a DOS routine searching for DHCP.... until it finally said there was no bootable disc.

I ran the repair tool a few times with the same result. Finally, I booted from a Paragon rescue CD to restore a backup from an external drive. The operation completed but when I rebooted I got "Missing Boot Manager" error.

And now when I try to boot from the retail W7 CD or a Windows repair CD, I get "this disc not compatible with your system". So I cannot get to a command prompt to try the fix mbr commands.

All the partitions and data are there... it's just the MBR messed up (or the GUID or whatever a GPT disk uses). Obviously Easus was not able to finish its job of resizing C.... Unless it's just the BM messed up. So ...

1. Does anyone know of a BOOTABLE CD tool that will repair the Boot Manager for GPT disks?

2. If I have to reformat the drive and start over, which BOOTABLE tool should I use? (I have never worked with a EFI/GUID/GPT disk.) Again, I cannot use a tool inside Windows... it has to be from a bootable CD/DVD.

Any help at all will be truly appreciated.

Kaktussoft said:

C (OS-W764) 100GB is primary and active?

And now when I try to boot from the retail Windows 7 CD or a Windows repair CD, I get "this disc not compatible with your system". So I cannot get to a command prompt to try the fix mbr commands.

it lists win7 as installed OS?

It doesn't get that far. It asks for US keyboard, then when I click yes I get the error that it is not compatible with my system. I read somewhere this is because of the OEMs hidden recovery partition. ?

Note I am clueless when it comes to recovery partitions and GUID... my computers still use MBR and I wiped the drives when new to get RID of the hidden recovery part. But this is her computer and it's a 1TB GPT with the hidden recovery part in D.

Kaktussoft said:

instead of Easus intercepting the reboot, the Windows Recovery routine kicked in and said it needed to repair Windows... when it rebooted it went into a DOS routine searching for DHCP.... until it finally said there was no bootable disc.

DOS routine searching for DHCP?? Looks like it is trying network boot(?) What is boot priority in BIOS?

Yes, when the drive would not boot, it started going down the list in BIOS looking for subsequent drives and found none, of course, b/c the internal was supposed to boot.

Did you restore an image to the 100GB partition (win7 OS). Very sure it was an win7 partition backup?

I think I used the wrong language last night... I did a Recovery in Paragon, not a Restore. The paragon archive was a single archive of the entire drive with all partitions, and I used the Recovery option to restore that archive to the entire drive.

I wanted to do a restore of C alone, and looked at that first, but wasn't sure what was screwed up with Easus not completing its re-size of C, or where/how the boot records work on a drive with GUID and a hidden recovery partition... AND I had already resized a few of the partitions leading up to this, and didn't want THAT to screw up a new boot, so I thought it safer and a better bet to let Paragon put the entire archive/drive back rather than cherry picking.

Kaktussoft said:

Command Prompt at Startup option ONE. then

Code:

attrib c:\bootmgr
attrib d:\bootmgr
attrib e:\bootmgr
attrib f:\bootmgr
attrib g:\bootmgr
attrib h:\bootmgr

Which drive letter(s) has bootmgr?

Code:

diskpart
list vol
exit

Tell me if it's the 100GB, 2GB or ...partition

Diskpart reported the sizes different than I listed. See : View image: diskpart sm Boot manager was found in the C (OS) 75GB and the (G) HP_Recovery partitions.

Note there is also a 100MB SYSTEM FAT32 hidden partition that has a boot folder and boot manager in it, I saw from using MiniTool.... but since it is not assigned a drive letter I could not have diskpart check that partition. All other part's are NTFS.

Also, it does NOT appear the HP_Recovery part is hidden afterall.

Thanks to EVERYONE for their replies!!!