Windows 8 stops booting after installation of Visual Studio 2012 Desktop

bootvisual studio 2012windows 8

I installed "Visual Studio 2012 Express Desktop" on my "Windows 8 Pro". The installer succeeded and told me to restart the system. I obeyed.

Now the system hangs somewhere in the bootprocess and my eyes won't stop bleeding while looking at the dancing little dots (aka the "wait" animation).

After 2 resets the automatic recovery triggered and Windows 8 healed itself. Windows 8 booted again, I was able to login. I tried to launch Visual Studio, but some .dll was missing. I repeaired the installation via the installer. The installer succeeded and told me to restart the system. I obeyed, again.

And, again, now my eyes bleed again while looking at the dancing dots.

What is the problem? What is the best way to diagnose this?

Update: Maybe related, after the 2nd restore I get some 'COM surrogate crashed' messages from the picture viewer. And the "remove programs" panel takes ages to load.

Update2: After several cleanups / recovery / reinstall etc: VStudio now works. Boot-hanging might be coincidence and not corelation. I vote for closing this question, might be usefull for others in terms of 'it was asked but can't be answered'.

Best Answer

There is a known issue with the Gigabyte motherboard, caused by an incompatibility of its on board USB3 controller.

See the last tip in the info below, from the emulator faq:

Problem: Installation of the SDK causes Windows 8 to fail to reboot.

This item is included in this troubleshooter because there is a known issue with Hyper-V interacting with third party software, and Hyper-V is used by the Emulator.

When this happens, restore your system by using the F8 option at reboot and choose the last known good OS instance.

Try manually installing the Hyper-V Windows feature before installing the SDK, via Control Panel->Programs and Features, “Turn Windows features on or off”.
Check whether you have any BIOS setting similar to: "Limit CPUID Maximum Value to 3". If yes, try setting it to disabled and see if that helps.

One possible root cause of this is if you are using a Gigabyte motherboard’s USB3 controller.

More information: Boot failure after installation of Hyper-V role on Gigabyte systems

http://social.msdn.microsoft.com/Forums/en-US/wptools/thread/75251ed8-22a3-4387-bfed-94bd2aa8c6ac