Reformatted PC, Unable to boot from C:, Bootmgr missing error

KGR772

Commendable
Dec 2, 2016
2
0
1,510
I reformatted my PC today to get a clean slate. I used a USB drive loaded with an ISO windows 7 and installed it onto my SSD (C:) drive (Disk 1) while Disk 0 is my HDD with nothing on it. The install ran without an issue. Once it was all set and done I restarted and changed the boot priority from my USB drive to my SDD and removed the USB drive. Upon restarting I got a "Bootmgr missing" error. Reversed the priority and put the USB back in and it worked.

The C: drive is Healthy (Boot, Page File, Active, Crash Dump, Primary Partition)

I checked the C: and the bootmgr file is there physically. I checked through cmd to see what was up and I got this:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.


C:\Windows\system32>bcdedit

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {bc36bbea-b8fb-11e6-ad52-c40f60cbf56d}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {bc36bbec-b8fb-11e6-ad52-c40f60cbf56d}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {bc36bbea-b8fb-11e6-ad52-c40f60cbf56d}
nx OptIn

C:\Windows\system32>

I kind of am at a loss as what to do. I tried just reformatting again but to no avail. I looked around for answers but none seem to address my situation.
 

KGR772

Commendable
Dec 2, 2016
2
0
1,510
Here is what I have tried since:
1. Double checked boot sequence both with and without USB install drive. The USB drive must be primary in the boot sequence.
2. Start up repair found no issues.
3. Created a new partition boot sector which didn't make a change.
4. Rebuilt boot configuration data which did change the fact that one (1) windows install was identified however did not fix the bootmgr issue.