Upgrading to Windows 10 Anniversary Edition and Hyper-V

4

After updating from Windows 10 to the Anniversary Update (build 1607), I experienced issues with Hyper-V. I was not able to start my virtual machines.

An error message was:

Export failed for virtual machine 'name' (guid) with error 'A virtual disk support provider for the specified file was not found.' (0xC03A0014).

windows-10
hyper-v
windows-10-upgrade
windows-10-v1607
asked on Super User Aug 3, 2016 by Bernard Vander Beken • edited Aug 3, 2016 by magicandre1981

2 Answers

2

Based on my troubleshooting steps, I recommend the following steps to reduce the upgrade pain.

Note: Since I already updated Windows 10 before getting into trouble, I was not able to test this in this order, so your feedback is important.

Before the update

  1. Shutdown all Hyper-V virtual machines.
  2. Go to Start > Turn Windows Features on or off.
  3. Uncheck Hyper-V and confirm the reboot question.

Update Windows

  • Update to Windows 10 Anniversary Edition, you can force this. Note that you have control of when you start the download, however, once the download was done I was not able to postpone the actual update.

After the Windows update

  1. Go to Start > Turn Windows Features on or off.
  2. Check Hyper-V and confirm the reboot question.
  3. After the reboot, start Hyper-V Manager
  4. Hyper-V Manager > Your virtual machine(s) > Right-click to update configuration version.
  5. Hyper-V Manager > Go to Virtual Switch Manager to re-create your virtual LAN and/or WIFI devices.
  6. In your VM configuration, configure the network device from the previous step.
answered on Super User Aug 3, 2016 by Bernard Vander Beken • edited Aug 3, 2016 by Bernard Vander Beken
-1

This Anniversary update is defective and has many issues with hyper-v the solution to this post is to introduce a line on the BCDBoot using the following command:

BCDEDIT /Set hypervisorlaunchtype auto

But there are other problems with this particular version of Windows 10 so I recommend that you stay in version 1106 until it gets fixed

answered on Super User Nov 1, 2016 by Fernando Pineda • edited Nov 2, 2016 by cascer1

User contributions licensed under CC BY-SA 3.0