Startup repair menu doesn't see an operating system

gregrocker,

Does the information in this thread apply to UEFI system boards running Windows 7 64-bit?

Unfortunately, no. All of these repairs are for a Legacy install for MBR disks. The best I can advise for UEFI installs is to run Startup Repair and verbatim search the results.

gregrocker said:

type:

DISKPART
LIST DISK
SELECT DISK 0 (confirm from list this is WIn7 HD #)
LIST PARTITION
SELECT PARTITION # (replace # with WIn7 part #)
ACTIVE
EXIT

This works. Huge thanks. But one note:

After applying the change, Windows reported "BootMgr Missing". But Windows Repair now detected my Win7 install and was now able to fix it.

Thx.

truerock said:

gregrocker,

Does the information in this thread apply to UEFI system boards running Windows 7 64-bit?

I'm running 64bit Win7 with UEFI and was able to fix my Raid-0 C: drive using the above steps.

Please post back a screenshot of Disk Management - Post a Screen Capture Image.

A UEFI install cannot be marked Active because it doesn't even use an MBR, which requires Active flag as a pointer to the System Partition.

Perhaps you have a UEFI system with CSM allowing an MBR bootable disk in it. In this case BIOS setup will be set to CSM with UEFI boot first or not.

gregrocker said:

Perhaps you have a UEFI system with CSM allowing an MBR bootable disk in it.

Yes, this is the case. Sorry for any confusion.

After I started this post I found that Windows 7 does not support UEFI... although UEFI CSM works with Windows 7. Windows 8 does support UEFI... and I expect Windows 9 is where Microsoft will finally get its UEFI act together.

This is what Wikipedia has about UEFI CSM:
**********************************************************
Compatibility Support Module (CSM) booting
For backwards compatibility, most of the UEFI implementations on PC-class machines also support booting in legacy BIOS mode from MBR-partitioned disks, through the Compatibility Support Module (CSM) which provides legacy BIOS compatibility. In that scenario, booting is performed in the same way as on legacy BIOS-based systems, by ignoring the partition table and relying on the content of a boot sector.

BIOS booting from MBR-partitioned disks is commonly called BIOS-MBR, regardless of it being performed on UEFI or legacy BIOS-based systems. As a side note, booting legacy BIOS-based systems from GPT disks is also possible, and it is commonly called BIOS-GPT.

Despite the fact MBR partition tables are required to be fully supported within the UEFI specification, some UEFI firmwares immediately switch to the BIOS-based CSM booting depending on the type of boot disk's partition table, thus preventing UEFI booting to be performed from EFI System partitions on MBR-partitioned disks. Such a scheme is commonly called UEFI-MBR.
********************************************************************************

Apparently when I installed Windows 7 64-bit on my Intel DZ77GA-70K system board in 2012 I ended up with UEFI-MBR.
So, I'm just going to ignore this mess and wait until Windows 9 comes out and then upgrade. Although, I guess it's questionable if Intel will come out with a DZ77GA-70K UEFI update to support Windows 9.

My command prompt won't let me continue after I type diskpart. It just gets stuck at:
Microsoft DiskPart Version 6.1.7601
Copyright (C) 1999-2008 Microsoft Corporation.
On computer: MINWINPC
When the Bios does not recognize the Hard drive the diskpart continues. Any fix? Thanks in advance

Is the HD detected in BIOS Setup? If so test it with makers diagnostics Extended CD scan then wipe it from same disk.

Thank you so much gregrocker! I know this thread is dead, but someone with my problem might run into it.

DISKPART
LIST DISK
SELECT DISK 0 (confirm from list this is WIn7 HD #)
LIST PARTITION
SELECT PARTITION # (replace # with WIn7 part #)
ACTIVE
EXIT

was precisely what I needed to add Windows painlessly to the bootloader (GRUB) again, after I had moved my primary windows partition from inside debian. I am now glad that I ran into that error, since a normal startup repair would probably have overwritten GRUB with the Windows bootloader.