locked
Hyper-V virtual machines disappearing RRS feed

  • Question

  • Running W10 Enterprise TP with no security software, nothing fancy.

    Twice now my Virtual Machine running locally in Hyper-V Manger have disappeared after a reboot. They are still running in the background by their VHDs being in use, but I can't see them to do anything.

    Last time this happened, I had to remove Hyper-V, reboot, re-add Hyper-V, and the VM appeared. However, there was something wrong with the VM so I deleted it and started over.

    Any ideas?


    My idea of a party is a virtualization server and a room of TechNet DVDs

    Tuesday, October 7, 2014 8:43 PM

Answers

  • Can you run this command from PowerShell:

    get-vm | ?{$_.heartbeat -eq "OKApplicationsUnknown"} | Disable-VMIntegrationService "Heartbeat"

    And see if that resolves your problem?


    This posting is provided AS IS with no warranties, and confers no rights. You assume all risk for your use.

    Friday, October 17, 2014 8:30 AM

All replies

  • You might refer to this install,

    There are also follow up tutorials available on the bottom to review,

     http://www.tenforums.com/tutorials/2087-hyper-v-virtualization-setup-use-windows-10-a.html

    Wednesday, October 8, 2014 12:28 AM
  • what version of Hyper-V are you running?

    How can you tell that their VHDs are being used in the background? And finally, when you say they disappear are you talking about their configuration files or just from the Hyper-V manager?

    Wednesday, October 8, 2014 12:31 AM
  • @ThrashZone, Thank you but this is an issue that occurs after it has already been up and running.

    @h_vHE I'm running Windows 10. Interesting: Everything has disappeared from C:\Users\Public\Documents\Hyper-V\. However, the virtual machine "IMAGEBASE" appears in C:\ProgramData\Microsoft\Windows\Hyper-V\. Here's a dir /b /s:

    C:\ProgramData\Microsoft\Windows\Hyper-V\data.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Groups
    C:\ProgramData\Microsoft\Windows\Hyper-V\Groups Cache
    C:\ProgramData\Microsoft\Windows\Hyper-V\IMAGEBASE
    C:\ProgramData\Microsoft\Windows\Hyper-V\Persistent Tasks
    C:\ProgramData\Microsoft\Windows\Hyper-V\Planned Snapshots
    C:\ProgramData\Microsoft\Windows\Hyper-V\Planned Snapshots Cache
    C:\ProgramData\Microsoft\Windows\Hyper-V\Planned Virtual Machines
    C:\ProgramData\Microsoft\Windows\Hyper-V\Planned Virtual Machines Cache
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types
    C:\ProgramData\Microsoft\Windows\Hyper-V\Snapshot Groups
    C:\ProgramData\Microsoft\Windows\Hyper-V\Snapshot Groups Cache
    C:\ProgramData\Microsoft\Windows\Hyper-V\Snapshots
    C:\ProgramData\Microsoft\Windows\Hyper-V\Snapshots Cache
    C:\ProgramData\Microsoft\Windows\Hyper-V\UndoLog Configuration
    C:\ProgramData\Microsoft\Windows\Hyper-V\UndoLog Configuration Cache
    C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines
    C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines Cache
    C:\ProgramData\Microsoft\Windows\Hyper-V\Groups\groupregistry.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Groups Cache\groupregistry.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\IMAGEBASE\Virtual Hard Disks
    C:\ProgramData\Microsoft\Windows\Hyper-V\IMAGEBASE\Virtual Machines
    C:\ProgramData\Microsoft\Windows\Hyper-V\IMAGEBASE\Virtual Hard Disks\IMAGEBASE.vhdx
    C:\ProgramData\Microsoft\Windows\Hyper-V\IMAGEBASE\Virtual Machines\DC334ED4-B8DF-4EFB-A6F0-10C508E7BA54
    C:\ProgramData\Microsoft\Windows\Hyper-V\IMAGEBASE\Virtual Machines\DC334ED4-B8DF-4EFB-A6F0-10C508E7BA54.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\IMAGEBASE\Virtual Machines\DC334ED4-B8DF-4EFB-A6F0-10C508E7BA54.VMRS
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\06FF76FA-2D58-4BAF-9F8D-455773824F37.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\118C3BE5-0D31-4804-85F0-5C6074ABEA8F.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\146C56A0-3546-469B-9737-FCBCF82428F4.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\19839BFF-6F04-4B24-B4B5-1AFCCBE729DE.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\353B3BE8-310C-4CF4-839E-4E1B14616136.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\4764334E-E001-4176-82EE-5594EC9B530E.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\4EA4F71F-16E6-4250-99A8-A2315332CC64.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\6A45335D-4C3A-44B7-B61F-C9808BBDF8ED.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\70BB60D2-A9D3-46AA-B654-3DE53004B4F8.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\72027ECE-E44A-446E-AF2B-8D8C4B8A2279.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\78AA0C27-B2BD-45BA-83D1-5F2A8C4C6656.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\7951A5ED-8DC5-42D7-AA8C-9F14C54CEB84.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\B637F347-6A0E-4DEC-AF52-BD70CB80A21D.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\BDE5D4D6-E450-46D2-B925-976CA3E989B4.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\D45268DA-37C5-44DA-B827-B0C55CCB3BDC.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\D92D268E-9AA8-49DD-8C7D-821CEFB5F597.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\DACDCF3F-6F67-4EB8-A4D0-5D93B48A2468.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\ED28BF6C-B698-4513-B8F4-7BDD01E006A2.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types\F6293891-F32F-4930-B2DB-1A8961D9CB75.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Snapshot Groups\groupregistry.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Snapshot Groups Cache\groupregistry.vmcx
    C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines Cache\DC334ED4-B8DF-4EFB-A6F0-10C508E7BA54
    C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines Cache\DC334ED4-B8DF-4EFB-A6F0-10C508E7BA54.vmcx


    My idea of a party is a virtualization server and a room of TechNet DVDs

    Wednesday, October 8, 2014 5:00 PM
  • In my upgrade, the Hyper-V\Virtual Machines folder had lost its permissions so that I had to retake permissions. Until I did that, it lost my virtual machines repeatedly. After retaking permissions, my virtual machines were in a weird state of flux... I could see them when I looked at a newly created virtual machine's settings, but could not see or start them normally, so I had to wipe the Virtual Machines folder. Since doing that, things have been running properly.
    Wednesday, October 8, 2014 5:47 PM
  • I am seeing exactly the same thing -

    I started from a clean slate on one of my machines:

    • Added a new VM and started installing Ubuntu
    • Right clicked on my machine name and selected "Refresh"
    • All VMs (just the one from above) disappeared (Luckily I still have the connect window open) 
    Monday, October 13, 2014 2:17 PM
  • I am seeing exactly the same thing -

    I started from a clean slate on one of my machines:

    • Added a new VM and started installing Ubuntu
    • Right clicked on my machine name and selected "Refresh"
    • All VMs (just the one from above) disappeared (Luckily I still have the connect window open) 
    Open Windows Explorer and check C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines. If it says you don't have permission to look at it and can take permission, do so. Reboot, and things should be fixed and reliabe again.
    Monday, October 13, 2014 4:02 PM
  • I am seeing the same thing. Permissions appear to be fine.
    Thursday, October 16, 2014 6:02 PM
  • Restarting the Hyper-V Virtual Machine Management services appears to fix it for me, until I close the tool. I also noticed if the VM state in the tool doesn't match the actual VM state. That is an indicator of the problem.
    • Edited by Abe van Niekerk Friday, October 17, 2014 2:31 PM Correct spelling
    Thursday, October 16, 2014 11:28 PM
  • Can you run this command from PowerShell:

    get-vm | ?{$_.heartbeat -eq "OKApplicationsUnknown"} | Disable-VMIntegrationService "Heartbeat"

    And see if that resolves your problem?


    This posting is provided AS IS with no warranties, and confers no rights. You assume all risk for your use.

    Friday, October 17, 2014 8:30 AM
  • That worked. Thank you. PowerShell to the rescue!

    Friday, October 17, 2014 3:51 PM
  • Running this powershell command also fixed the HyperV issue for me - wasn't seeing any newly created vm's.

    Permissions were ok - restarted service numerous times etc etc. HyperV on Windows 10 TP seems to be a bit buggy. 

    Monday, October 20, 2014 10:25 PM
  • I had a similar issue as per the OP.  I ran the same PS command but my VMs did not reappear.  Only after I rebooted my workstation did my VMs show up in the mmc.

    Feedback: My issue started when I accidently clicked on "Remove Server".  When I reconnected to the localhost, the VMs did not populate the mmc.

    Wednesday, January 14, 2015 7:48 PM