This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 8%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
I have confirmed there is some kind of problem with Windows 11 22H2 and Remote Desktop published apps. Seemingly all RDS implementation versions dating back to 2012 R2 have the same problem. The gateway itself works fine. Published apps work fine also, even on farms with many host servers. The problem is once the APP is spawned, it never appears at the desktop. Is there a known workaround or is this a known issue with 22H2 perhaps?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(64, 47%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEB%3C/text%3E%3C/svg%3E)
we have the same experience. We stuck also in the RDP Session as above and had to rollback the client to solve this issue.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 24%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJC%3C/text%3E%3C/svg%3E)
We have had the issue as well. I believe the problem is due to the fact that the RDS connection is trying to connect over UDP and is not trying to connect over TCP if the UDP fails.
If you add the following registry setting the Remote Desktop Connection will work.
Have to set this value to 1 in the registry for Windows 11 client to work outside the network
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client
KEY VALUE - fClientDisableUDP SET TO 1
I am on the early adopter program with Microsoft and raised this exact issue with Microsoft when the beta came out for Windows 11 and they did not fix the issue.
UDP port 3391 should be open, this speeds up high bandwidth file transfers for gateway connections. This setting destroys file transfer speeds, printing, video and audio there. It's interesting that it has an effect with 22H2. This is good info.
Can you provide any details or measures as to how disabling UDP destroys transfer speeds, etc? We have not been allowing UDP into our network via firewall opting for TCP only for RDP connections for a couple years and have had no issues with any of those items you have mentioned.
This issue here is related to apps not appearing, not RDS gateway sessions so this is a bit out of scope for the issue here but has some relevance.
The RDS gateway has two functions, it can host apps and can act as an RDP gateway. It's the gateway part that suffers without UDP 3391. There's a reason it's there in the gateway config. Some protocols simply aren't appropriate for TCP. Things like file transfer, video and audio for instance, they never transfer via TCP well and it gets worse when the distance (RTT) is extreme. SIP is always UDP for this same reason. To demonstrate. Pick a gateway user at least 1000 miles from the RDS gateway. Block UDP 3391. Drag and drop a file onto a remote PC through the gateway. Without UDP 3391, transfer will occur slowly. The same test transfers faster with UDP