Remote Desktop 0x2407



If receiving the Remote Desktop Error 0x204 while using trying to connect to your PC through Remote Desktop, then, fortunately, you are at the right place. In this article, you will get the complete solutions to fix Remote Desktop Error Code 0x204 on Windows 10.

Remote Desktop is a very useful option with which we can control our Windows computer from another computer. Well, this is very easy-to-use and indeed the best tool because not only you can connect to your PC but also have access to all your apps, files, and network resources.

Type Remote Desktop and press Enter. Open the app in question. Navigate to the Remote Desktop connection you wish to delete. Click on the icon that looks like three horizontally aligned dots. Select the Remove option. Close the Remote Desktop app. Then open the app again and set up the connection you have deleted previously. In the About Remote Desktop Connection dialog box, look for the phrase “Network Level Authentication supported”. If you disable or do not configure this policy setting, Network Level Authentication is not required for user authentication before allowing remote connections to the RD Session Host server. When I opened a RDP connection from my Mac to the Windows Server I would ge the following error: 'Remote Desktop Connection cannot verify the identity of the computer that you want to connect to' Since I was able to connect from a Windows Machine I was under the assumption that the RDP problem layed with my Mac. Make sure the PC is turned on and connected to the network, and that remote access is enabled'All MAC clients, can connect to all other RDS servers. Windows clients CAN connect to the new RDS server - No issues. MAC clients are running the newest version of Microsoft Remote Desktop.

But to use the remote desktop option and connect to your PC there are several conditions that should be met, such as:

  • Your system should be turned on
  • The remote desktop option must be enabled
  • Must have the network connection and network access to a remote computer
  • And lastly, you must have permission to connect to another device.

And if you meet these conditions you can easily connect to your PC. But, the things may not always go the same, many users reported they are receiving the Microsoft Remote Desktop error 0x204 while using Remote Desktop.

This is really very frustrating but fortunately, there are fixes that you can try to fix Remote Desktop error 0x204.

What Causes Remote Desktop Error 0x204 on Windows 10?

There are a number of things that cause the error code 0x204. Here learn about them:

  • Due to outdated drivers or recently installed hardware/drivers
  • The security settings or the third party security programs can also cause interruption
  • If the remote desktop protocol is disabled
  • The problematic Remote Desktop connection account can also cause the problem.

Now follow the solutions given one by one to resolve Remote Desktop Connection fails error 0x204.

How Do I Fix Remote Desktop Error 0x204 on Windows 10?

Fix 1: Verify the Remote Desktop Protocol

As said above if the remote desktop protocol is disabled then this is what causes the error and becomes a big hurdle. So very first check whether the Remote Desktop Protocol is enabled or not.

Follow the steps to do so:

  • First press Windows key + R > in the Run box type SystemPropertiesRemote.exe > hit OK
  • Then in the System Properties > navigate to Remote tab
  • Next under the Remote desktop> checkmark Allow remote connections to this computer – Allow remote connections only from computers running Remote Desktop with Network-level authentication (recommended)

Now check if the error code 0x204 in Windows 10 is fixed or not.

Fix 2: Allow Remote Desktop via Windows Firewall

Many users confirmed that disabling the third party security program and the Windows Firewall works for them.

The Remote desktop connection fails – error 0x204 or 0x207 occurs because the Windows Firewall and the other third-party security program causes an interruption.

Follow the steps to verify your security settings:

  • Click on Start Menu > Control Panel > hit Enter
  • Now go to System and Security > and to Windows Defender Firewall,
  • Then through Windows Firewall link > click on the Allow an app through Windows Firewall
  • Locate Remote Desktop > and click on it to allow for both the private and public network

I hope this works for you to fix the remote desktop error 0x204 in Windows 10. But if not then check if you have installed any third-party antivirus program then disable it temporarily.

Especially the McAfee Internet Security is causing error code 0x204, so check if you are running this security program then disable it.

Fix 3: Configure the Port for Remote Desktop connections

If still encountering the error code 0x204 then another thing that you need to do is check if your remote sessions are through the internet, then make sure that your router was configured to forward the remote desktop port 3389 by default.

As the routers have different interfaces so it is completely impossible to provide definite instructions. But still, there are some basic steps that guide you through the process.

So follow the steps given:

  • Here you need to get the IP address of the system you want to connect and to do so you need to open Command Prompt > type ipconfig
  • Next log into the router > finds out the Port Forwarding section.

And in that section, you need to forward TCP port 3389 to the earlier located IP address.

Please Note: You need to make sure that exposing the Remote Desktop server directly to the internet can generate risks like virus infection, malware, hacking, etc. So, assure using strong passwords and also install a VPN.

Or else you can change the RDP listening port from the 3389 default to another high post number in dynamic range.

Now check if the Remote Desktop error 0x204 or 0x207 is fixed or not. If not then head to the next solution.

Fix 4: Check if You Have Installed New Hardware/ Drivers

As discussed above if you have installed any new hardware or drivers then this can also cause error code 0x204 in Windows 10.

So, check if this is a case then try the below-given steps:

  • Run Hardware Diagnosis provided by the manufacturer to identify which hardware component is not working or failed
  • Also, uninstall or replace the recently installed driver.

Despite this, if your device drivers are outdated then this can also cause the remote desktop error 0x204 in Windows 10.

So, check for the outdated drivers and update them, you can go to the manufacturer website or the Microsoft Official website and search for the latest driver update compatible with your Windows 10 system.

Remote Desktop 0x2407

Moreover, you can also do it easily by running the Driver Easy, this is an advanced tool that just by scanning once detect and update the entire device drivers.

Get Driver Easy to update the drivers automatically

Fix 5: Reset your Account Remote Desktop Connection

You can also try resetting the Remote Desktop connection, and check if the Remote desktop connection error 0x204 is resolved or not.
Follow the steps given:

  • Press Windows + S key > now type Remote Desktop > press Enter.
  • Now open the app in question > go to the Remote Desktop connection you want to delete.
  • Then click on an icon (three horizontally-aligned dots)
  • And choose the Remove option > close the Remote Desktop app.

Now you need to open the app and try to set up the connection you have deleted now.

Fix 6: Reinstall Remote Desktop app

If none of the above-given solutions work for you then try to reinstall the remote desktop software and to do so first uninstall Remote Desktop app in Windows 10.

Follow the steps to do so:

  • First, open the Microsoft Remote Desktop app
  • Then click on the overflow menu (…) button > placed next to the name (ex: “My Laptop”) of Remote Desktop connection that is needed to delete > click on Remove
  • Next after disabling the app > try installing it again

Fix 7: Check if You are Running Latest Version of Microsoft Remote Desktop App

Here it is suggested to verify if you are using the latest version of the Microsoft Remote Desktop app.

As if the Microsoft Remote Desktop app is outdated then it is not compatible with your system and can cause remote desktop connection error 0x204 in Windows 10.

So, make sure to install the latest version of the app from the Microsoft official website.

People Also Ask:

Remote Desktop Error Code 0x204

How do I Fix Remote Desktop Connection Fails - Error 0x204 or 0x207?

You can fix the remote desktop connections fails error code 0x204 or 0x207, in the following ways:

Enabling the Remote Desktop Protocol,

  • Verify the security settings,
  • Reinstall Remote Desktop app
  • Reset RDP connection
  • Configure the port for Remote Desktop connections
  • Verify recently installed hardware/drivers
  • Run the latest version of Remote Desktop App
How do I Fix Remote Desktop Connection has Stopped Working Error

To fix the Remote desktop connection has stopped working error, try the fixes - Allow Remote Desktop Via Windows Firewall, verify the dependency services, uncheck printers option in Remote Desktop Connection, disable autologin via Registry Editor, remove the recently installed apps, and rename bitmapped images.

To know more read the article - How To Fix Remote Desktop Connection Stopped Working Error

How do I Clear My Remote Desktop Connection History

You can delete the RDP connection history manually from the jump list in Windows 10 or else delete the RDP connection cache using the registry, or use the script method to clear the remote desktop history.

Read the article to follow the detailed steps: How to Clear the RDP Connection History

Recommended Solution: Fix PC Problems & Enhance its Performance

If your Windows PC/laptop is running slow or you are facing various PC issues and errors then you can fix the problem easily by scanning your system with trusted and 100% safe solution.

Just run the PC Repair Tool, this is an advanced multifunctional tool that scans, detects and fixes various stubborn PC errors.

With this, you can fix DLL errors, Registry corruption, repair system file corruption, protect your PC from virus and malware infection, clean your PC and much more.

Microsoft Remote Desktop 0x2407 Mac

This also optimizes and enhances PC performance in a few clicks.

Get PC Repair Tool, to Optimize, Enhance & Speed your Computer

Wrapping Things Up

Undoubtedly the remote desktop option is an effective option as managing or troubleshooting the PC from afar can give us huge comfort.

And this is the reason it is highly popular among the users.

But if you encounter remote desktop error 0x204 in Windows 10, then follow the above listed possible solutions one by one.

The solutions listed are useful and will definitely work for you to fix Microsoft Remote Desktop Connection error 0x204 in Windows 10.

And, as I always say and recommend, always keep your PC clean and updated, and following this simple rule will make your PC more secure and fix various issues and errors and you will no longer get it in the future.

I hope you like the article, also feel free to give a big thumbs up on our FB page and Twitter.

Good Luck..!

Hardeep Kaur

Hardeep has always been a Windows lover ever since she got her hands on her first Windows XP PC. She has always been enthusiastic about technological stuff, especially Artificial Intelligence (AI) computing. Before joining PC Error Fix, she worked as a freelancer and worked on numerous technical projects.

-->

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.

Check the status of the RDP protocol

Check the status of the RDP protocol on a local computer

To check and change the status of the RDP protocol on a local computer, see How to enable Remote Desktop.

Note

If the remote desktop options are not available, see Check whether a Group Policy Object is blocking RDP.

Check the status of the RDP protocol on a remote computer

Important

Follow this section's instructions carefully. Serious problems can occur if the registry is modified incorrectly. Before you start modifying the registry, back up the registry so you can restore it in case something goes wrong.

To check and change the status of the RDP protocol on a remote computer, use a network registry connection:

  1. First, go to the Start menu, then select Run. In the text box that appears, enter regedt32.
  2. In the Registry Editor, select File, then select Connect Network Registry.
  3. In the Select Computer dialog box, enter the name of the remote computer, select Check Names, and then select OK.
  4. Navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal Server.
    • If the value of the fDenyTSConnections key is 0, then RDP is enabled.
    • If the value of the fDenyTSConnections key is 1, then RDP is disabled.
  5. To enable RDP, change the value of fDenyTSConnections from 1 to 0.

Check whether a Group Policy Object (GPO) is blocking RDP on a local computer

If you can't turn on RDP in the user interface or the value of fDenyTSConnections reverts to 1 after you've changed it, a GPO may be overriding the computer-level settings.

To check the group policy configuration on a local computer, open a Command Prompt window as an administrator, and enter the following command:

After this command finishes, open gpresult.html. In Computer ConfigurationAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostConnections, find the Allow users to connect remotely by using Remote Desktop Services policy.

  • If the setting for this policy is Enabled, Group Policy is not blocking RDP connections.

  • If the setting for this policy is Disabled, check Winning GPO. This is the GPO that is blocking RDP connections.

Check whether a GPO is blocking RDP on a remote computer

To check the Group Policy configuration on a remote computer, the command is almost the same as for a local computer:

The file that this command produces (gpresult-<computer name>.html) uses the same information format as the local computer version (gpresult.html) uses.

Modifying a blocking GPO

You can modify these settings in the Group Policy Object Editor (GPE) and Group Policy Management Console (GPM). For more information about how to use Group Policy, see Advanced Group Policy Management.

To modify the blocking policy, use one of the following methods:

  • In GPE, access the appropriate level of GPO (such as local or domain), and navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections > Allow users to connect remotely by using Remote Desktop Services.
    1. Set the policy to either Enabled or Not configured.
    2. On the affected computers, open a command prompt window as an administrator, and run the gpupdate /force command.
  • In GPM, navigate to the organizational unit (OU) in which the blocking policy is applied to the affected computers and delete the policy from the OU.

Check the status of the RDP services

On both the local (client) computer and the remote (target) computer, the following services should be running:

  • Remote Desktop Services (TermService)
  • Remote Desktop Services UserMode Port Redirector (UmRdpService)

You can use the Services MMC snap-in to manage the services locally or remotely. You can also use PowerShell to manage the services locally or remotely (if the remote computer is configured to accept remote PowerShell cmdlets).

On either computer, if one or both services are not running, start them.

Note

If you start the Remote Desktop Services service, click Yes to automatically restart the Remote Desktop Services UserMode Port Redirector service.

Check that the RDP listener is functioning

Remote desktop 0x2407 image

Important

Follow this section's instructions carefully. Serious problems can occur if the registry is modified incorrectly. Before you starty modifying the registry, back up the registry so you can restore it in case something goes wrong.

Error Code 0x2407 Mac

Check the status of the RDP listener

For this procedure, use a PowerShell instance that has administrative permissions. For a local computer, you can also use a command prompt that has administrative permissions. However, this procedure uses PowerShell because the same cmdlets work both locally and remotely.

Remote Desktop 0x2407 Image

  1. To connect to a remote computer, run the following cmdlet:

  2. Enter qwinsta.

  3. If the list includes rdp-tcp with a status of Listen, the RDP listener is working. Proceed to Check the RDP listener port. Otherwise, continue at step 4.

  4. Export the RDP listener configuration from a working computer.

    1. Sign in to a computer that has the same operating system version as the affected computer has, and access that computer's registry (for example, by using Registry Editor).
    2. Navigate to the following registry entry:
      HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp
    3. Export the entry to a .reg file. For example, in Registry Editor, right-click the entry, select Export, and then enter a filename for the exported settings.
    4. Copy the exported .reg file to the affected computer.
  5. To import the RDP listener configuration, open a PowerShell window that has administrative permissions on the affected computer (or open the PowerShell window and connect to the affected computer remotely).

    1. To back up the existing registry entry, enter the following cmdlet:

    2. To remove the existing registry entry, enter the following cmdlets:

    3. To import the new registry entry and then restart the service, enter the following cmdlets:

      Replace <filename> with the name of the exported .reg file.

  6. Test the configuration by trying the remote desktop connection again. If you still can't connect, restart the affected computer.

  7. If you still can't connect, check the status of the RDP self-signed certificate.

Check the status of the RDP self-signed certificate

  1. If you still can't connect, open the Certificates MMC snap-in. When you are prompted to select the certificate store to manage, select Computer account, and then select the affected computer.
  2. In the Certificates folder under Remote Desktop, delete the RDP self-signed certificate.
  3. On the affected computer, restart the Remote Desktop Services service.
  4. Refresh the Certificates snap-in.
  5. If the RDP self-signed certificate has not been recreated, check the permissions of the MachineKeys folder.

Check the permissions of the MachineKeys folder

  1. On the affected computer, open Explorer, and then navigate to C:ProgramDataMicrosoftCryptoRSA.
  2. Right-click MachineKeys, select Properties, select Security, and then select Advanced.
  3. Make sure that the following permissions are configured:
    • BuiltinAdministrators: Full control
    • Everyone: Read, Write

Check the RDP listener port

On both the local (client) computer and the remote (target) computer, the RDP listener should be listening on port 3389. No other applications should be using this port.

Important

Follow this section's instructions carefully. Serious problems can occur if the registry is modified incorrectly. Before you starty modifying the registry, back up the registry so you can restore it in case something goes wrong.

To check or change the RDP port, use the Registry Editor:

  1. Go to the Start menu, select Run, then enter regedt32 into the text box that appears.
    • To connect to a remote computer, select File, and then select Connect Network Registry.
    • In the Select Computer dialog box, enter the name of the remote computer, select Check Names, and then select OK.
  2. Open the registry and navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWinStations<listener>.
  3. If PortNumber has a value other than 3389, change it to 3389.

    Important

    You can operate Remote Desktop services using another port. However, we don't recommend you do this. This article doesn't cover how to troubleshoot that type of configuration.

  4. After you change the port number, restart the Remote Desktop Services service.

Remote Desktop Connection

Check that another application isn't trying to use the same port

For this procedure, use a PowerShell instance that has administrative permissions. For a local computer, you can also use a command prompt that has administrative permissions. However, this procedure uses PowerShell because the same cmdlets work locally and remotely.

Microsoft Remote Desktop 0x2407

  1. Open a PowerShell window. To connect to a remote computer, enter Enter-PSSession -ComputerName <computer name>.

  2. Enter the following command:

  3. Look for an entry for TCP port 3389 (or the assigned RDP port) with a status of Listening.

    Note

    The process identifier (PID) for the process or service using that port appears under the PID column.

  4. To determine which application is using port 3389 (or the assigned RDP port), enter the following command:

  5. Look for an entry for the PID number that is associated with the port (from the netstat output). The services or processes that are associated with that PID appear on the right column.

  6. If an application or service other than Remote Desktop Services (TermServ.exe) is using the port, you can resolve the conflict by using one of the following methods:

    • Configure the other application or service to use a different port (recommended).
    • Uninstall the other application or service.
    • Configure RDP to use a different port, and then restart the Remote Desktop Services service (not recommended).

Check whether a firewall is blocking the RDP port

Use the psping tool to test whether you can reach the affected computer by using port 3389.

Remote Desktop 0x2407

  1. Go to a different computer that isn't affected and download psping from https://live.sysinternals.com/psping.exe.

  2. Open a command prompt window as an administrator, change to the directory in which you installed psping, and then enter the following command:

  3. Check the output of the psping command for results such as the following:

    • Connecting to <computer IP>: The remote computer is reachable.
    • (0% loss): All attempts to connect succeeded.
    • The remote computer refused the network connection: The remote computer is not reachable.
    • (100% loss): All attempts to connect failed.
  4. Run psping on multiple computers to test their ability to connect to the affected computer.

  5. Note whether the affected computer blocks connections from all other computers, some other computers, or only one other computer.

  6. Recommended next steps:

    • Engage your network administrators to verify that the network allows RDP traffic to the affected computer.
    • Investigate the configurations of any firewalls between the source computers and the affected computer (including Windows Firewall on the affected computer) to determine whether a firewall is blocking the RDP port.