I have a test platform, which is based on a consumer mainboard and Intel Core i3 CPU. Changing it is not a choice.
This one worked wonderful with Server 2008 R2, including the Hyper-V role. Until I tried to install Server 2012 as upgrade. At first reboot during the installation the system stopped with the single window logo on screen - and only a rollback could bring the machine up again.
Ok, incompatibilities with old drivers or such I thought and performed a clean install. This went well. System was performing great and only waiting to get its jobs. But after adding the Hyper-V role the following reboot again ended in a frozen startup logo. Only safe mode is still working, but an attempt to remove the Hyper-V role from here failed (the wizard did not move on after unselecting the role).
So now I have a useless Server 2012 machine and the choice to go back to Windows Server 2008 R2 or find a way to get Server 2012 up and running again on the platform - with Hyper-V.
Any ideas what is causing the behavior and how to fix it?
Best greetings from Germany
Olaf