Hyper-V Did Not Find Virtual Machines to Import – Error 32784

When importing a VM into Windows Server 2012 that was exported from Windows 2012 R2 you will be unable to import the VM.  If you import the VM using PowerShell’s Import-VM cmdlet the error message is not very descriptive – “The operation cannot be performed because the object is not in a valid state”.  You will also find EventID 15040 in the VMMS event log. 

The operation cannot be performed because the object is not in a valid state

The full error message for reference:

Import-VM '.\Virtual Machines\F5164EF0-5F87-40F1-9872-C669406A18A5.XML'

Import-VM : Failed to import a virtual machine.

The operation cannot be performed because the object is not in a valid state.

At line:1 char:1

+ Import-VM '.\Virtual Machines\F5164EF0-5F87-40F1-9872-C669406A18A5.XML'

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidOperation: (Microsoft.HyperV.PowerShell.VMTask:VMTask) [Import-VM], Virtualizatio


+ FullyQualifiedErrorId : InvalidObjectState,Microsoft.HyperV.PowerShell.Commands.ImportVMCommand


If you look in the Microsoft-Windows-Hyper-V-VMMS/Admin event log, EventID 15040 should be present, stating that “Failed to import a virtual machine”. 

EventID 15040 Failed to import a virtual machine

Not much to go on and troubleshoot there…

Let’s retry this using the GUI…..

If you used the Hyper-V Manager to import the same VM it provides a clue:

Importing 2012 R2 Into 2012 Using Hyper-V Manager

Importing 2012 R2 Into 2012 Using Hyper-V Manager


Hyper-V Did Not Find Virtual Machines To Import From Location Error 32784

Now that we have an error code, we can plug that into our favourite search engine.  Which should lead you to the following KB article:

KB 2868279 Moving a virtual machine (VM) from a Windows Server 2012 R2 Hyper-V host to a Windows Server 2012 Hyper-V host is not a supported scenario under any circumstances.

I wanted to publish this quick post so folks who gravitate to importing via PowerShell can search and easily find the cause of the issue since it is the GUI that provides the clue.



Comments (9)
  1. anonymouscommenter says:

    A virtual machine from Windows Server 2012 R2 cannot be directly imported into Windows Server 2012. This

  2. Thanks for sharing Rhoderick. Have a nice day.

  3. Sam Boutros says:

    perhaps not direct import export, but we can:
    1. Remove the integration services from the VM,
    2. Build a new VM on 2012 host using the same VHD(x) disks
    but I cannot imagine why would anyone want to downgrade from 2012 R2 to 2012..

  4. Exactly Sam, and that’s what’s in here

    In terms of wanting this, its kinda clear cut on the import/export side. However this also applies to live migration too – so if someone moved the VM over to test out a net new 2012 R2 box then it cannot move back to 2012.

    I do agree – In general it is normally upwards and onwards when it comes to such things.


  5. anonymouscommenter says:

    One scenario I ran into with this….I had pre-configured a server using hyper-v manager on my windows 8.1 machine to be imported later at the office into my 2012 hyper-v server……however i got the same error messages using the powershell method and
    using the gui.

    Windows 8.1 and Server 2012 r2 have this issue with backward compatibility on importing vm’s.

  6. anonymouscommenter says:

    Very similar scenario as Chris. I just made new VM on the 2012 (not R2) server and copied the disk from the R2 VM then attached the copied disk to the non R2 VM. Booted the VM without issue. Very seldom do I use export. I organize my VM config files and
    disks differently than the default separation so to clone, copy, export a VM all I do is copy the folder that houses the folders for configuration and disk files to another server and import.

Comments are closed.

Skip to main content