A Remote Desktop security warning appears when you open an .rdp file in Windows 11, even if it worked before. The April 2026 security updates added checks for the destination and the access the file requests.
What Is Remote Desktop Connection?
Remote Desktop Connection is the Windows app that opens .rdp files and connects to another PC. It’s built into Windows 11. An .rdp file can name a remote PC and request access to local resources, such as your clipboard or drives.
You may see two messages. A one-time educational warning explains the security change the first time you open an .rdp file on that device. The connection security dialog shows a file’s destination, publisher, and requested resources before you connect. It can appear again for another file or session.
Prerequisites
- A Windows 11 PC with current cumulative updates.
- An
.rdpfile you expected to receive, or permission to connect to a known remote PC. - The remote PC’s address or name, confirmed by its owner or your IT team.
- A username and password for an account allowed to use the remote PC.
- Network access to the remote PC, such as the same local network or your organization’s VPN.
- If you’re setting up your own remote PC: Windows 11 Pro, Enterprise, or Education on that PC. Windows 11 Home can connect to a remote PC but can’t host a connection using Windows’ built-in Remote Desktop feature.
Step-by-Step Guide
Fix #1: Check your Windows version and updates
- On the PC you’ll connect from, open Settings > System > About. Under Windows specifications, note the Version and OS build. These tell you which updates apply to your PC.
- Open Settings > Windows Update and click Check for updates. Install the current cumulative update offered for your Windows 11 release. Restart if prompted.
Expected result: Windows says your PC is up to date after any required restart. The .rdp warning change began with the April 2026 security updates. The update you need depends on your Windows 11 release.
Fix #2: Enable Remote Desktop on the remote PC
If work or school supplied your .rdp file, IT may have set up the remote PC already. Use this fix when you control the PC you want to reach.
- On the remote PC, open Settings > System > Remote Desktop.
- Turn on Remote Desktop, then click Confirm if Windows asks. Leave Require devices to use Network Level Authentication to connect enabled if it appears.
Expected result: The page says Remote Desktop is on and shows the PC name you can use.
- Write down the PC name shown on that page. Keep the remote PC on and connected to the network.
- Make sure the account you plan to use has a password. If it isn’t an administrator account, select Remote Desktop users on the same page and add it.
Expected result: The account is listed as allowed to connect. If the setting is unavailable on a managed work PC, ask IT to enable access.
- If you’re outside the remote PC’s local network, connect to your organization’s VPN using its instructions. For a home setup, use a trusted VPN or another approved method instead of opening Remote Desktop directly to the internet.
Fix #3: Verify the .rdp file before opening it
- Check how you received the file. If you didn’t request it, contact the supposed sender another way, such as at a phone number you already know.
- Ask the sender or remote PC’s owner for the expected computer name or address. Compare it with the PC you intend to reach. If your employer supplied the file, check its setup instructions for the address.
- In File Explorer, find the
.rdpfile and check its name and source. A familiar filename doesn’t prove its contents are safe.
Expected result: You know who sent the file and which remote address you should see. If either detail is unclear, stop and verify it before opening the file.
Fix #4: Open the file and review the connection warning
- Double-click the verified
.rdpfile in File Explorer. If Windows asks which app to use, choose Remote Desktop Connection. You can also search Start for Remote Desktop Connection, or runmstsc.exe. Opening the client manually does not trigger the new file-specific warning; open your verified.rdpfile to review that warning.
- If you see the first-time educational warning, read it and continue to the connection details. This message explains the change. It doesn’t verify the file you opened, and it may appear only once on your PC.
- In the connection security dialog, compare the remote computer address with the one you confirmed in Fix #3. Check the publisher field too.
Expected result: The address matches your intended destination. “Unknown publisher” means Windows can’t verify who signed the .rdp file. It alone doesn’t mean the file is malicious. A recognized signature also doesn’t prove the connection is appropriate. Check the sender and address either way.
- If the address, sender, or publisher details are unexpected, click Cancel. Confirm the file with its sender or IT before trying again.
Fix #5: Allow only the resources this session needs
The April 2026 change leaves requested local-resource sharing off by default. Clipboard copying or drive sharing may seem broken even when the connection succeeds.
- In the connection security dialog, review each resource the file requests. Depending on the file and your Windows release, you may see clipboard, drives, printers, cameras, and other devices.
- Enable only what you need for this session. For example, allow clipboard access to copy text between PCs. Leave drive access off unless you need to transfer files.
- Click Connect once the destination and requested access match what you expected. Enter the remote account’s credentials when prompted.
Expected result: The remote desktop opens. Only the local resources you approved are available to that session. To change a resource choice, disconnect and review the choices when you reconnect.
Fix #6: Check the connection if the desktop does not open
- Make sure the remote PC is on, connected to its network, and still has Remote Desktop enabled under Settings > System > Remote Desktop.
- Check that you’re connected to the required local network or VPN.
- Recheck the remote PC name or address and the username you entered. If IT sent the
.rdpfile, report any mismatch. Don’t edit an unfamiliar address just to make it connect.
Expected result: A reachable PC with an allowed account accepts the connection. If you still get an error after the security dialog, record its exact wording. The warning and connection failure may have separate causes.
Configuration: Common Resource Choices
| Resource | Enable it when you need to… | Leave it off when… |
|---|---|---|
| Clipboard | Copy text or other supported content between PCs | Nothing needs to move between them |
| Drives | Open or transfer files from your local drive in the remote session | The session does not need local files |
| Printers | Print remote documents on your local printer | You will not print locally |
| Camera | Use your local camera in a remote meeting or app | The remote session has no camera task |
| Other devices | Use a specific device required by the remote app | You do not recognize the request |
These choices control what the remote session can access on your local PC. If you use a USB headset, webcam, external SSD, or docking station, check which device the session needs before granting access. Your organization may restrict some choices.
Tips and Troubleshooting
“Unknown publisher” appears on an expected file
An unsigned .rdp file can show “Unknown publisher”. Compare its address with one you got independently. If anything differs, confirm the file with its sender. Cancel if you can’t verify it. You don’t need to whitelist every expected file or suppress the dialog to use Remote Desktop.
Clipboard, drives, or printers are missing
Disconnect and reopen the verified .rdp file. In the security dialog, enable the resource you need before connecting. If the choice is unavailable or stays disabled on a managed PC, ask IT whether organization policy blocks it.
An expected .rdp file is blocked on a work PC
Your organization may require files signed by a trusted publisher or block unsigned files. Send IT the file’s source, expected remote address, publisher, and exact block message. IT manages trusted-publisher policy on work PCs. Changing Group Policy or the registry yourself can conflict with those settings.
The warning is clipped or its controls overlap
Microsoft documented display problems with the warning on some setups using monitors with different scaling percentages. Open Settings > Windows Update, install the current cumulative update for your Windows 11 release, and restart. If you still can’t read the dialog, cancel it. Send IT your Windows version and OS build from Settings > System > About. Don’t approve a connection whose details you can’t read.
The first-time message keeps appearing
The educational message introduces the change. The connection security dialog reviews a specific connection. If the educational message keeps returning, record its exact wording and your Windows build for IT. Review each connection security dialog when it appears.
For Microsoft’s details, see Understanding security warnings for RDP files. Microsoft also documents managed-device RDP file policy and the April 14, 2026 Windows 11 update.
Wrapping Up
Check the address and allow only the access you need. If a verified connection fails or its details change, cancel and check with the sender or IT before connecting.