Fix HyperV Error - Cannot connect to the virtual machine, try to connect again

This video explains how to fix an error with HyperV in Windows 10 devices: "Cannot connect to the virtual machine, try to connect again". It seems to be a bug of Windows 10 which I have noticed in several devices. This method works for sure.

[jbnrusnya_should_be_punished]

Unfortunately, I have not used this feature in Windows until this year, using Virtual Box, vmware or others. They are much slower and require additional software installations. I was amazed at the speed of Hyper-V. But I also encountered a couple of times with the refusal to start, but it was on win11. The first time, I read the error message carefully to the end - the C drive was running out of space. But then, suddenly, there was a "processor configuration" error, even though the number of CPU cores was selected during installation. I had to reduce it and the virtual machine started up again and worked quickly.

[f.eckert]

Thank you so much! After the update from 21H1 to 21H2, I suddenly had this problem and went out of ideas. Luckily I found your video. Works like a charme.

[JamesBunchkles]

Very good guide! Direct and concise. Thank you!

[alokfake]

thank you very much, i just did the step you did in "stop-service vmms / start-service vmms", and it worked right away THANK YOU <3

[TechCare_Aus]

Thanks for the video mate.

However, there is an error in what you are saying around 8:00. You make the point that if you search for 2179 it is now listening after changing the port to 21791. That is incorrect. If you look at the results it doesn't show:

TCP 0.0.0.0:21791
TCP 0.0.0.0:2179

But only TCP 0.0.0.0:21791.

The reason is because you are parsing the results through the find command and dropping the 1 at the end of 2179 still finds the same results as 21791.

If I change the command to:
netstat -ano | find "217"

It still finds:

TCP 0.0.0.0:2179

Have a great day.

[jeremysmith]

Still exists as a bug even now, they're pretty hopeless

[mmarmute]

Thanks so much! Just loved it!
I did appreciate shared information

[farhanshaikh]

hi i am getting this msg "cannot connect to the virtual when i try to clone my virtual machine by running sysprep
can you help

[ziyodillajalilov]

if anyone got start pxe over ipv4 after this fix just disable secure boot, it fixed it for me.

[cmt-quezon]

Listening on both ports 2179 & 21791 but still can't connect. What else seems to be the problem?

[ericdaigneault]

Thank you! that works! I can use my virtual machine now! I subscribe to your channel! Thanks again!

[venkateswararao]

What about remaining vms even though they r working, one vm has issue, if we changed port what about running vms ? There is any disturbance is there for runnyvms?

[ShadowlordDio]

FIRST IN POWERSHELL WRITE >

sc.exe config vmms start=auto

[rob]

so I am not sure what is wrong my registry shows the 2179 but when I double click on listenor port it shows 883 which when I did the netstat option it read something but it is under udp. So how do I fix that part?

[pabss]

Mine is listening on that port yet still not able to connect :s, by that I mean 2179

[vadymvoznyuk]

Hi. I have port opening. But i have issue again. Do you have any ideas?

[HamirpurBoys]

Ports connecting is ok but still the issue persists

[erfanalp]

thank u so much bro thats work <<3