The 2282 issue with the update is this, fixed or do I have to go around the work around, thank you.
It actually seems worse now than before. At this point I'm stuck using PIRO to force high priority which is also a workaround for it.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
All of our Remote Desktop Users using Windows 11 are having problems connecting to Remote Desktop after installing this update. It just hangs at connecting.
We have found that there is a bug in the Remote Desktop client so that it is only trying the UDP connection and not trying TCP connection. We only allow the port 443 connection through on our firewall.
The only workaround we have found is to make the following change on the Windows 11 computer.
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
Otherwise the Remote client just keeps trying to connect via UDP.
This issue did not start until the Windows 11 update was installed over the last couple days.
Jeff
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
The 2282 issue with the update is this, fixed or do I have to go around the work around, thank you.
It actually seems worse now than before. At this point I'm stuck using PIRO to force high priority which is also a workaround for it.
I took the 22H2 update on one of my other devices, a laptop, about a week ago and it resulted in the connectivity issue, so I do not think it is resolved. I did the registry work around on one of my other devices (desktop) a few weeks ago and it is working fine.
Great finding! Thanks for help.
That really only works if you're one of the few people where manually forcing a port for it, works. In my case and others? Nope. Sad to say, while I like the gaming changes that were stuck into Win11. Win10 is acting in a far more reasonable and less painful way, between this and the LSA errors. But that's a whole 'nother problem.
edit: As of the update pushed for KB5018496, this seems to be fixed at least on my end.
I do not have this registry entry on my win 11 pro