Hi everyone,

I have an issue when installing Hyper-V role from a fresh Windows Server 2012 installation.

During the deployment of the role, Windows reboots but after the reboot, Windows does not manage to get to the login screen.

Hardware assisted virtualization and data execution prevention are both enabled in the BIOS when the problem occurs. But, disabling one of these 2 options let Windows start normally (with Hyper-V not started tough). I can also start in safe mode.

Can it be a gigantic startup time (I tried to wait for ~1 hour) or an unbeatable compatibility problem with my motherboard ?

Here's a listing of my setup.

-Windows Server 2012 Standard Edition FRESH installation (with a GUI) with a genuine product key 

-Motherboard: Gigabyte GA-P55A-UD5 (BIOS: F12 => the latest non beta)

-Proc: i5 750 @ 2.66Ghz (VT-x & EDB available)

EDIT: SLAT is also available for my CPU.

• Edited by Lolz Bar 15 hours 21 minutes ago

SLAT is not required for Server, just for client.

Have you cold booted after enabling data execution prevention?  (cold boot is required to initialize it).

And, have you searched the Hyper-V forum for the long history of gigabyte motherboards?

http://social.technet.microsoft.com/Forums/en-US/home?forum=winserverhyperv

Try disabling the USB 3  option in the BIOS.

• Proposed as answer by Andre.ZieglerMicrosoft community contributor 5 hours 46 minutes ago
• Marked as answer by Lolz Bar 4 hours 30 minutes ago

Wow, this actually worked (I disabled the USB3 option at the same time I installed a few MINOR Windows Update, so I'm not 100% sure)

But I do not understand why would USB3 prevent Hyper-V from doing its job properly, can you explain a little bit ? :)

By the way, with or without explainations, thanks a lot !