Windows 10 Preview – VMs Missing In Hyper-V Manager

After updating my Windows 8.1 machine to the Windows 10 preview, some of my VMs were no longer visible in the Hyper-V Manager.  Prior to powering on some VMs, all of them were visible.  After powering on, some VMs disappeared in the Hyper-V Manager console. 

In the screen shot below, there should be 10 VMs displayed which have the prefix of “HA”.

Honest Guv, There Really Are More VMs.....

Restarting the Virtual Machine management service made no difference.  The VMs that were not displayed remain in that state, i.e. hidden.

But they are certainly there! Looking in PowerShell using Get-VM showed all the VMs:

PowerShell Shows All VMs

They were still manageable via PowerShell. 

Get-VM | Where {$_.State –eq “Running”}

Save VM State Using PowerShell

If they were saved using PowerShell, then they appear in the GUI once again:

Get-VM | Where {$_.State –eq “Running”}  | Save-VM


After they had been saved, simply refreshing the Hyper-V Manager made them all re-appear.

Now You See Them - All VMs Are Visible When They Are Saved

If the VMs were started up again, some of them would “stick” at the starting phase.  This is highlighted in the screenshot blow.

Why Is This VM Stuck In the Starting Phase?

Despite being marked with a status of “Starting” all VMs were all successfully started and were fully accessible.  Refreshing the Hyper-V Manager would then cause VMs to again disappear. 


OK – what is up with that VM?  Why is it saying it is stuck starting, but the VM is actually running?  Why is it not reporting it is in a happy place?


Checking VM Integration Services & Heartbeat

If we look at the VM Integration Services, there is a difference between a VM that is happy and the one that was stuck in starting phase.  Note the highlighted areas below:

Get-VMIntegrationService –VMName “VMName”

Comapring A VM Stuck In Starting With One That Transitions As Expected

Digging deeper, how does the VM heartbeat appear for these VMs?

Get-VM  HA* | Select Name,  Heartbeat

Using PowerShell To Check VM Heartbeat

As indicated with the big red arrow, there is a bit of a difference…..


Fixing This Up

In the Windows 10 Preview, there is currently an issue if the VM heartbeat is reported as unknown.  In this case, VMs do not appear in the Hyper-V Management console.

To workaround this issue, disable the heartbeat for these VMs.  The following command will disable the heartbeat for VMs that have a status of “OKApplicationsUnknown”.

Get-VM  | Where {$_.Heartbeat -eq "OkApplicationsUnknown"} | Disable-VMIntegrationService Heartbeat

After running the above command and refreshing the Hyper-V Manager the VMs are now visible!  The naughty VM listed above is now in the running state and all is good!

Windows 10 Hyper-V VMs Now Visible

Please remember that this is the initial preview of Windows 10, and that this article was written specifically for the preview.



Comments (11)
  1. Kevin Whiley says:

    Great Post!

    this saved me hours of work thanks

  2. Steve Hose says:

    Thanks for the article. It was driving me nuts and you pointed me in the right direction.

  3. Ivan Carlos says:

    You sir, are my new hero for today, thank you kindly.

  4. Little Fire says:


  5. Chris Ayres says:

    This has literally saved me from going bald from pulling my hair out. I’ve been plagued by this for many weeks now! Thank you so much 🙂

  6. John Nibarger says:

    i would recommend running Windows 10 Preview INSIDE VM, not updating an existing System. I put Win10 VM in Hyper-V on my Win8.1 system…seems to run fine.

  7. NDao says:

    Hyper-V Manager gave me the same problem and your article solved it. Thanks!

  8. Stra says:

    Lifesaver, thanks!

  9. Daniel says:

    Hi I would like you to help me with the process of my lon-svr1 virtual machine using hyper V manager to the state of the desktop background being black and written on the desktop "LON-SVR1 logged on: ………./Administrator, please help with the step
    by step
    My email

  10. Gizay D says:


Comments are closed.

Skip to main content