I created a VM using Hyper-V-Manager and was able to start the VM and use it for a week.
Today Hyper-V-Manager would not show me my VM.

I checked C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines and was able to find some files and an empty folder:

  • 16B1743A-42BA-4A83-BEFC-847456184561\
  • 16B1743A-42BA-4A83-BEFC-847456184561.vmcx
  • 16B1743A-42BA-4A83-BEFC-847456184561.vmgs
  • 16B1743A-42BA-4A83-BEFC-847456184561.VMRS

The date & time of these files match the time i turned off the machine yesterday. My virtual HDD (the .vhdx file) also exists in its custom place.

The Hyper-V-Manager does not show any options in the 'actions' pane on the right side (stuff like: New, Import Virtual Machine..., Hyper-V Settings..., etc.). The only options it shows is 'Connect to Server...' .

enter image description here

Software Version
Windows 10 Pro
Hyper-V-Manager: Management Console 3.0, Version 1803

  • Cryptic names such as? Can you post a screenshot... you may have some filesystem corruption... – Kinnectus Oct 12 '18 at 11:48

I have two suggestions:

  1. Click that Connect to Server link. You should get a dialog with a radio button for "local computer" and one for "remote computer". Click the former, then click OK and see what happens. If that doesn't work, try choosing "remote computer" and typing localhost into the address box or similar. (I'm nowhere near my Win10 PC at the moment, which is why I can't give you more specific directions.)
  2. Are you running Hyper-V Manager elevated? This is sometimes required for it to be able to connect to the Hyper-V manager service.
  • Unfortunately or rather fortunately, I do not have that problem anymore. Since I can not reproduce the problem, I also can not test your solution. My Computer did not shut down over the weekend, I used the power button to turn it off. After booting the thing, Hyper-V-Manager showed everything, leaving me clueless about the problem and solution. – Human Oct 15 '18 at 8:49

If anyone else is looking at this thread, the issue also may be that the "Hyper-V Virtual Machine Management" Service is not running. If it is turned off, you will get the same symptoms.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.