Need help resolving Hyperv error

[warpig]

With the release of the Windows 10 demo, I decided to enable Windows 8 hyperv to check it out. However, after insuring virtualization was enabled in my bios and attempting to create a virtual machine, I encountered the following error: 

 

Hyperv encountered an error while configuring the network on (VM Name) 

Hyperv encountered an error trying to access an object on computer localhost because the object was not found. The object might have been deleted, or you might not have permission to perform the task. Verify that the Virtual machine management service is running. If the service is running, try running the task as admin. (Already tried) 

 

In addition, when trying to open the virtual switch manager, I receive the error: 

An Error occurred while trying to retrieve a list of virtual switches.

The operation on computer 'localhost' failed

 

I've tried running with virtualization on and off, as admin, and with different user accounts, and have gotten the same result. 

 

On a somewhat related note, when attempting to create a VM in virtualbox, I am only given the option to create 32 bit VMs, regardless of whether or not virtualization was enabled. When I attempt to install windows 10 in one of these 32 bit VMs, I am told that my CPU does not support PAE. 

 

I have had little sucess with googling the errors, any help would be highly appreciated. 

 

Here are my system specs, should they prove relevant: 

• • CPU
    AMD Phenom 2 x4 965
  • Motherboard
    Asus M5A99FX Pro R2.0
  • RAM
    8gb corsair vengeance @ 1866mhz
  • GPU
    MSI 7950 Twin-Frozr boost
  • Case
    NZXT Tempest 410
  • Storage
    2x WD caviar blue 500gb + 1 samsung 650gb (+ 1x 60gb kingston ssdnow when it's not in my laptop)
  • PSU
    Corsair CX750
  • Display(s)
    1x Dell 2007fp 1x Dell 1907fp
  • Cooling
    Cooler Master Hyper 212+
  • Keyboard
    A Dell found in a trashbin
  • Mouse
    Steelseries Diablo III mouse
  • Sound
    Schiit Modi + Vali, Hifiman HE-300, Audio Technica ATH-M50
  • Operating System
    Windows 8.1 pro

  Wifi Card TP-LINK TG-3269 10/100/1000Mbps Gigabit PCI Network Adapter/Card

 

[GoodBytes]

Did you restart your computer?

The locolhost problem, is because the way Hyper-V works, is that you remote desktop to the VM, well a modified version of remote desktop which give you menu options to control the system (insert disk, restart, turn off, install the hyper-V software on the OS, etc.)

So it telling you it can;t connect, probably due to a conflict where it already started but crashed on the back or something.

Under Hyper-V you can install a 64-bit OS.

[warpig]

bump