Hello everybody,

I've looked far and wide for anybody who has experienced the issue that I am currently dealing with in hopes of not duplicating an already answered question. I found nothing, but please forgive me if it slipped by me.

My issue began after installing VirtualBox to virtualize one of my favorite Linux OS's. Of course, I changed the BCD hypervisorlaunch type to 'off' so I could take advantage of HAV. Everything went great with Virtualbox, and my OS was running perfectly smoothly. Today, I needed to boot into one of my Windows virtual machines in Hyper-V. I changed the hypervisorlaunchtype to 'auto' in BCD and rebooted my machine.

At this point, everything seemed normal. Windows took a few seconds longer to reboot and gave me a message about making configuration changes. After reboot, I logged into my PC and fired up Hyper-V. While one of my VM's was booting, I received multiple errors about why my VM couldn't boot - every single aspect of my VM was getting an error. I am getting 'Failed to allocate resources' errors, 'Insufficient system resources exist to complete the requested service' errors, 'could not find virtual switch' errors.

It seems like they hypervisorlaunchtype did not actually change, but when I tried VirtualBox I received a 'VT-X is not available' error, so Hyper-V has taken ownership of that part of the chip. I rebooted another time after that, then a cold boot after that.

It seems like I'm missing something pretty obvious, but I can't find any information on what it might be. I've never had any issues like this before, and have been using Hyper-V on this laptop for around 9 months. Any help would be greatly appreciated!

I'm running Windows 8.1 Pro x64, 8GB DDR3, Intel i7. Guest machines included Windows XP, Windows 7 and Windows 8.