Remote Desktop can't connect to the remote computer Error using the macOS RDP client RDP displays a black screen instead of the desktop Unable to remotely log on to an instance with a user that is not an administrator Troubleshooting Remote Desktop issues using Amazon Systems Manager Enable Remote Desktop on an EC2 instance with remote registry I've lost my private key. How can I connect to my Windows instance?

Troubleshoot connecting to your Windows instance

The following are possible problems you might have and error messages you might see while trying to connect to your Windows instance.

Remote Desktop can't connect to the remote computer
Error using the macOS RDP client
RDP displays a black screen instead of the desktop
Unable to remotely log on to an instance with a user that is not an administrator
Troubleshooting Remote Desktop issues using Amazon Systems Manager
Enable Remote Desktop on an EC2 instance with remote registry
I've lost my private key. How can I connect to my Windows instance?

Remote Desktop can't connect to the remote computer

Try the following to resolve issues related to connecting to your instance:

Verify that you're using the correct public DNS hostname. (In the Amazon EC2 console, select the instance and check Public DNS (IPv4) in the details pane.) If your instance is in a VPC and you do not see a public DNS name, you must enable DNS hostnames. For more information, see DNS attributes for your VPC in the Amazon VPC User Guide.
Verify that your instance has a public IPv4 address. If not, you can associate an Elastic IP address with your instance. For more information, see Elastic IP addresses.
To connect to your instance using an IPv6 address, check that your local computer has an IPv6 address and is configured to use IPv6. For more information, see Configure IPv6 on your instances in the Amazon VPC User Guide.
Verify that your security group has a rule that allows RDP access. For more information, see Create a security group.
If you copied the password but get the error Your credentials did not work, try typing them manually when prompted. It's possible that you missed a character or got an extra white space character when you copied the password.
Verify that the instance has passed status checks. For more information, see Status checks for your instances and Troubleshoot instances with failed status checks (Amazon EC2 User Guide for Linux Instances).
Verify that the route table for the subnet has a route that sends all traffic destined outside the VPC to the internet gateway for the VPC. For more information, see Creating a custom route table (Internet Gateways) in the Amazon VPC User Guide.
Verify that Windows Firewall, or other firewall software, is not blocking RDP traffic to the instance. We recommend that you disable Windows Firewall and control access to your instance using security group rules. You can use AWSSupport-TroubleshootRDP to disable the Windows Firewall profiles using SSM Agent . To disable Windows Firewall on a Windows instance that is not configured for Amazon Systems Manager, use AWSSupport-ExecuteEC2Rescue, or use the following manual steps:

Stop the affected instance and detach its root volume.
Launch a temporary instance in the same Availability Zone as the affected instance.

Warning
If your temporary instance is based on the same AMI that the original instance is based on, you must complete additional steps or you won't be able to boot the original instance after you restore its root volume because of a disk signature collision. Alternatively, select a different AMI for the temporary instance. For example, if the original instance uses the Amazon Windows AMI for Windows Server 2016, launch the temporary instance using the Amazon Windows AMI for Windows Server 2019.
Attach the root volume from the affected instance to this temporary instance. Connect to the temporary instance, open the Disk Management utility, and bring the drive online.
Open Regedit and select HKEY_LOCAL_MACHINE. From the File menu, choose Load Hive. Select the drive, open the file Windows\System32\config\SYSTEM, and specify a key name when prompted (you can use any name).
Select the key you just loaded and navigate to ControlSet001\Services\SharedAccess\Parameters\FirewallPolicy. For each key with a name of the form xxxxProfile, select the key and change EnableFirewall from 1 to 0. Select the key again, and from the File menu, choose Unload Hive.
(Optional) If your temporary instance is based on the same AMI that the original instance is based on, you must complete the following steps or you won't be able to boot the original instance after you restore its root volume because of a disk signature collision.

Warning
The following procedure describes how to edit the Windows Registry using Registry Editor. If you are not familiar with the Windows Registry or how to safely make changes using Registry Editor, see Configure the Registry.
1. Open a command prompt, type regedit.exe, and press Enter.
2. In the Registry Editor, choose HKEY_LOCAL_MACHINE from the context menu (right-click), and then choose Find.
3. Type Windows Boot Manager and then choose Find Next.
4. Choose the key named 11000001. This key is a sibling of the key you found in the previous step.
5. In the right pane, choose Element and then choose Modify from the context menu (right-click).
6. Locate the four-byte disk signature at offset 0x38 in the data. Reverse the bytes to create the disk signature, and write it down. For example, the disk signature represented by the following data is E9EB3AA5:
```
...
0030  00 00 00 00 01 00 00 00
0038  A5 3A EB E9 00 00 00 00
0040  00 00 00 00 00 00 00 00
...
```
7. In a Command Prompt window, run the following command to start Microsoft DiskPart.
```
diskpart
```
8. Run the following DiskPart command to select the volume. (You can verify that the disk number is 1 using the Disk Management utility.)
```
DISKPART> select disk 1

Disk 1 is now the selected disk.
```
9. Run the following DiskPart command to get the disk signature.
```
DISKPART>  uniqueid disk

Disk ID: 0C764FA8
```
10. If the disk signature shown in the previous step doesn't match the disk signature from BCD that you wrote down earlier, use the following DiskPart command to change the disk signature so that it matches:
```
DISKPART> uniqueid disk id=E9EB3AA5
```
Using the Disk Management utility, bring the drive offline.

Note
The drive is automatically offline if the temporary instance is running the same operating system as the affected instance, so you won't need to bring it offline manually.
Detach the volume from the temporary instance. You can terminate the temporary instance if you have no further use for it.
Restore the root volume of the affected instance by attaching it as /dev/sda1.
Start the instance.

Verify that Network Level Authentication is disabled on instances that are not part of an Active Directory domain (use AWSSupport-TroubleshootRDP to disable NLA).
Verify that the Remote Desktop Service (TermService) Startup Type is Automatic and the service is started (use AWSSupport-TroubleshootRDP to enable and start the RDP service).
Verify that you are connecting to the correct Remote Desktop Protocol port, which by default is 3389 (use AWSSupport-TroubleshootRDP to read the current RDP port and change it back to 3389).
Verify that Remote Desktop connections are allowed on your instance (use AWSSupport-TroubleshootRDP to enable Remote Desktop connections).
Verify that the password has not expired. If the password has expired, you can reset it. For more information, see Reset a lost or expired Windows administrator password.
If you attempt to connect using a user that you created on the instance and receive the error The user cannot connect to the server due to insufficient access privileges, verify that you granted the user the right to log on locally. For more information, see Grant a Member the Right to Logon Locally.
If you attempt more than the maximum allowed concurrent RDP sessions, your session is terminated with the message Your Remote Desktop Services session has ended. Another user connected to the remote computer, so your connection was lost. By default, you are allowed two concurrent RDP sessions to your instance.

Error using the macOS RDP client

If you are connecting to a Windows Server instance using the Remote Desktop Connection client from the Microsoft website, you may get the following error:


Remote Desktop Connection cannot verify the identity of the computer that you want to connect to.

Download the Microsoft Remote Desktop app from the Mac App Store and use the app to connect to your instance.

RDP displays a black screen instead of the desktop

Try the following to resolve this issue:

Check the console output for additional information. To get the console output for your instance using the Amazon EC2 console, select the instance, and then choose Actions, Monitor and troubleshoot, Get system log.
Verify that you are running the latest version of your RDP client.
Try the default settings for the RDP client. For more information, see Remote Session Environment.
If you are using Remote Desktop Connection, try starting it with the /admin option as follows.
```
mstsc /v:instance /admin
```
If the server is running a full-screen application, it might have stopped responding. Use Ctrl+Shift+Esc to start Windows Task Manager, and then close the application.
If the server is over-utilized, it might have stopped responding. To monitor the instance using the Amazon EC2 console, select the instance and then select the Monitoring tab. If you need to change the instance type to a larger size, see Change the instance type.

Unable to remotely log on to an instance with a user that is not an administrator

If you are not able to remotely log on to a Windows instance with a user that is not an administrator account, ensure that you have granted the user the right to log on locally. See Grant a user or group the right to log on locally to the domain controllers in the domain.

Troubleshooting Remote Desktop issues using Amazon Systems Manager

You can use Amazon Systems Manager to troubleshoot issues connecting to your Windows instance using RDP.

AWSSupport-TroubleshootRDP

The AWSSupport-TroubleshootRDP automation document allows the user to check or modify common settings on the target instance that can impact Remote Desktop Protocol (RDP) connections, such as the RDP Port, Network Layer Authentication (NLA), and Windows Firewall profiles. By default, the document reads and outputs the values of these settings.

The AWSSupport-TroubleshootRDP automation document can be used with EC2 instances, on-premises instances, and virtual machines (VMs) that are enabled for use with Amazon Systems Manager (managed instances). In addition, it can also be used with EC2 instances for Windows Server that are not enabled for use with Systems Manager. For information about enabling instances for use with Amazon Systems Manager, see Managed nodes in the Amazon Systems Manager User Guide.

To troubleshoot using the AWSSupport-TroubleshootRDP document

Log in to the Systems Manager Console.
Verify that you are in the same Region as the impaired instance.
Choose Documents from the left navigation pane.
On the Owned by Amazon tab, enter AWSSupport-TroubleshootRDP in the search field. When the AWSSupport-TroubleshootRDP document appears, select it.
Choose Execute automation.
For Execution Mode, choose Simple execution.
For Input parameters, InstanceId, enable Show interactive instance picker.
Choose your Amazon EC2 instance.
Review the examples, then choose Execute.
To monitor the execution progress, for Execution status, wait for the status to change from Pending to Success. Expand Outputs to view the results. To view the output of individual steps, in Executed Steps, choose an item from Step ID.

AWSSupport-TroubleshootRDP examples

The following examples show you how to accomplish common troubleshooting tasks using AWSSupport-TroubleshootRDP. You can use either the example Amazon CLI start-automation-execution command or the provided link to the Amazon Web Services Management Console.