RDP Keeps crashing when starting a new session

Hello Randall,

Welcome to the Microsoft Community.

When Remote Desktop Protocol (RDP) crashes while starting a new session, it can be caused by a variety of issues related to configuration, software conflicts, or networking problems. Here are some steps you can take to troubleshoot and resolve this issue:

1. Check for System Updates
Ensure that both the client (your local machine) and the server (the remote machine you're trying to connect to) have the latest updates installed.

Windows Updates: Sometimes RDP issues are resolved through updates that address bugs or compatibility problems.
On Windows, go to Settings > Update & Security > Windows Update > Check for updates.
RDP Client: Make sure your Remote Desktop client is up-to-date. If you're using a third-party RDP client, ensure that it’s the latest version.

2. Check RDP Version Compatibility
RDP versions may cause compatibility issues. Ensure both the client and server are running compatible versions of RDP. For example, newer versions of Windows support RDP 10 (or newer), and older versions of Windows might not be fully compatible with them.

Check the RDP version on your client machine by entering

mstsc /version 

in the Run dialog (Win + R).
Ensure the server you're connecting to supports the RDP version you're using.

3. Verify Network Connectivity
Ping Test: Ensure that the remote machine is reachable and there are no network issues between your local machine and the remote server.
Open Command Prompt (cmd) and type ping [remote IP or hostname].
If there is no response or packet loss, there may be a network issue or firewall blocking the RDP connection.
Firewall Settings: Ensure that RDP (port 3389) is not being blocked by any firewall. On both the client and server, verify that port 3389 is open and allowed.

4. Clear RDP Cache: Corrupted cached data might cause RDP to crash. You can clear the cache to see if that resolves the issue.

On the client machine, clear RDP credentials and cache:
Windows Credential Manager: Go to Control Panel > User Accounts > Credential Manager. Remove any saved RDP credentials for the problematic server.
Delete RDP Cache: Navigate to C:\Users[YourUsername]\AppData\Local\Microsoft\Terminal Server Client and delete files like Default.rdp or any cache-related files.

5. Disable RDP Graphics Hardware Acceleration: If you are using an older graphics card or have issues with hardware acceleration, RDP can crash. Try disabling hardware acceleration:

Open Remote Desktop Connection (mstsc).
Click on Show Options, then go to the Experience tab.
Uncheck Persistent Bitmap Caching or reduce the display settings.
Under Display, set it to a lower resolution or disable the "Font Smoothing" and "Desktop Composition" options.

6. Reinstall RDP Components
If the issue persists, reinstall the RDP components or reset RDP configuration on the server and client:

On the server, run the following PowerShell command to reset RDP configurations:
Get-WmiObject -Class Win32_OperatingSystem | Set-WmiInstance -Arguments @{RemoteDesktopEnabled=$true}
Alternatively, you can disable and then enable the Remote Desktop feature on the server.
Go to Control Panel > System > Remote Settings and toggle Allow Remote Connections.

7. Check Event Viewer Logs
If RDP keeps crashing, reviewing the Event Viewer logs may provide insight into what's causing the issue.

On the client machine:
Open Event Viewer (press Win + R and type eventvwr.msc).
Navigate to Windows Logs > Application and look for any RDP-related errors or crashes.
Look for events from "TermService" (Remote Desktop Services) or any "Faulting Application" errors related to mstsc.exe.
On the server:
Check the Application logs for any Remote Desktop Services errors.

8. Check for Third-Party Conflicts
Antivirus software, third-party firewall programs, or other security software might interfere with RDP connections.

Perform a clean boot to see if a background program is causing the issue. This will start Windows with a minimal set of drivers and startup programs. How to perform a clean boot in Windows - Microsoft Support

1. Press Windows + R, type msconfig, and press Enter.
2. Go to the Services tab, check Hide all Microsoft services, and then click Disable all.
3. Go to the Startup tab and click Open Task Manager.
4. Disable all startup items.
5. Restart your computer.
   Disclaimer: A “clean boot” starts Windows with a minimal set of drivers and startup programs. It helps to determine whether a background service is interfering with your game or program and to isolate the cause of a problem.   
   These steps of "clean boot" might look complicated at first glance. However, to avoid any trouble for you, please follow them in order and step-by step so that it will help you get back on track.

9. Configure RDP Licensing Mode (for Windows Server)
If you're connecting to a Windows Server and using Remote Desktop Services (RDS), ensure that the RDS licensing is properly configured:

Open Server Manager on the server, go to Remote Desktop Services, and ensure the licensing mode is correctly configured.
Misconfigured licenses could lead to RDP crashes.

10. Test with Alternative RDP Clients
If you're still experiencing issues with the native Windows RDP client (mstsc), try using a third-party RDP client like:

Microsoft Remote Desktop (available in the Microsoft Store)
If this client works, this might suggest an issue with the built-in RDP client.

11. Check for Group Policy Settings (For Servers)
Sometimes group policy settings on the remote server can cause issues with RDP.

Open gpedit.msc (Group Policy Editor) on the server and navigate to:
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections.
Ensure that the Allow users to connect remotely by using Remote Desktop Services is enabled.
Review other settings that might restrict or interfere with RDP connections.

12. Check for Memory or CPU Resource Exhaustion
High CPU usage or low available memory on the server can cause RDP sessions to crash.
Open Task Manager on the remote server and check for excessive resource usage during an RDP session.
Conclusion

By following these troubleshooting steps, you can likely pinpoint the cause of RDP crashes and resolve the issue. If the problem persists, it may help to examine specific error codes in the Event Viewer, check for server-side misconfigurations, or explore third-party tools.

Best Regards,

William.Y | Microsoft Community Support Specialist