5

I have installed Hyper-V manager on Windows 10 pro and have connected to the server which is hosting all virtual machines. By using the Connect to server, I am able to see all the virtual machines. Their state's are running and their status is empty. I try to connect to them but I can't, and ideas? and no error message.

Improve this question
3
  • Have you got any further with this?
    – Anthony Horne
    Commented May 17, 2016 at 5:46
  • It works and does not work = ( . So I made sure that the bios had virtualization enabled. And it seems to have a glitch with RDP console. Some days it works after restart and some days it won't. Sorry.
    – coco minion
    Commented May 19, 2016 at 7:26
  • I seem to have less issues if I start the machine AFTER I connect, i.e. I see the "starting machine", messages, etc. If I start it "right-click >> Start" and then connect afterwards, tickets!! - mostly.
    – Anthony Horne
    Commented May 19, 2016 at 11:30

4 Answers 4

Reset to default
1

I had the same issue initially after I set up a VM yesterday, but got it going after some fiddling around. Unfortunately I can't remember what I did that made the difference though! I think it was related to security. However this morning, after connecting to a different network, it failed again.

My eventual solution: I turned off the Hyper-V features in "Turn Windows features on or off", restarted, then turned them back on again and restarted again. Now everything works fine. Hopefully it will continue to work when I move networks again - will comment here if it doesn't.

Improve this answer
1

Try fixing it by regedit. You will have to go to the - Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services and there you will have to change the value to 0. If it's not working then try using RDP wrapper

Improve this answer
0

I experienced this issue with a local Hyper-V instance on a Windows 10 client while working outside of the office network. In our domain environment, all RDP connections go through an RD Broker. Since I did not have access to the RD Broker, Hyper-V would try to communicate to the RD Broken then fail to connect to the VM's console. I was able to resolve the issue by disabling the RD Proxy to our RD Broker within the registry.

Computer\HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows NT\Terminal Services\UseProxy = 0

My issue may be unique, but it's worth noting during the troubleshooting process of this console connection issue.

Also, if your computer and user account are governed by GPO, your registry tweak on "UseProxy" will probably be reverted.

Improve this answer
1
  • Can you be a little more specific with your detail, consider adding some reference and proof supporting what you state.
    – Vomit IT - Chunky Mess Style
    Commented Oct 4, 2017 at 23:54
0

that works,but I needed to change it a bit. Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services

then i create a new value key UseProxy = 0.

Improve this answer
2
  • 1
    What works? This looks like it might be a comment about Derek Preston's answer.
    – fixer1234
    Commented Apr 13, 2018 at 0:12
  • It is not exactly a comment to Derek Prestonss answer as this one points to a different location of regedit that did work for me. Dereks answer did not work for me.
    – todorm
    Commented Feb 14, 2019 at 16:59

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .