Windows 10: Win10Pro: Updated to 1703 - Hyper-V 0x80070005 Error on VM

I've been running Windows Home Server 2011 in VM on my Windows 10 Pro Machine for a couple years without a hitch. Once I updated to 1703 last week, I'm receiving error 0x80070005 (see picture) and the VM won't start. Does anyone know of a work-around that won't entail me either having to downgrade or reinstalling the VM?

Thank you very much!




:)

 

Hyper-V Virtual Machines Fail to Start and Initialize after Windows 10 Upgrade from Windows 8.1

I setup a vm on win8.1.2 using the exact same settings I used on win10, and the vm started to boot (it did not totally boot beacuase there was no OS, but I got expected results) there is definitely an issue with win10 hyper-v. I did notice that disabling
the hyper-v remotfx3d entry in device manager seems to allow the vm to boot further before erroring out with the same error as in OP

 

Hyper-V Stopped Working on Windows 10 Pro

Hello,

I had successfully installed and ran a VM on Hyper-V when I first bought this laptop, however it seems after the Fall update Hyper-V won't start any VMs and gives me the follow error. Anyone know how to fix this?

 

Try this:

Backup the VHD / VHDX and possible AVHD / AVHDX (checkpoint) files of your VM.

Open VM settings, select DVD Drive. If an ISO is added as CD/DVD, remove it selecting None or completely removing CD/DVD drive:





On left pane, select Hard Drive. Select New and go through New Virtual Hard Disk Wizard to set up a temporary, dynamically expanding dummy VHD with default settings:





Save settings, run VM which now fails to boot.

Turn of VM, in settings add a CD or DVD (ISO) if needed, change VHD back to original VHD or VHDX. Notice that if checkpoint exists, the correct VHD to select here is the most current AVHD or AVHDX file, the one with latest time stamp.

The above process rewrites file read / write permissions for VM configuration file. Come back if this does not help, we'll think something else.

 

Thank you very much! That worked.

 

You are welcome *Smile

Forgot to mention in my previous post that you can delete the temporary VHD you created when done.