Sending CTRL-ALT-DEL to a second remote desktop session in Windows requires using the keyboard shortcut Ctrl+Alt+End instead of the standard Ctrl+Alt+Delete. This key combination acts as a bridge, translating your local input into the secure attention sequence for the remote machine. Because RDP intercepts the original keys for its own security functions, you must use this specific alternative to trigger the login screen or task manager on the target system.
Understanding the Double-Hop Challenge
When you connect to a remote computer via Remote Desktop Connection (RDC), the client application captures certain control sequences locally to prevent accidental triggers. The standard Ctrl+Alt+Delete sequence is one such protected command, reserved for the local operating system's security layer. In a single-hop scenario, this limitation is manageable because you are interacting directly with one remote host. However, when you attempt to send this signal from within an already established remote session—a "double-hop" scenario—the RDP client on the first remote machine does not automatically forward the keystroke to the second machine.
This architectural design prevents security breaches where a compromised first server could inject commands into a more sensitive second server without user intervention. Consequently, users often find themselves stuck, unable to log in to the second server or access its Task Manager because the expected key combo simply disappears into the void of the first session. Recognizing that the RDP protocol has built-in translation for these events is the first step toward resolving the issue.
The Primary Solution: Using Ctrl+Alt+End
The most straightforward and universally supported method for sending the Secure Attention Sequence (SAS) to a remote machine is the key combination Ctrl+Alt+End. When you press these three keys while focused on the RDP window, the client software translates them into the SAS event for the remote host. This works effectively for both the initial connection and subsequent double-hop connections.
To ensure this works correctly, follow these steps:
- Focus the Window: Click inside the Remote Desktop window so that it is the active application. If another window is selected, the keys may be intercepted by the local OS.
- Press the Keys: Hold down Ctrl and Alt, then press End. You should see the Windows Security screen appear on the remote machine.
- Verify Behavior: If you are in a double-hop scenario, remember that you need to do this twice. First, from your local machine to the first remote server, and second, from the first remote server to the second remote server.
It is important to note that on some international keyboard layouts or compact laptops, the End key might be combined with other functions. In such cases, you may need to hold Fn or Shift alongside Ctrl+Alt+End. If the standard shortcut fails, check your keyboard layout settings in the RDP client options to ensure no remapping is occurring.
Alternative Methods for Advanced Users
While Ctrl+Alt+End is the standard, there are scenarios where it might be inconvenient, such as when using a touch keyboard or if the key combination conflicts with local shortcuts. Microsoft provides alternative ways to invoke the secure attention sequence through the RDP interface itself.
One reliable method is using the On-Screen Keyboard (OSK). Open the Start menu on the remote machine and search for "On-Screen Keyboard." Once open, click the Ctrl, Alt, and Del buttons displayed on the virtual keyboard. This mimics the physical key press and triggers the same system response. Another approach involves using the Taskbar menu. Right-click the Start button on the remote machine and select "Task Manager." From there, you can navigate to File > Run new task to execute commands or restart processes, bypassing the need for the SAS entirely in many administrative contexts.
For persistent issues, consider checking the RDP client configuration. Go to Show Options in the connection dialog, navigate to the Local Resources tab, and verify that the "Apply Windows key combinations" setting is set to "In full screen mode." Changing this to "Only when using the full screen" can sometimes resolve conflicts where local shortcuts interfere with remote commands. If you experience connectivity delays during these operations, refer to our guide on
Troubleshooting Slow Connecting Times for Remote Desktop on Windows 10 to optimize network performance.
Troubleshooting Common Issues
If Ctrl+Alt+End does not produce the expected result, several factors could be at play. First, ensure that you are running the latest version of the Microsoft Remote Desktop client. Older versions may have bugs related to key translation, especially in complex multi-session environments. Second, check for group policy restrictions. Administrators can disable the ability to send SAS commands via RDP for security reasons. If you suspect this is the case, contact your IT department to verify current policies.
Another common pitfall is the state of the remote machine. If the remote session is hung or unresponsive, keyboard inputs will not register. In this case, try using the RDP disconnect feature rather than closing the window, which allows the session to remain active but disconnected. This preserves your state and allows you to reconnect and retry the key combination. For users dealing with display issues after reconnection, such as black screens, consult our article on
Fixing Black Screen Issue in Windows 10 Pro RDC. Additionally, ensuring your RDP client does not sleep during long sessions is crucial; see
Prevent sleep for RDP client for tips on maintaining stability.
Frequently Asked Questions
Why doesn't Ctrl+Alt+Delete work in my RDP session?
The standard Ctrl+Alt+Delete keys are intercepted by the local operating system for security purposes and do not pass through to the remote machine. You must use the translated sequence Ctrl+Alt+End to trigger the secure attention sequence on the remote host.
Can I change the default key combination for RDP?
No, the Ctrl+Alt+End translation is hardcoded into the RDP protocol client for security consistency. While you cannot change the mapping, you can use the On-Screen Keyboard or Task Manager alternatives if the physical keys are unavailable.
What if I am using a Mac as my RDP client?
On macOS, the equivalent key combination is Command+Option+Esc. This sends the interrupt signal to the remote Windows session, allowing you to access the Task Manager or logout screen just as you would with Ctrl+Alt+End on Windows.
Does this method work for non-Windows remote servers?
This specific solution applies to Windows Remote Desktop clients connecting to Windows hosts. If you are using third-party tools like VNC or SSH, the key handling differs significantly, and you should consult the documentation for those specific applications.
How do I handle multiple remote sessions simultaneously?
You must apply the Ctrl+Alt+End sequence separately to each active RDP window. Each session maintains its own context, so focusing on one window and pressing the keys will only affect that specific remote machine.