Virtual Machine fails to start after importing on Windows Server 2012

Applies to: Windows Server 2012 DatacenterWindows Server 2012 DatacenterWindows Server 2012 Standard More

Symptoms


A virtual machine that is exported from Windows Server 2012 using a script, fails to start when it is imported on Windows Server 2012 using PowerShell or the User Interface.

Cause


Virtual machines must be imported with the same APIs which were used to export them. Hyper-V PowerShell and User Interface utilize the Hyper-V v2 WMI APIs.

Resolution


Either update export scripts to utilize the WMI v2 export APIs or use a WMI v1 import script to import the virtual machine.