Windows April 2026 Update: New RDP Security Warnings and How to Fix Them

If your team uses Remote Desktop and suddenly started seeing new warning dialogs or lost access to local drives, clipboard, and printers during remote sessions — you're not alone. Microsoft's April 2026 security update (KB5083769) made significant changes to how Windows handles .rdp files.

Here's what changed, why Microsoft did it, and how to fix it for your business.

---

What Changed

Starting with the April 2026 update, the Remote Desktop Connection app (mstsc.exe) now shows a new security dialog every time you open an .rdp file. This dialog:

• Shows the remote computer address before connecting
• Lists every local resource the RDP file wants to access (drives, clipboard, printers, cameras, etc.)
• Sets all resource sharing to OFF by default — you must manually re-check each one
• Removes the "Don't ask me again" checkbox for unsigned RDP files

This means if your team has been double-clicking saved .rdp shortcuts to connect to work, they'll now need to manually enable drive mapping, clipboard, and printers every single time.

---

Why Microsoft Made This Change

This update addresses CVE-2026-26151, a vulnerability where attackers were sending malicious .rdp files through phishing emails. When a victim opened the file, their computer would silently connect to an attacker-controlled server and share local drives, clipboard, and credentials — without the user realizing what was happening.

By forcing users to explicitly opt in to each resource redirect, Microsoft is making it much harder for these phishing attacks to succeed.

---

Who Is Affected

• Affected: Anyone who opens saved .rdp files or shortcuts to connect to remote computers
• Not affected: Manual connections where you type the computer name directly into Remote Desktop Connection
• Not affected: Azure Virtual Desktop and Windows 365 connections (these are signed by Microsoft)

---

How to Fix It

Option 1: Digitally Sign Your RDP Files (Recommended)

The best long-term solution is to digitally sign your RDP files with a code-signing certificate. Signed files show your organization's name in the security dialog instead of "Unknown publisher," and your IT admin can configure Windows to trust your publisher — reducing or eliminating the warning.

You can sign RDP files using PowerShell:

# Get your code-signing certificate
$cert = Get-ChildItem Cert:\CurrentUser\My -CodeSigningCert | Where-Object { $_.Subject -like "*Your Company*" }

# Sign the RDP file
Set-AuthenticodeSignature -FilePath "C:\Path\To\connection.rdp" -Certificate $cert -HashAlgorithm SHA256

Once signed, your IT department can deploy a Group Policy to trust your publisher, making the experience seamless for your team.

Option 2: Temporary Registry Workaround

If you need an immediate fix while you set up certificate signing, you can revert to the old dialog behavior with a registry change:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Terminal Services\Client]
"RedirectionWarningDialogVersion"=dword:00000001

Important: Microsoft has warned that this registry setting will be removed in a future update. This is a temporary fix only — plan to transition to signed RDP files.

Option 3: Train Users to Re-Check Boxes

For small teams, the simplest approach is to inform users about the new dialog and instruct them to:

1. Verify the remote computer address is correct
2. Check the boxes for the resources they need (drives, clipboard, printers)
3. Click Connect

This is the least ideal option since it adds friction to every connection, but it requires no technical changes.

---

What Resources Are Affected

The new dialog shows checkboxes for all of these, all unchecked by default:

• Drives — Local hard drives, USB drives, and mapped network drives
• Clipboard — Copy/paste between local and remote
• Printers — Local printers available in the remote session
• Smart cards / Windows Hello — Authentication credentials
• Microphones — Audio recording devices
• Cameras — Video capture devices
• Ports — Serial and parallel ports

---

Our Recommendation

For businesses that rely heavily on Remote Desktop, we recommend a two-step approach:

1. Apply the registry workaround now to stop the disruption to your team
2. Set up RDP file signing within the next few months before Microsoft removes the workaround

If you're managing multiple workstations, both of these can be deployed via Group Policy — no need to touch each machine individually.

---

Need Help?

If your team is struggling with the new RDP warnings and you need help deploying the fix across your organization, contact ITP 360. Our managed IT team can deploy the registry fix, set up certificate signing, and configure Group Policy for your entire network — so your team can get back to work without the hassle.