Windows build number:
26200
Your Distribution version:
24.04
Your WSL versions:
2.6.3.0
Steps to reproduce:
- Use WSL with WSLg enabled on Windows 11.
- Install the recent April 2026 Windows updates.
- Start WSL/WSLg, or launch any Linux GUI application.
- A Windows dialog titled "RemoteApp security warning" appears.
- The dialog shows:
- Unknown remote connection
- Unknown publisher
- a RemoteApp path like
dummy-entry
- an app ID / GUID
- At the same time, PowerShell shows that WSLg has started
mstsc.exe in the background using C:\Program Files\WSL\wslg.rdp.
WSL logs:
No response
WSL dumps:
No response
Expected behavior:
WSLg should establish its background RDP connection silently, or otherwise as a trusted internal connection, without showing an end-user RemoteApp security warning.
Actual behavior:
A RemoteApp security warning is shown for the WSLg background connection, even though I did not manually open any .rdp file. From the user perspective, this looks like an untrusted RemoteApp launch triggered by WSLg.
Additional information
- The issue started after installing recent Windows 11 April 2026 updates.
- I initially suspected
%USERPROFILE%\Documents\Default.rdp, but that does not appear to be the source of the warning:
Default.rdp is auto-generated by mstsc as expected
- it contains
remoteapplicationmode:i:0
- it does not contain obvious RemoteApp fields such as
remoteapplicationfile or remoteapplicationprogram
- The warning appears to be tied to the WSLg-launched background RDP connection instead.
This is the PowerShell command I used to inspect the process:
Get-CimInstance Win32_Process | Where-Object {$_.Name -match 'mstsc|msrdc'} | Select-Object Name, CommandLine
Windows build number:
26200
Your Distribution version:
24.04
Your WSL versions:
2.6.3.0
Steps to reproduce:
dummy-entrymstsc.exein the background usingC:\Program Files\WSL\wslg.rdp.WSL logs:
No response
WSL dumps:
No response
Expected behavior:
WSLg should establish its background RDP connection silently, or otherwise as a trusted internal connection, without showing an end-user RemoteApp security warning.
Actual behavior:
A RemoteApp security warning is shown for the WSLg background connection, even though I did not manually open any
.rdpfile. From the user perspective, this looks like an untrusted RemoteApp launch triggered by WSLg.Additional information
%USERPROFILE%\Documents\Default.rdp, but that does not appear to be the source of the warning:Default.rdpis auto-generated bymstscas expectedremoteapplicationmode:i:0remoteapplicationfileorremoteapplicationprogramThis is the PowerShell command I used to inspect the process: