Windows 11 - Remote Desktop stuck on "Estimating connection Quality"

Joseph McGuinness 36

Hi all,

I'm having a problem with remote desktop getting stuck on the "Estimating connection quality" stage, but what's strange is that this is only affecting Windows 11 PCs within my organisation. Has anyone experienced this problem specifically with Windows 11 whilst seemingly not affecting Windows 10 machines at all? So far, I've established that using a WiFi connection on 2.4Ghz, 5Ghz, or a LAN cable makes no difference. I appreciate any help on this matter.

Kind Regards,

Joe

Daniel Ström 6 Reputation points

2022-10-11T17:25:38.063+00:00

Same problem but when I take a fresh Windows 11 machine it works. But not on the Windows 11 machine that the RDP had worked before. Have tho Windows 11 computers at work now that cant connect o our servers Windows Server 2012.
Same updates on both but the diffrence is that the machine that works has a fresh setup works correctly. I you press stpoo on the "Estimating connection Quality" you can se that RDP software has gon stuck and you need to X it down. So somthing is wrong since some update on windows 11 or Windows 2012 Server
GSinnema 6 Reputation points

2022-10-14T09:30:59.157+00:00

Same problem here; Windows Home 11 (22H2) using MSTSC version 10.0.22621 unable to connect to RDS running on Server 2019 via RDWGateway running on Server 2019 remotely
When on local network connecting via the RDWGateway the connection works flawlessly.
Cleaned RDclient bitmap cache & cleaned registry under: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default
This solves the problem once.
Next logon the client hangs again on estimating connection quality...

W11 Pro and W10 clients are not affected in my situation :/

2 answers

Joseph McGuinness 36 Reputation points

2022-10-14T10:12:07.73+00:00
Hi all,

I've come across a temporary solution to this problem.

Run Regedit.exe

Navigate to: hkey-local-machine -> Software ->Policies ->Microsoft ->Windows NT -> Terminal Service ->Client

Add DWORD (32bit) fClientDisableUDP -> Change value from 0 to 1

Close and restart your PC.
Please sign in to rate this answer.

5 people found this answer helpful.
GSinnema 6 Reputation points

2022-10-14T10:33:58.42+00:00

That works here indeed!

Henk Verschoor 1 Reputation point

2022-10-21T08:17:49.023+00:00

thanks :D

kingbingring 1 Reputation point

2022-11-02T14:35:27.193+00:00

OMG from October 2022 after PC update i am facing this issue, and I was about to buy another lap since my RDP not working, BUT not my issue resolved TY

James McDonald 1 Reputation point

2022-11-16T00:40:59.423+00:00

This worked... but I didn't need to reboot as the mstsc client picks up the settings when you close and re-start it.

The other option, mentioned below, of setting HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\RDGClientTransport to 1 threw an "Your conputer can't connect to the remote computer because a security package occurred in the transport layer. Retry the connection or contact your network administrator for assistance" error. So I set it back to 0 and use this fix and we are all good.

OGLEA 1 Reputation point

2022-12-15T12:14:18.707+00:00

Thanks.

Worked. Saved my day.

Kevin Banta 21 Reputation points

2022-12-15T15:06:30.387+00:00

Hi everyone, personally I have lot of performance issue by disabling UDP...
Someone have a solution for this ? Or Fix to enable UDP again on Windows 11 22H2 ?
Regards,
Sign in to comment
Daniel Ström 6 Reputation points

2022-10-16T17:22:47.207+00:00

Solved on the server side

There was a bunch of updates on our Server 2012 (Updates from aug/sept broke RDP for Windows 11):
2022-10 Security and Quality Rollup for .NET Framework 3.5, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows Server 2012 R2 for x64 (KB5018549)
Windows Malicious Software Removal Tool x64 - v5.106 (KB890830)
2022-10 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5018474)

After installing them Windows 11 clients could connect without "Estimating connection Quality"

Best
Regards Daniel
Please sign in to rate this answer.

1 person found this answer helpful.
Kevin McWhirter 21 Reputation points

2022-10-17T07:55:27.777+00:00

This worked for me:
Make Changes to the Registry

You can fix the Windows 10 Remote Desktop not working error by making changes to the Registry Editor. Here is the way to make changes:

Step 1: Press the Win key and the R key at the same time to open the Run box.

Step 2: Type regedit in the box and then click OK. Click Yes to open Registry Editor.

Step 3: Navigate to HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client.

Step 4: Right-click the empty space on the right side and then choose New > DWORD (32-bit) Value. Name it RDGClientTransport.

Step 5: Double-click this new key to open its Properties. Set Value data to 1 and click OK to save changes.

Step 6: Try to connect the remote computer one more time and check if the error still exists.

Jason Frary (@Monitor) 6 Reputation points

2022-10-17T09:49:21.203+00:00

Kevin, this worked perfectly and sorted out the issue for us. Thank you for taking the time to document the fix.

M Littlefield 0 Reputation points

2023-02-04T19:56:29.7733333+00:00

Thank you! I couldn't log in at all today, I tried everything that would come to mind then I decided to Google it and saw these answers. I tried this one since I know updates are usually important. I thought I didn't have an update since the laptop usually tells me...but I did, I had 2 updates.. ran both updates...restarted.. and the remote desktop worked right away.
Sign in to comment

Share via

Windows 11 - Remote Desktop stuck on "Estimating connection Quality"

2 answers