SSD will only allow UEFI boot and not show up as a Legacy Boot option.

[Ariel_Bar]

Hi,

My comany is purchasing HP EliteDesk 800 G2, some comes with HDD and some with SSD.

We deploy Windows 7 x64 using SCCM using legacy boot.

On a machine with HDD installed I can configure the boot options to use legacy boot, but when I replace the disk to a SSD drive the only boot option for this drive is UEFI.

That causes the deployment to fail because the drive need to be partitioned as GPT.

On the other hand, if I disable legacy boot, PXE boot to UEFI and partition the disk as GPT, after the image deployment the disk is unable to boot with 0xc000000d error (I imagine the cause is Windows 7 support becuase it does work on Windows 8.1).

Bottom line, I can install Windows 7 on a HP EliteDesk 800 G2 only if legacy boot is enabled and I partition the disk as UEFI.

Is there any way of forcing the SSD to boot as legacy and not UEFI?

Is this issue caused by the workstation or is it enforced by the SSD?

thanks.

[Jay_101]

Greetings,

You disabled secure boot and enabled legacy boot. Have you tried clearing HP security keys? You're installing your own drivers.

Why are you partitioning the disc as UEFI prior to the network installation if the image requires MBR? The image should set the disc as MBR and install the operating system.

Did you disable fast boot?

Look, I work with consumer PC's so I am not familiar with the EliteDesk.

I have never had a problem deploying a MBR image on an SSD using a disc, USB, or a network image.

Did you contact HP Enterprise Support?

To the best of my knowledge SSD's will run on MBR or GPT. The SSD will adapt to the installation media. I also can't see why a network image deployment would require GPT. 

Maybe I am not understanding your problem. But I see inconsistencies in some of the steps you have taken, or your description of these steps, so far. It may be a mis-communication between us. 

It's got to be a BIOS setting.

Jay

[Ariel_Bar · Accepted solution]

Hi Jay,

I appreciate you trying to help.

I guess there is some miscommunication because this is an enterprise issue and there are other technical components involved that I did not include.

After some more investigation it seems that this issue occurs with a specific model of SSD.

We will just have to wait for HP support.

thanks.