I don’t want to create an Issues/Request post if this is just me/my issue.
I only connect to jump server occasionally, every week or two or whatever. Starting about last week or so, when I connect, it spuriously loses connection constantly…about every 30-60 seconds, then reconnects in a few seconds right back to whatever state it was in when connection was lost. Then disconnects again in a minute or two.
I update Windows once a month around the first, last time being about 9 days ago, so that may be a difference in my system between when I remember it was OK to now that might account for this?
So if anyone else has same general issue, it probably means something.
If this is recent (several months ago for users on the beta track, relatively recently for those on normal updates), on Windows 11, its likely due to a Windows change. This is likely the case for you guys.
Here’s a pretty quick fix - I tried to make this easy, let me know if its not. If you’re unsure about this, please don’t hesitate to run it past a trusted IT resource, it won’t hurt my feelings
One thing to note - this requires local admin access, and if you’re using a corporate laptop, the setting may also be overridden by IT during the next policy refresh. If its your personal computer and you can install software, you should be able to do this just fine.
Another note: If this is a corporate laptop you’re working on, I highly suggest NOT doing this - instead, reach out to your IT team and forward them this message, if necessary - it’s a whole different animal when it’s not a simple home PC.
(Reference: KB5051987)
Open a command prompt (in the search bar, type Command then click on Command Prompt when it pops up at the top
In the Command Prompt window, type the following and hit enter: gpedit
. When the Local Group Policy Editor window shows up, navigate to
→ Local Computer Policy
→ Computer Configuration
→ Administrative Templates
→ Windows Components
→ Remote Desktop Services
→ Remote Desktop Connection Client
Double click on Turn Off UDP on the Client, choose Enabled, and click OK
Close the Local Group Policy Editor window
Back in the Command Prompt window, type the following: gpupdate /force
Once the Computer policy update has been completed successfully and User Policy update has been completed successfully messages appear, close the Command Prompt window
If step 7 fails: just reboot your computer normally
Instructions were straightforward…thanks. But…sigh…Microdumb by default does not make the Group Policy Editor (gpedit.msc) available on Windoze 11 Home editions (and probably other home editions as well.
People can/should do their own research, or verify the following for themselves, but I enabled Gpedit by executing the following commands in an elevated command prompt window:
FOR %F IN ("%SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~*.mum") DO (DISM /Online /NoRestart /Add-Package:"%F")
FOR %F IN ("%SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~*.mum") DO (DISM /Online /NoRestart /Add-Package:"%F")
Results should look something like (check all commands for successful completion):
Microsoft Windows [Version 10.0.26100.3476]
(c) Microsoft Corporation. All rights reserved.
C:\Windows\System32>gpedit
'gpedit' is not recognized as an internal or external command,
operable program or batch file.
C:\Windows\System32>FOR %F IN ("%SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~*.mum") DO (DISM /Online /NoRestart /Add-Package:"%F")
C:\Windows\System32>(DISM /Online /NoRestart /Add-Package:"C:\WINDOWS\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1591.mum" )
Deployment Image Servicing and Management tool
Version: 10.0.26100.1150
Image Version: 10.0.26100.3476
Processing 1 of 1 - Adding package Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1591
[==========================100.0%==========================]
The operation completed successfully.
C:\Windows\System32>(DISM /Online /NoRestart /Add-Package:"C:\WINDOWS\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.3037.mum" )
Deployment Image Servicing and Management tool
Version: 10.0.26100.1150
Image Version: 10.0.26100.3476
Processing 1 of 1 - Adding package Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.3037
[==========================100.0%==========================]
The operation completed successfully.
C:\Windows\System32>(DISM /Online /NoRestart /Add-Package:"C:\WINDOWS\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.3323.mum" )
Deployment Image Servicing and Management tool
Version: 10.0.26100.1150
Image Version: 10.0.26100.3476
Processing 1 of 1 - Adding package Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.3323
[==========================100.0%==========================]
The operation completed successfully.
C:\Windows\System32>(DISM /Online /NoRestart /Add-Package:"C:\WINDOWS\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~~10.0.26100.1591.mum" )
Deployment Image Servicing and Management tool
Version: 10.0.26100.1150
Image Version: 10.0.26100.3476
Processing 1 of 1 - Adding package Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~~10.0.26100.1591
[==========================100.0%==========================]
The operation completed successfully.
C:\Windows\System32>(DISM /Online /NoRestart /Add-Package:"C:\WINDOWS\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~~10.0.26100.3194.mum" )
Deployment Image Servicing and Management tool
Version: 10.0.26100.1150
Image Version: 10.0.26100.3476
Processing 1 of 1 - Adding package Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~~10.0.26100.3194
[==========================100.0%==========================]
The operation completed successfully.
C:\Windows\System32>(DISM /Online /NoRestart /Add-Package:"C:\WINDOWS\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~~10.0.26100.3470.mum" )
Deployment Image Servicing and Management tool
Version: 10.0.26100.1150
Image Version: 10.0.26100.3476
Processing 1 of 1 - Adding package Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~~10.0.26100.3470
[==========================100.0%==========================]
The operation completed successfully.
C:\Windows\System32>FOR %F IN ("%SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~*.mum") DO (DISM /Online /NoRestart /Add-Package:"%F")
C:\Windows\System32>(DISM /Online /NoRestart /Add-Package:"C:\WINDOWS\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1.mum" )
Deployment Image Servicing and Management tool
Version: 10.0.26100.1150
Image Version: 10.0.26100.3476
Processing 1 of 1 - Adding package Microsoft-Windows-GroupPolicy-ClientExtensions-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
[==========================100.0%==========================]
The operation completed successfully.
C:\Windows\System32>(DISM /Online /NoRestart /Add-Package:"C:\WINDOWS\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~31bf3856ad364e35~amd64~~10.0.26100.1591.mum" )
Deployment Image Servicing and Management tool
Version: 10.0.26100.1150
Image Version: 10.0.26100.3476
Processing 1 of 1 - Adding package Microsoft-Windows-GroupPolicy-ClientExtensions-Package~31bf3856ad364e35~amd64~~10.0.26100.1591
[==========================100.0%==========================]
The operation completed successfully.
C:\Windows\System32>(DISM /Online /NoRestart /Add-Package:"C:\WINDOWS\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~31bf3856ad364e35~amd64~~10.0.26100.3037.mum" )
Deployment Image Servicing and Management tool
Version: 10.0.26100.1150
Image Version: 10.0.26100.3476
Processing 1 of 1 - Adding package Microsoft-Windows-GroupPolicy-ClientExtensions-Package~31bf3856ad364e35~amd64~~10.0.26100.3037
[==========================100.0%==========================]
The operation completed successfully.
C:\Windows\System32>(DISM /Online /NoRestart /Add-Package:"C:\WINDOWS\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~31bf3856ad364e35~amd64~~10.0.26100.3323.mum" )
Deployment Image Servicing and Management tool
Version: 10.0.26100.1150
Image Version: 10.0.26100.3476
Processing 1 of 1 - Adding package Microsoft-Windows-GroupPolicy-ClientExtensions-Package~31bf3856ad364e35~amd64~~10.0.26100.3323
[==========================100.0%==========================]
The operation completed successfully.
C:\Windows\System32>
Portable edition seems to work nicely, is no-cost (unless you want/need some bells/whistles), independent of mstsc. Might make for good troubleshooting, even if you don’t want to use it full-time.
Thinking about the streaming video keeping the connection up…
I’m betting this has something to do with the UDP port translations in the different firewalls. Given UDP’s stateless nature, firewalls, especially stricter firewalls, will have small inactivity timers for tearing down UDP translations. This used to bite us all the time when folks put things like PIX/ASA in front of their lower-end VoIP switches. It may even be related to the windows host firewall.
It would make sense that streaming video through RDP would utilize UDP - after all, that’s what some competitive technologies like Teredici’s PCoIP and VMware’s Blast are using. Constant video streaming means constant UDP flow, which should keep translations from being torn down. I don’t know enough about how RDP uses UDP to be sure, but this makes sense.
