Forum Discussion

M Gibson's avatar
M Gibson
Copper Contributor
Nov 17, 2018

Windows 10 1803 to 1809 Hyper-V - Cannot connect to the virtual machine

Windows 10 1803 to 1809 Hyper-V - Cannot connect to the virtual machine Hi all, After upgrading from Windows 10 1803 to 1809 I am no longer able to connect to any running VM's. I am able to start ...
Vic_U's avatar
Vic_U
Copper Contributor
Sep 30, 2019

I've been having this issue since a couple of weeks now. I'm running 1903.

Any updates?

AMoeller88's avatar
AMoeller88
Copper Contributor
Oct 21, 2019
So i was just digging and found that my Server got a patch that disable Windows Remote Management Service. I re-enable and turn it back to auto-delayed like i had it. Then started the service and everything came right back to life. I also add the Hyper V adapter to public firewall, but i don't think that did anything.
  • Vic_U's avatar
    Vic_U
    Copper Contributor
    Oct 23, 2019

    AMoeller88 That doesn't work for me, unfortunately.

    • M Gibson's avatar
      M Gibson
      Copper Contributor
      Aug 18, 2020

      Vic_U I know this is an old thread I initially started, but I had the exact same issue migrating from Windows 10 1909 to 2004.

       

      I did come across an article with a registry fix, changing the ListenerPort dword from 2179 to 21791 under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization. After stopping/started the hyper-v windows services I was able to connect to the virtual machines as normal.

      • Maitre Elias's avatar
        Maitre Elias
        Copper Contributor
        Jan 06, 2021

        M Gibson correct and thanks for this fix, I changed the ListenerPort dword from 2179 to 21791 and was able to access the new VM. I have the most update-to-date win10 20H version.

        Can somebody from MS indicate why this happens from time to time and if we should keep this different port?

Resources