Hyper-V not connecting to Virtual Machine in Windows 10
up vote
3
down vote
favorite
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.
windows-10 virtual-machine virtualization hyper-v
asked Feb 25 '16 at 17:17
coco minion
2116
add a comment |
up vote
3
down vote
favorite
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.
windows-10 virtual-machine virtualization hyper-v
asked Feb 25 '16 at 17:17
coco minion
2116
Have you got any further with this?
– Anthony Horne
May 17 '16 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
May 19 '16 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
May 19 '16 at 11:30
add a comment |
up vote
3
down vote
favorite
up vote
3
down vote
favorite
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.
windows-10 virtual-machine virtualization hyper-v
asked Feb 25 '16 at 17:17
coco minion
2116
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.
windows-10 virtual-machine virtualization hyper-v
windows-10 virtual-machine virtualization hyper-v
asked Feb 25 '16 at 17:17
coco minion
2116
asked Feb 25 '16 at 17:17
coco minion
2116
asked Feb 25 '16 at 17:17
coco minion
2116
asked Feb 25 '16 at 17:17
coco minion
2116
asked Feb 25 '16 at 17:17
coco minion
2116
2116
Have you got any further with this?
– Anthony Horne
May 17 '16 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
May 19 '16 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
May 19 '16 at 11:30
add a comment |
Have you got any further with this?
– Anthony Horne
May 17 '16 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
May 19 '16 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
May 19 '16 at 11:30
Have you got any further with this?
– Anthony Horne
May 17 '16 at 5:46
Have you got any further with this?
– Anthony Horne
May 17 '16 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
May 19 '16 at 7:26
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
May 19 '16 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
May 19 '16 at 11:30
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
May 19 '16 at 11:30
add a comment |
3 Answers
3
active
oldest
votes
up vote
0
down vote
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.
ComputerHKEY_CURRENT_USERSoftwarePoliciesMicrosoftWindows NTTerminal ServicesUseProxy = 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.
answered Oct 4 '17 at 23:04
Derek Preston
1
Can you be a little more specific with your detail, consider adding some reference and proof supporting what you state.
– Pimp Juice IT
Oct 4 '17 at 23:54
add a comment |
up vote
0
down vote
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.
answered Dec 13 '17 at 23:52
Billious
1035
add a comment |
up vote
-1
down vote
that works,but I needed to change it a bit.
ComputerHKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services
then i create a new value key UseProxy = 0.
answered Apr 12 at 22:51
Marcos
11
1
What works? This looks like it might be a comment about Derek Preston's answer.
– fixer1234
Apr 13 at 0:12
add a comment |
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
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.
ComputerHKEY_CURRENT_USERSoftwarePoliciesMicrosoftWindows NTTerminal ServicesUseProxy = 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.
answered Oct 4 '17 at 23:04
Derek Preston
1
Can you be a little more specific with your detail, consider adding some reference and proof supporting what you state.
– Pimp Juice IT
Oct 4 '17 at 23:54
add a comment |
up vote
0
down vote
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.
ComputerHKEY_CURRENT_USERSoftwarePoliciesMicrosoftWindows NTTerminal ServicesUseProxy = 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.
answered Oct 4 '17 at 23:04
Derek Preston
1
Can you be a little more specific with your detail, consider adding some reference and proof supporting what you state.
– Pimp Juice IT
Oct 4 '17 at 23:54
add a comment |
up vote
0
down vote
up vote
0
down vote
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.
ComputerHKEY_CURRENT_USERSoftwarePoliciesMicrosoftWindows NTTerminal ServicesUseProxy = 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.
answered Oct 4 '17 at 23:04
Derek Preston
1
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.
ComputerHKEY_CURRENT_USERSoftwarePoliciesMicrosoftWindows NTTerminal ServicesUseProxy = 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.
answered Oct 4 '17 at 23:04
Derek Preston
1
answered Oct 4 '17 at 23:04
Derek Preston
1
answered Oct 4 '17 at 23:04
Derek Preston
1
answered Oct 4 '17 at 23:04
Derek Preston
1
1
Can you be a little more specific with your detail, consider adding some reference and proof supporting what you state.
– Pimp Juice IT
Oct 4 '17 at 23:54
add a comment |
Can you be a little more specific with your detail, consider adding some reference and proof supporting what you state.
– Pimp Juice IT
Oct 4 '17 at 23:54
Can you be a little more specific with your detail, consider adding some reference and proof supporting what you state.
– Pimp Juice IT
Oct 4 '17 at 23:54
Can you be a little more specific with your detail, consider adding some reference and proof supporting what you state.
– Pimp Juice IT
Oct 4 '17 at 23:54
add a comment |
up vote
0
down vote
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.
answered Dec 13 '17 at 23:52
Billious
1035
add a comment |
up vote
0
down vote
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.
answered Dec 13 '17 at 23:52
Billious
1035
add a comment |
up vote
0
down vote
up vote
0
down vote
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.
answered Dec 13 '17 at 23:52
Billious
1035
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.
answered Dec 13 '17 at 23:52
Billious
1035
answered Dec 13 '17 at 23:52
Billious
1035
answered Dec 13 '17 at 23:52
Billious
1035
answered Dec 13 '17 at 23:52
Billious
1035
1035
add a comment |
add a comment |
up vote
-1
down vote
that works,but I needed to change it a bit.
ComputerHKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services
then i create a new value key UseProxy = 0.
answered Apr 12 at 22:51
Marcos
11
1
What works? This looks like it might be a comment about Derek Preston's answer.
– fixer1234
Apr 13 at 0:12
add a comment |
up vote
-1
down vote
that works,but I needed to change it a bit.
ComputerHKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services
then i create a new value key UseProxy = 0.
answered Apr 12 at 22:51
Marcos
11
1
What works? This looks like it might be a comment about Derek Preston's answer.
– fixer1234
Apr 13 at 0:12
add a comment |
up vote
-1
down vote
up vote
-1
down vote
that works,but I needed to change it a bit.
ComputerHKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services
then i create a new value key UseProxy = 0.
answered Apr 12 at 22:51
Marcos
11
that works,but I needed to change it a bit.
ComputerHKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services
then i create a new value key UseProxy = 0.
answered Apr 12 at 22:51
Marcos
11
answered Apr 12 at 22:51
Marcos
11
answered Apr 12 at 22:51
Marcos
11
answered Apr 12 at 22:51
Marcos
11
11
1
What works? This looks like it might be a comment about Derek Preston's answer.
– fixer1234
Apr 13 at 0:12
add a comment |
1
What works? This looks like it might be a comment about Derek Preston's answer.
– fixer1234
Apr 13 at 0:12
1
1
What works? This looks like it might be a comment about Derek Preston's answer.
– fixer1234
Apr 13 at 0:12
What works? This looks like it might be a comment about Derek Preston's answer.
– fixer1234
Apr 13 at 0:12
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1045478%2fhyper-v-not-connecting-to-virtual-machine-in-windows-10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have you got any further with this?
– Anthony Horne
May 17 '16 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
May 19 '16 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
May 19 '16 at 11:30