How to Fix Hyper V Error: (0x80070539)

Microsoft Hyper-V is utilized for generating VMs, whether they are 32-bit or 64-bit, on the Windows operating system. In Windows 8 and above versions, Hyper-V took over the Windows Virtual PC functionality and became the primary hardware virtualization component for Windows devices.

Hyper-V facilitates the creation of virtual machines on Windows, whether they are client or server systems. The procedure for creating a VM in Hyper-V is fairly straightforward. In addition to other benefits offered by VMs, the ability to migrate or import VMs from one system to another is one of the notable features of this technology.

0x80070539 Hyper-V Error

When importing or migrating a VM, you will get the 0x80070539 Hyper-V Error. The issue might occur during import or when launching or initializing a VM.

How to Fix 0x80070539 Hyper-V Error
How to Fix 0x80070539 Hyper-V Error

The issue occurs due to differences between the environments (either on the same machine or on another PC) from where the VM is copied and where the VM is being imported. Due to this difference, the host machine cannot import or use the security certificates or details of the guest machine.

You may see any of the following errors when this happens:

The security ID structure is invalid (0x80070539)

VM could not initialize 0x80070539

An error occurred while attempting to start the selected virtual machine(s).

‘vm-name’ could not initialize.

An attempt to read or update virtual machine configuration failed.

An attempt to read or update virtual machine configuration failed.

‘vm-name’ could not initialize. (Virtual machine ID)

‘vm-name’ could not read or update virtual machine configuration: The security ID structure is invalid. (0x80070539). (Virtual machine id: your-vm-ID)

How to Fix 0x80070539 Hyper-V Error

Usually, Hyper-V automatically assigns a security ID to a newly created VM but that is not the case with the imported machines. For imported VMs, manually adding the security ID into the VM configurations will do the trick.

Solution 1. Add a Valid User ID to the VM

On the host machine:

  1. Click Windows and search for PowerShell.
  2. Right-click on it and select as Run as Administrator.
    Open Windows PowerShell
    Open Windows PowerShell
  3. Execute the following but remember to replace the name of the VM and Domain and username with the actual details of your VM:
    Grant-VMConnectAccess -VMName <Name of VM that is not starting> -UserName <Domain and username of the current user>
    Run the VMConnectAccess Command
    Run the VMConnectAccess Command
  4. Launch the VM and verify if the problem is solved.

For example, if you have a VM machine named appuals, run the following command:

Grant-VMConnectAccess -VMName " appuals" -UserName ".\Administrator"

Avoid the Error in the Future

Properly migrating a Hyper-V VM is the way to stop the recurrence of the error. You can

  1. Perform Hyper-V Live Migration
  2. Use the Hyper-V Manager
  3. Export and Import the Hyper-V VM
  4. Use the PowerShell
  5. Use a 3rd party App or service

1. Perform Hyper-V Live Migration

  1. Launch Server Manager and go to Tools > Hyper-V Manager.
  2. Right-click on the Hyper-V Manager and select Connect to Server.
    Connect to a Server in the Hyper-V Manager
    Connect to a Server in the Hyper-V Manager
  3. Enter the name of the server and click OK.
  4. Select the server and go to the Virtual Machines pane.
  5. Right-click on the desired VM and select Move.
    Move the VM in the Hyper-V Manager
    Move the VM in the Hyper-V Manager
  6. Follow the Move wizard to complete the process.

2. Use the PowerShell to Move the VM

  1. Launch the PowerShell as an administrator and execute the following:
    Move-VM VMTest TestServer -IncludeStorage -DestinationStoragePath D:\VMTest
  2. Remember to replace VMTest with the required VM and TestServer with the destination server.

3. Export and Import VM

Export VM

  1. Launch the Hyper-V Manager and right-click on VM.
    Export VM in the Hyper-V Manager
    Export VM in the Hyper-V Manager
  2. Click on Export and select the destination of the exported VM.
  3. Click on Export and wait for the completion of the process.

Import VM

  1. Open the Hyper-V Manager and right-click on the destination host.
    Import Virtual Machine in the Hyper-V Manager
    Import Virtual Machine in the Hyper-V Manager
  2. Click on Import VM and follow the on-screen prompts to complete the process.

4. Use the Hyper-V Manager

Add the Destination Server

  1. Launch the Hyper-V Manager and right-click on it.
  2. Open Connect to Server and add the required source/destination servers.

Migrate Hyper-V VM:

  1. Right-click on the required VM and click on Move.
  2. Follow the on-screen prompts to complete the process.

5. Use Another App or Service

The Internet is your best friend to find the one that suits your needs to correctly migrate a Hyper-V VM.

If you have a query or suggestion, we are available in the comments section. 

ABOUT THE AUTHOR

Raza Arshad


Raza Arshad is a certified Google IT Support Professional. With a keen eye for detail and a passion for problem-solving, he excels in identifying and resolving bugs and Windows-related issues. Armed with a deep understanding of computer systems, Raza effortlessly navigates through complexities to pinpoint the root cause and implement effective solutions. His exceptional skills in bug detection and Windows troubleshooting make him a valuable asset in any IT support team.