How can I install Windows 7 x64 on GUID partition table? My motherboard has UEFI. I tried using Ubuntu to create the GPT and NTFS partition on it, but Windows 7 just says

Windows cannot be installed to this disk. The selected disk is of the GPT partition style

I found this: Use the Diskpart.efi Utility to Create a GUID Partition Table Partition on a Raw Disk in Windows – but all diskpart commands in it don't work, it seems its a different version of diskpart.

How can I make this work?

  • See this document...msdn.microsoft.com/en-us/windows/hardware/gg463140.aspx – Moab Aug 16 '11 at 20:56
  • @Moab, I created the partitions as it says, but I don't see the UEFI boot option for the installation cd – Dani Aug 16 '11 at 21:05
  • 1
    I suppose GUID booting could be disabled or blocked in the bios. – Moab Aug 16 '11 at 21:12
  • 2
    Make sure you boot the installer through UEFI. Windows CDs come with both El Torito (legacy BIOS) and UEFI bootloaders; I'm not sure if it makes a difference, but can't hurt to try. – grawity Aug 16 '11 at 21:38
  • 3

Microsoft erroneously conflates has an EFI partitioned hard disc with has EFI firmware. This is, of course, clearly wrong. It's quite possible — and indeed is becoming ever more desirable these days — to have an EFI partitioned disc on a machine that has old non-EFI firmware.

Moreover, as of revision 2.3.1 of the UEFI Specification, the EFI partition table has a "startable" attribute defined for partitions and it is possible to even bootstrap from EFI partitioned discs on a machine that has old non-EFI firmware. Old-style PC98 MBR bootstrap programs can look for partitions marked with the "startable" attribute in the EFI partition table and bootstrap the flagged partition's Volume Boot Record bootstrap program in the old PC98 way.

There are only two sources of such EFI-partitioning-aware MBR bootstrap programs right now:

  • I've written and published one.
  • The so-called "GPT" MBR boostrap in SYSLINUX, written by H. Peter Anvin, is another.

One of the several consequences of Microsoft's error is that if the Windows NT 6.1 install disc is bootstrapped in the old PC98 way, as you've done, the Windows NT 6.1 installer will think that there's old PC98 firmware, and so declare that it cannot be installed to EFI partitioned hard discs. The Windows NT 6.1 installer has to be invoked from an install medium that has in turn been bootstrapped from new EFI firmware, in order for it to accept the idea of installing Windows NT 6.1 to a disc partitioned with the new EFI partitioning scheme.

As the Microsoft documentation explains, the installation CD-ROM is in fact dual-boot. A machine with old PC98 firmware will bootstrap one operating system image and installation program; and a machine with new EFI firmware will bootstrap another. A machine with a compatibility support module can bootstrap an installation medium either way. One has to instruct one's firmware to bootstrap the installation CD-ROM in the right way, the new EFI way.

As Rod Smith explains, one can also, alternatively, manually construct a non-dual-boot Windows NT 6.1 install disc that only bootstraps in the new EFI way.

Further reading

  • 1
    I don't think it's so relevant for this question... The OP has UEFI already. Yours would be more applicable on some of the other questions where your answers seem to have vanished all of a sudden – Milind R Feb 10 '14 at 5:16

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.