Sending Ctrl+Alt+Del Over RDP: Why It Doesn’t Work and What to Do Instead
If you manage remote servers or support colleagues via Remote Desktop (RDP), you’ve likely run into this: you press Ctrl+Alt+Del to access the security screen—and nothing happens, or your own machine responds instead.
So, if you’re wondering how to send Ctrl Alt Del in Remote Desktop, you’re not alone. In fact, Windows intercepts this command at the hardware level, meaning it never reaches the remote session.
While it’s a built-in security feature, it can be frustrating. Fortunately, there are simple workarounds depending on your RDP client and platform.
Why Ctrl+Alt+Del Doesn’t Work Directly
Here’s what’s actually happening under the hood: Windows treats Ctrl+Alt+Del as something called a Secure Attention Sequence (SAS). In fact, Microsoft documents this behaviour as part of its Windows security architecture (see Windows security attention sequence documentation). Essentially, it’s a hardware-level interrupt that the local operating system has exclusive control over. As a result, no application—including your RDP client—can override it. The moment you press those three keys, your local machine responds, and the remote session never even sees the input.
Importantly, this is by design. The Secure Attention Sequence (SAS) prevents malicious software from faking login screens and stealing credentials, since only the operating system can respond to that key combination.
So, how do you send it to a remote machine? In practice, you have two options: either use a substitute shortcut your RDP client translates, or bypass local key capture entirely using alternative methods.
Ultimately, both approaches are reliable—it just depends on your setup.
The Primary Shortcut: Ctrl+Alt+End
For standard Windows Remote Desktop sessions using mstsc.exe, This is especially useful when managing hosted Windows environments or VPS servers from providers like HostingB2B:
Ctrl + Alt + End
RDP equivalent of Ctrl+Alt+Del
The RDP client intercepts Ctrl+Alt+End and transmits it to the remote machine as a Ctrl+Alt+Del signal. The remote Windows session responds identically to how it would respond to the physical key combination pressed locally.
Important limitation
This shortcut only works within a native Windows RDP client (mstsc.exe), it will not function in browser-based sessions, macOS clients, or most third-party viewers without additional configuration.
On-Screen Keyboard Method
The On-Screen Keyboard, launched inside the remote session, sends keystrokes directly to that remote operating system. Because the input originates on the remote machine, there is no local interception. This method works regardless of which client you are using.
- Connect to your Remote Desktop session and wait for it to be fully active.
- On the remote desktop, open the Run dialog with Win+R, type osk, and press Enter. Alternatively, search for “On-Screen Keyboard” in the Start menu.
- The On-Screen Keyboard window will appear on the remote desktop.
- Click Ctrl, then Alt, then Del on the on-screen keyboard in sequence.
- The Windows security screen will appear on the remote machine.
Alternative launch path
From the remote session, navigate to Settings → Accessibility → Keyboard and toggle on the On-Screen Keyboard, which keeps it available in the system tray for repeated use.
“The On-Screen Keyboard, launched inside the remote session, sends keystrokes directly to the remote OS — there is nothing for the local machine to intercept.”
Using the RDP Client’s Built-In Button
Most dedicated RDP clients expose a menu action that sends Ctrl+Alt+Del directly, without requiring any keyboard shortcut knowledge. This is particularly useful on macOS and mobile platforms where the keyboard layout differs significantly.
Windows — mstsc.exe (Full Screen)
- While in a full-screen RDP session, move your cursor to the top-centre of the screen to reveal the connection bar.
- Click the ellipsis (…) or keyboard icon in the bar.
- Select Send Ctrl+Alt+Delete from the menu.
macOS — Microsoft Remote Desktop
- While the remote session window is active, open the Connections menu from the macOS menu bar.
- Click Send Ctrl+Alt+Delete.
- Alternatively, use Cmd + Fn + Backspace, though this varies by keyboard model.
macOS note
Key mappings on macOS can differ between keyboard models and app versions. If the keyboard shortcut is inconsistent, the Connections menu method is the most reliable approach. If neither works, fall back to the On-Screen Keyboard method inside the remote session.
Need more macOS guidance?
macOS keyboard layouts, modifier key behaviour, and RDP client versions vary widely. If the methods above do not resolve your situation — or if you need guidance for a specific macOS version, keyboard model, or use case — ask directly and a tailored solution can be provided.
Web-Based RDP Clients
Browser-based RDP clients (such as Azure Virtual Desktop web client, Guacamole, or others) almost universally provide a toolbar or floating action panel with a dedicated Ctrl+Alt+Del button. Keyboard shortcuts reliably fail in browser sessions because the browser itself captures them first. Use the toolbar button exclusively for web-based sessions.
Citrix Workspace
Within Citrix sessions, the default shortcut is Ctrl+F2. If this has been remapped by your organisation’s policy, use the Citrix toolbar and look for the Send Keys or Ctrl+Alt+Del option.
Configuring Keyboard Passthrough
If Ctrl+Alt+End is not reaching the remote session even within mstsc.exe, your connection may be configured to handle keyboard shortcuts locally rather than passing them through. This is controlled by the Local Resources settings in the RDP connection dialog.
- Open Remote Desktop Connection (mstsc.exe) but do not connect yet.
- Click Show Options at the bottom left to expand the full dialog.
- Navigate to the Local Resources tab.
- Under the Keyboard section, locate the dropdown labelled “Apply Windows key combinations.”
- Change the value to On the remote computer.
- Save the setting and connect. Ctrl+Alt+End will now route correctly to the remote session.
| Keyboard Setting | Behaviour | Recommended for |
| On the local computer | All key combos handled locally; remote receives nothing | Local desktop work only |
| On the remote computer | Key combos passed through to remote session | Remote administration |
| Only when using full screen (default) | Passthrough enabled only in full-screen RDP mode | General use |
Quick Reference by Platform
| Client / Platform | Method | Notes |
| Windows RDP (mstsc.exe) | Ctrl + Alt + End | Standard; requires keyboard set to “On the remote computer” |
| macOS — Microsoft Remote Desktop | Connections menu → Send Ctrl+Alt+Delete | Most reliable macOS method; keyboard shortcut varies by model |
| Web-based RDP clients | Toolbar / action panel button | Keyboard shortcuts blocked by browser; use UI exclusively |
| Citrix Workspace | Ctrl + F2 or toolbar | May be remapped by organisational policy |
| Mobile RDP apps | Virtual keyboard panel button | Dedicated special-key buttons in most mobile clients |
| All clients (universal fallback) | On-Screen Keyboard (osk.exe) inside the remote session | Works in every scenario; platform-independent |
Common Problems and Fixes
Symptom Resolution
Ctrl+Alt+End has no effect Open Local Resources in mstsc.exe and set keyboard combos to “On the remote computer.” Ensure the RDP window is in focus.
Shortcut triggers the local machine instead Switch to full-screen mode or change the Local Resources keyboard setting permanently.
Browser-based session ignores all shortcuts Expected behaviour. Use the client toolbar button or use the On-Screen Keyboard inside the remote session.
Nested RDP session (RDP within RDP)Press Ctrl+Alt+End once per nesting level. For the innermost session, the On-Screen Keyboard is the most dependable approach.
macOS shortcut inconsistent Use the Connections menu method. If unavailable, launch the On-Screen Keyboard inside the remote session.
The Quick Answer — and What to Do When It Doesn’t Work
For most standard Windows RDP sessions, first of all, Ctrl+Alt+End is your go-to. It’s the direct substitute, it works immediately, and there’s no setup required. In fact, if you’re on a Windows machine connecting to another Windows machine, you should try this before anything else.
However, it won’t always be available. For example, if you’re connecting from a Mac, working through a browser-based RDP client, or you’re inside a nested remote session, Ctrl+Alt+End may do nothing — and that’s where people get stuck. In those cases, the universal fallback is the On-Screen Keyboard, launched from within the remote session itself. While it may sound old-fashioned, it works without exception regardless of your platform, client, or how many sessions deep you are.
If that still doesn’t work, don’t go down a rabbit hole of reboots and reinstalls just yet. Instead, check one common setting: the keyboard passthrough configuration under Local Resources in your RDP connection settings. Ultimately, this option determines whether key combinations are forwarded to the remote machine or intercepted by your local OS — and it’s frequently overlooked.
