cant enable remote desktop in windows 10 pro











up vote
0
down vote

favorite












I cant enable remote desktop in windows 10 pro (build 1803).
I toggle the button



pic1.



clicks confirm



pic2.



but the service is not toggled on



pic3.



However, when I check the classic way of enabling RDP, it shows the service being ticked on. but unable to remote in. I did restart the RDP service too.



pic4.



I was able to activate the RDP service by disabling the firewall rules under Public network settings



pic5pic6



Unsure what rules is causing this issue yet.






windows-10 remote-desktop







share|improve this question
























  • Where are you trying to connect from? If from outside the network, make sure you have port forwarding set up.
    – HazardousGlitch
    Nov 22 at 2:13










  • I was able to activate the RDP service by disabling the firewall rules under Public network settings. Unsure what rules is causing this issue yet. see the updated images for clarity. the issue is that the service is started on the system due to some rules - something is preventing it.
    – Falken
    Nov 22 at 2:26










  • Where are you trying to access the computer from? On the same network or outside of it?
    – HazardousGlitch
    Nov 22 at 2:32










  • within the same network. I have figured out the issue now. The network profile was set to Public instead of Private. Under Private, with FW enabled, you can enable the RDP service without any issue.
    – Falken
    Nov 22 at 2:34






  • 1




    added the solution
    – Falken
    Nov 22 at 2:41















up vote
0
down vote

favorite












I cant enable remote desktop in windows 10 pro (build 1803).
I toggle the button



pic1.



clicks confirm



pic2.



but the service is not toggled on



pic3.



However, when I check the classic way of enabling RDP, it shows the service being ticked on. but unable to remote in. I did restart the RDP service too.



pic4.



I was able to activate the RDP service by disabling the firewall rules under Public network settings



pic5pic6



Unsure what rules is causing this issue yet.






windows-10 remote-desktop







share|improve this question
























  • Where are you trying to connect from? If from outside the network, make sure you have port forwarding set up.
    – HazardousGlitch
    Nov 22 at 2:13










  • I was able to activate the RDP service by disabling the firewall rules under Public network settings. Unsure what rules is causing this issue yet. see the updated images for clarity. the issue is that the service is started on the system due to some rules - something is preventing it.
    – Falken
    Nov 22 at 2:26










  • Where are you trying to access the computer from? On the same network or outside of it?
    – HazardousGlitch
    Nov 22 at 2:32










  • within the same network. I have figured out the issue now. The network profile was set to Public instead of Private. Under Private, with FW enabled, you can enable the RDP service without any issue.
    – Falken
    Nov 22 at 2:34






  • 1




    added the solution
    – Falken
    Nov 22 at 2:41













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I cant enable remote desktop in windows 10 pro (build 1803).
I toggle the button



pic1.



clicks confirm



pic2.



but the service is not toggled on



pic3.



However, when I check the classic way of enabling RDP, it shows the service being ticked on. but unable to remote in. I did restart the RDP service too.



pic4.



I was able to activate the RDP service by disabling the firewall rules under Public network settings



pic5pic6



Unsure what rules is causing this issue yet.






windows-10 remote-desktop







share|improve this question















I cant enable remote desktop in windows 10 pro (build 1803).
I toggle the button



pic1.



clicks confirm



pic2.



but the service is not toggled on



pic3.



However, when I check the classic way of enabling RDP, it shows the service being ticked on. but unable to remote in. I did restart the RDP service too.



pic4.



I was able to activate the RDP service by disabling the firewall rules under Public network settings



pic5pic6



Unsure what rules is causing this issue yet.






windows-10 remote-desktop




windows-10 remote-desktop






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 22 at 2:31









Twisty Impersonator

17.3k126293




17.3k126293










asked Nov 22 at 1:50









Falken

13




13












  • Where are you trying to connect from? If from outside the network, make sure you have port forwarding set up.
    – HazardousGlitch
    Nov 22 at 2:13










  • I was able to activate the RDP service by disabling the firewall rules under Public network settings. Unsure what rules is causing this issue yet. see the updated images for clarity. the issue is that the service is started on the system due to some rules - something is preventing it.
    – Falken
    Nov 22 at 2:26










  • Where are you trying to access the computer from? On the same network or outside of it?
    – HazardousGlitch
    Nov 22 at 2:32










  • within the same network. I have figured out the issue now. The network profile was set to Public instead of Private. Under Private, with FW enabled, you can enable the RDP service without any issue.
    – Falken
    Nov 22 at 2:34






  • 1




    added the solution
    – Falken
    Nov 22 at 2:41


















  • Where are you trying to connect from? If from outside the network, make sure you have port forwarding set up.
    – HazardousGlitch
    Nov 22 at 2:13










  • I was able to activate the RDP service by disabling the firewall rules under Public network settings. Unsure what rules is causing this issue yet. see the updated images for clarity. the issue is that the service is started on the system due to some rules - something is preventing it.
    – Falken
    Nov 22 at 2:26










  • Where are you trying to access the computer from? On the same network or outside of it?
    – HazardousGlitch
    Nov 22 at 2:32










  • within the same network. I have figured out the issue now. The network profile was set to Public instead of Private. Under Private, with FW enabled, you can enable the RDP service without any issue.
    – Falken
    Nov 22 at 2:34






  • 1




    added the solution
    – Falken
    Nov 22 at 2:41
















Where are you trying to connect from? If from outside the network, make sure you have port forwarding set up.
– HazardousGlitch
Nov 22 at 2:13




Where are you trying to connect from? If from outside the network, make sure you have port forwarding set up.
– HazardousGlitch
Nov 22 at 2:13












I was able to activate the RDP service by disabling the firewall rules under Public network settings. Unsure what rules is causing this issue yet. see the updated images for clarity. the issue is that the service is started on the system due to some rules - something is preventing it.
– Falken
Nov 22 at 2:26




I was able to activate the RDP service by disabling the firewall rules under Public network settings. Unsure what rules is causing this issue yet. see the updated images for clarity. the issue is that the service is started on the system due to some rules - something is preventing it.
– Falken
Nov 22 at 2:26












Where are you trying to access the computer from? On the same network or outside of it?
– HazardousGlitch
Nov 22 at 2:32




Where are you trying to access the computer from? On the same network or outside of it?
– HazardousGlitch
Nov 22 at 2:32












within the same network. I have figured out the issue now. The network profile was set to Public instead of Private. Under Private, with FW enabled, you can enable the RDP service without any issue.
– Falken
Nov 22 at 2:34




within the same network. I have figured out the issue now. The network profile was set to Public instead of Private. Under Private, with FW enabled, you can enable the RDP service without any issue.
– Falken
Nov 22 at 2:34




1




1




added the solution
– Falken
Nov 22 at 2:41




added the solution
– Falken
Nov 22 at 2:41










1 Answer
1






active

oldest

votes

















up vote
0
down vote



accepted










I have figured out the issue now. The network profile was set to Public instead of Private. Under Private, with FW enabled, you can enable the RDP service without any issue. But when the profile is set for Public and with FW enabled, the RDP service isn't allowed to start by default it seems. Unless manual configurations are done.






share|improve this answer





















  • Thanks for posting the solution! Do you want to set it as Answer?
    – davidbaumann
    Nov 22 at 16:10










  • yes, please. thanks
    – Falken
    2 days ago











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377451%2fcant-enable-remote-desktop-in-windows-10-pro%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
0
down vote



accepted










I have figured out the issue now. The network profile was set to Public instead of Private. Under Private, with FW enabled, you can enable the RDP service without any issue. But when the profile is set for Public and with FW enabled, the RDP service isn't allowed to start by default it seems. Unless manual configurations are done.






share|improve this answer





















  • Thanks for posting the solution! Do you want to set it as Answer?
    – davidbaumann
    Nov 22 at 16:10










  • yes, please. thanks
    – Falken
    2 days ago















up vote
0
down vote



accepted










I have figured out the issue now. The network profile was set to Public instead of Private. Under Private, with FW enabled, you can enable the RDP service without any issue. But when the profile is set for Public and with FW enabled, the RDP service isn't allowed to start by default it seems. Unless manual configurations are done.






share|improve this answer





















  • Thanks for posting the solution! Do you want to set it as Answer?
    – davidbaumann
    Nov 22 at 16:10










  • yes, please. thanks
    – Falken
    2 days ago













up vote
0
down vote



accepted







up vote
0
down vote



accepted






I have figured out the issue now. The network profile was set to Public instead of Private. Under Private, with FW enabled, you can enable the RDP service without any issue. But when the profile is set for Public and with FW enabled, the RDP service isn't allowed to start by default it seems. Unless manual configurations are done.






share|improve this answer












I have figured out the issue now. The network profile was set to Public instead of Private. Under Private, with FW enabled, you can enable the RDP service without any issue. But when the profile is set for Public and with FW enabled, the RDP service isn't allowed to start by default it seems. Unless manual configurations are done.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 22 at 2:40









Falken

13




13












  • Thanks for posting the solution! Do you want to set it as Answer?
    – davidbaumann
    Nov 22 at 16:10










  • yes, please. thanks
    – Falken
    2 days ago


















  • Thanks for posting the solution! Do you want to set it as Answer?
    – davidbaumann
    Nov 22 at 16:10










  • yes, please. thanks
    – Falken
    2 days ago
















Thanks for posting the solution! Do you want to set it as Answer?
– davidbaumann
Nov 22 at 16:10




Thanks for posting the solution! Do you want to set it as Answer?
– davidbaumann
Nov 22 at 16:10












yes, please. thanks
– Falken
2 days ago




yes, please. thanks
– Falken
2 days ago


















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377451%2fcant-enable-remote-desktop-in-windows-10-pro%23new-answer', 'question_page');
}
);

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







-

Popular posts from this blog

AnyDesk - Fatal Program Failure

Image
up vote 0 down vote favorite Good day all. I have a window that pops up saying Fatal Program Failure (AnyDesk). This is what I have done so far: Uninstalled AnyDesk and reinstalled it. ( The window still appeared ) I disabled AnyDesk start up in Msconfig and the window seems to have disapeared. Lastly I made sure that AnyDesk worked by remoting into it, and it worked. Today the same window appeared. How do I get rid of this window? remote-desktop share | improve this question edited 10 hours ago Tomasz Jakub Rup 552 3 13 ...
Read more

How to calibrate 16:9 built-in touch-screen to a 4:3 resolution?

Image
up vote 0 down vote favorite I need help with an issue we're facing in a project where we are moving from a Windows-based POS environment to one running on CentOS7. The problem consists of a number of factors, please find the details below: The supplier of our POS application will only deliver an application that is hard-coded to run in a 1024:768 4:3 format. The hardware we are using is a POS unit from HP that has a built-in 16:9 touch-screen. The employees using this solution is not supposed to see nor have access to anything but the POS application. Our sales organization demands that touch is an available feature when going live with the new POS environment. Going further into this, allow me to explain what we have encountered on the way trying to achieve the goal of having a touch-screen: We've simply change...
Read more

QoS: MAC-Priority for clients behind a repeater

Image
1 1 I've setup a wireless network using a Linksys-Router (DD-WRT) as an AP and a TP-Link repeater for range extension. To manage bandwith for specific users, I've setup QoS-Rules on the AP (DD-WRT) using MAC-Priority: However the AP shows only the Repeater's MAC and the MACs of users inside the AP-Range. The MAC addresses of users behind the Repeater are not listed : The purple MAC is not listed in the AP-Clientlist. Its related to a device connected via the TP-Link repeater. Q: How can I setup MAC-Priority for repeater-clients? Do I simply add the purple MAC in AP-MAC priority list although it's not listed as a client? I want to setup specific priority instead of giving one priority for all clients behind the repeater by adding the repeater's MAC in the MAC priority list in the AP as ...
Read more