Migrating back to hyper-v on same machine, now cannot initialize any VMs

[RADRaze2KX]

Hello all,
I was running Hyper-V on my Server 2012 machine and then decided to try VMWare Workstation 9 for testing. I've decided I'd prefer to go back to Hyper-V to utilize RemoteFX. I uninstalled VMWare, ensured all the VT-d / virtualization features were turned on, installed the Hyper-V role again, created a new virtual machine and find that I can't initialize it.

I just get:

Virtual Machine Connection
The application encountered an error while attempting to change the state of '<virtual machine name>'

'<virtual machine name>' could not initialize.

The details include the GUID of the virtual machine.

This happens with all virtual machines; previously existing ones I created in Hyper-V that I'm trying to import, and it happens with any new VM's I try to create. The event viewer shows error 3040 and nothing else. Error 3040 says " '<virtual machine name>' could not initialize. (Virtual machine ID <guid>)

I've ensured everything is turned in the the BIOS, I ran coreinfo before and it showed the hypervisor was running; I turned off the computer, turned it on, disabled everything, turned it off, turned the computer on, booted and ran coreinfo again to verify the settings were turning off correctly; rebooted turned everything on, turned the computer off, turned it back on, ran coreinfo again, it shows the hypervisor is running. Hyper-V opens, it just doesn't initialize any of the VM's.

They all get the same error message and none of them have any details. I'm stuck and inexperienced with Hyper-V; does anybody have any ideas? I'm about ready to wipe/reload the entire system.

 

[Zetro]

Having built a ton of Hyper-V boxes it sounds extremely confused...

As you have already re-installed the Hyper-V role I would probably just wipe/type it at this point

 

[RADRaze2KX]

Whatever it was, it was software-related. I had reset my CMOS and experienced the same issue on default settings after turning all the virtualization features back on.

Having nothing other than a bunch of Steam games installed on the OS drive, I opted to format/reinstall. Upon coming back up, the issue went away.

Now I just need to convert my VMWare drives back to Hyper-V and get the ports forwarded again and we're set. Thanks for the reply, Zetro, it was the best option in this case.