Can t turn on remote desktop windows 10

1. Allow RDP in Windows Firewall

The first time you try to access the remote desktop the windows firewall will not allow you to do so because it is not active by default. It is because of security reasons as it gives security warnings if you try to access your computer from a different device. It may also happen if you are using any other antivirus software that does not let any other device access your computer. So in the case of antivirus the solution may be to uninstall it or stop it from running in the background.

In case of Windows firewall warnings, we have to turn it on

  • Type “firewall” in the search and open the Windows Defender Firewall.
  • From the left menu click onAllow an app or feature through Windows Firewall.
  • Click on change settings
  • Now find the Remote Desktop and turn it on

There you go, the Windows firewall will now allow you to connect to this PC remotely using remote desktop protocol.

Remote Desktop - Allow access to your PC

  • Article
  • 12/23/2021
  • 3 minutes to read
  • 10 contributors

Is this page helpful?

Yes No

Any additional feedback?

Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.

Submit

Thank you.

In this article

Applies to: Windows Server 2022, Windows 10, Windows 8.1, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2

You can use Remote Desktop to connect to and control your PC from a remote device by using a Microsoft Remote Desktop client [available for Windows, iOS, macOS and Android]. When you allow remote connections to your PC, you can use another device to connect to your PC and have access to all of your apps, files, and network resources as if you were sitting at your desk.

Note

You can use Remote Desktop to connect to Windows 10 Pro and Enterprise, Windows 8.1 and 8 Enterprise and Pro, Windows 7 Professional, Enterprise, and Ultimate, and Windows Server versions newer than Windows Server 2008. You can't connect to computers running a Home edition [like Windows 10 Home].

To connect to a remote PC, that computer must be turned on, it must have a network connection, Remote Desktop must be enabled, you must have network access to the remote computer [this could be through the Internet], and you must have permission to connect. For permission to connect, you must be on the list of users. Before you start a connection, it's a good idea to look up the name of the computer you're connecting to and to make sure Remote Desktop connections are allowed through its firewall.

General Remote Desktop connection troubleshooting

  • Article
  • 12/23/2021
  • 8 minutes to read
  • 8 contributors

Is this page helpful?

Yes No

Any additional feedback?

Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.

Submit

Thank you.

In this article

Use these steps when a Remote Desktop client can't connect to a remote desktop but doesn't provide messages or other symptoms that would help identify the cause.

Remote Desktop won't stay enabled

Archived Forums

>

Windows 10 Installation, Setup, and Deployment

  • Question

  • 0

    Sign in to vote

    I had to rebuild one of our clients after a disk crash. It's running Win10Pro 1809 networked on a domain.

    When I go to Settings/System/Remote Desktop, if I try to turn on the slide-switch, it follows the mouse, but slides back off immediately. No error messages or warnings. The "Select users..." link is visible and highlights, but nothing happens.

    I'm logged on as the domain administrator. The machine allowed remote access before the disk crash.

    Sunday, November 11, 2018 6:56 PM

All replies

  • 0

    Sign in to vote

    The OS version might be wrong - it's from my memory, which is volatile. I can't access it remotely, so I can't verify it until next time I'm in the office.

    Tuesday, November 13, 2018 1:26 AM

  • 0

    Sign in to vote

    The version is 1803.

    When I set the access via the "old way", it warned me that the unit was set to hibernate. I changed that and it enabled fine. I never went back to the "proper method" to enable it, so I'm not sure whether it was the method or the hibernate. No matter, it now works.


    • Edited by jjgurley Wednesday, November 14, 2018 5:21 PM

    Wednesday, November 14, 2018 5:20 PM

Chủ Đề