By Dushmantha Charaka 2026-04-20
Starting with the April 2026 Windows Security Update, Microsoft introduced a new layer of protection for Remote Desktop Protocol (RDP) users. While this is a great step forward to combat phishing attacks that abuse .rdp files, it has become a significant friction point for IT administrators and power users who connect to trusted servers daily.
If you are tired of seeing the pop-up “Verify the publisher of this remote connection” or the “Review resource redirection” dialog every single time you open an RDP file, this guide provides the full background and the permanent fix.
The Problem: What Changed in April 2026?
Microsoft identified a growing trend of hackers sending malicious .rdp files via email. When opened, these files connect the victim's computer to an attacker-controlled server and silently map local drives and the clipboard, leading to data theft.
To stop this, Windows now does the following every time you open an RDP file:
Publisher Warning: Displays a large, yellow "Caution" banner if the RDP file is not digitally signed.
Resource Review: Forces you to manually check boxes to allow Clipboard, Drive, or Printer sharing. These are unchecked by default, breaking automated workflows.
One-Time Education Prompt: An extra pop-up explaining the phishing risk.
For a home lab or a secure internal corporate network, this is overkill. Here is how to turn it off.
The Solution: Disabling the Warning Dialog via Registry
To revert to the classic connection behavior (where it connects immediately if you trust the destination), we need to add a specific DWORD value to the Windows Registry.
What this registry change does:
It tells Windows, "I understand the security risk. Do not show me the new resource redirection warning dialog. I accept the legacy behavior."
Download Fix (Vilified Google Drive)
Method 1: Manual Fix (For a Single Computer)
Follow these steps carefully:
Press Windows Key + R, type regedit, and press Enter.
Navigate to the following path (you can copy and paste this into the Regedit address bar):
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client
Note: If the Client folder does not exist, right-click on Terminal Services, select New > Key, and name it Client.
In the right-hand pane, right-click an empty space and select New > DWORD (32-bit) Value.
Name the new value exactly:
RedirectionWarningDialogVersion
Double-click the new value and set the Value data to 1.
Click OK and close Registry Editor.
Result: The next time you open an .rdp file, the connection will initiate without the extra resource review step.
Method 2: Automated Fix (Deploy to Multiple Users)
If you are managing multiple computers or want to send this fix to a colleague, use one of the scripts below.
Option A: .REG File (Registry Import)
Copy the text below into Notepad and save it as Disable_RDP_Warning.reg. Then, right-click the file and select Merge.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client]
"RedirectionWarningDialogVersion"=dword:00000001
Important: This must be executed with Administrator Privileges because it modifies HKLM\Software\Policies.
Option B: PowerShell Command (Run as Admin)
Open PowerShell as Administrator and paste this line:
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client" -Name "RedirectionWarningDialogVersion" -Value 1 -Type DWord -Force
Important Security Note from Microsoft
Before you apply this fix, remember why Microsoft added this feature. Do not disable this warning on computers used by non-technical staff who frequently open email attachments.
A digitally signed RDP file does not mean it is safe. Attackers can purchase code signing certificates under names like "Microsft" (note the typo) to trick users. If you disable this dialog, ensure your users are trained never to open RDP files received via email.
Conclusion
The April 2026 update is a solid security enhancement for the average user, but it's a nuisance for IT professionals. By adding the RedirectionWarningDialogVersion = 1 registry key, you regain control over your workflow and eliminate the constant connection friction.
Have you encountered this warning in your environment? Let us know in the comments below if this fix worked for you
){kind=link}
0 Comments