Windows 11 22H2 - Cant connect to a RDS server after update

Mmmax 171

Hi,

I have several clients on Windows 11 , and after the update 22H2, they were not able to log to our RDS servers

I tried to log to the server using the private IP, it worked
It is still not working when I try to log to the public IP

I tried without the firewall, nothing changed

The problem disappeared after the rollback, they have been able to log back in.

I cant find anything about this issue.

This issue happens during the connexion to both Windows Server 2012 R2 and Windows Server 2016.

Is there a fix yet ?

Thanks

Paul Okimura 11 Reputation points

2022-09-21T20:18:28.843+00:00

We are running Windows Server 2019 RDS in our environment, and experiencing the same issue as a result of the latest Windows 11 update.
Brandon Chapman 181 Reputation points

2022-09-22T17:39:37.073+00:00

This is definitely an issue with Windows 11 22H2--specifically the mstsc.exe and mstscax.dll files that come with it.

If you are connecting to an RDS farm that has a broker and a gateway, regardless of whether it's running Windows Server 2022, 2019, or 2016, the RDP client will get stuck at "Loading virtual machine" or sometimes "Configuring remote connection". You'll have to use Task Manager to end mstsc.exe because you won't be able to close the program by clicking the X.

Connecting directly to another computer/server with mstsc.exe (no broker or gateway) works fine.

The only workaround for now is to copy c:\windows\system32\mstsc.exe and mstscax.dll from a Windows 11 21H2 machine to the same location on your 22H2 machine. You may have to take ownership of the 22H2 versions of the files in order to be able to overwrite those files.

EDIT: JeffCleath-8569's fix is even better!!! Make the following registry change and restart your computer:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client
New DWORD value: fClientDisableUDP SET TO 1
Salina Tooraji 6 Reputation points

2022-11-03T15:09:22.613+00:00

Perfect, added the value worked for me.
Борис Садовский 6 Reputation points

2022-11-07T04:37:04.27+00:00

Another one solution is change path and working directory of mstsc.exe from "%windir%\systems32\mstsc.exe" to backup path"C:\Windows.old\Windows\System32\mstsc.exe" in exe link.
Manny 6 Reputation points

2022-11-07T05:33:43.257+00:00

Love this solution, use different MSTSC and .dll I believe temporarily. How did you do it?
Борис Садовский 6 Reputation points

2022-11-07T06:42:25.067+00:00
While trying to use this solution above
"The only workaround for now is to copy c:\windows\system32\mstsc.exe and mstscax.dll from a Windows 11 21H2 machine to the same location on your 22H2 machine."

I got an 5 "Access denied" error.
So next step was not copy, but change exe path to backup copy of Windows 11 21H2 in a link.
Michael Benadiba 0 Reputation points

2023-01-17T21:39:12.3933333+00:00

The solution was to sign into the console of the target computer

Run Notepad.exe "Run-As" and enter in the credentials of the account you are trying to use to RDP in.

from the Run Command: runas /user:"Username" notepad.exe

This will initialize something and allow you to login from a remote computer.

In my case, the issue i believe was also related to signing into a microsoft account instead of a local account.
Musa Ata 0 Reputation points

2023-02-20T11:19:38.5033333+00:00

Can someone update if this issue is solved including a link to the item solved please.

Accepted answer

Jeff Cleath 181 Reputation points

2022-09-22T17:01:58.61+00:00

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.
Please sign in to rate this answer.

16 people found this answer helpful.
Brandon Chapman 181 Reputation points

2022-09-22T17:46:24.647+00:00

OMG, that works!

That's a MUCH better fix than replacing the mstsc.exe and mstscax.dll files from a 21H2 computer!!!

Thank you!!!!

Minder Andreas (ID) 6 Reputation points

2022-09-23T06:01:24.253+00:00

Wow, this is it. Thank you so much!

Mmmax 171 Reputation points

2022-09-23T08:10:12.887+00:00

Thank you so much ! It worked perfectly !

Matthias Zeitler 6 Reputation points

2022-09-23T11:06:22.86+00:00

Super Jeff, thank you for your information and analysis!

Best Regards, Matthias

Ed Hammond 6 Reputation points

2022-09-26T18:29:58.823+00:00

I pushed this out to all my Window 11 PCs using Group Policy. Crisis averted!
Just make sure to only hit your windows 11 PCs by using a WMI Filter in Group Policy:
SELECT * FROM Win32_OperatingSystem WHERE Name LIKE "%Windows 11%"

Manny 6 Reputation points

2022-09-29T06:06:22.05+00:00

Thank you, you are a life saver. :)

Peter Cooke 1 Reputation point

2022-09-29T10:58:37+00:00

Didn't work for me. I changed the registry on the client first and then my workstation. I rebooted after each time change and I still received "Your credentials did not work error".

I'm running Windows 11 on both machines.

I assume you only need to make this change on the client and not the machine you are trying to remote into.

Any ideas?

Thanks,

pete

Jeff Cleath 181 Reputation points

2022-09-29T14:54:15.187+00:00

If you are getting an error regarding credentials then you are having a different issue. You would just get an endless message of trying to connect with the issue described.

If you are getting a credentials error then either you have the incorrect username/password, your account does not have permission to connect remotely, or some other user/permission error most likely.

Brandon Chapman 181 Reputation points

2022-09-29T23:08:54.257+00:00

You can do this to Windows 10 machines as well--it's just that it's not necessary since its mstsc.exe version doesn't have the UDP bug.

George Koukouvetsios 1 Reputation point

2022-09-30T10:55:55.623+00:00

Can someone say what to do I am very bad at computers and I deal with the problem I can’t connect to Microsoft servers pliz help

Altenburger, Mark 1 Reputation point

2022-09-30T15:00:50.467+00:00

Thanks!

Waliu Mustapha 1 Reputation point

2022-09-30T23:08:17.463+00:00

Thanks for this fix @Jeff Cleath !! I will be speaking with my Infrastructure guys on Monday to push this out via Group Policy as I have begun to set up new machines with Windows 11 22H2. I just happen to be testing it my own machine and was wondering why it suddenly wouldn't work. Totally fine adding the RDS link via Control Panel, but just wouldn't open any apps I select.

Thanks again Jeff!

Waliu Mustapha 1 Reputation point

2022-09-30T23:09:42.69+00:00

Here's hoping Microsoft make changes soon with a patch of some sort!

Oren Lahav 6 Reputation points

2022-10-02T06:21:55.097+00:00

Thanks Jeff,
I have enable the UDP 3389 in my hosting farm FW and and its solved as well.
Is there any disadvantage for enabling work with RDP UDP over WAN?

Vojta Fluger 1 Reputation point

2022-10-02T13:15:52.757+00:00

I cannot find the fClientDisableUDP option in the registry. Im in the right directory and all. But its just not there. Should I create one?

Oren Lahav 6 Reputation points

2022-10-02T13:19:10.897+00:00

Yes,
Create the new DWORD (32-bit) fClientDisableUDP

Vojta Fluger 1 Reputation point

2022-10-02T13:50:32.863+00:00

So, I did that, but it created like new folder - I named it fClient... and then changed the default value to 1. But it didn't work. Should I make DWORD file instead of the key?

Oren Lahav 6 Reputation points

2022-10-02T14:00:25.847+00:00

New DWORD (32-bit) Value

ITPro-714 1 Reputation point

2022-10-03T23:26:35.88+00:00

Anyone getting this error?

Not sure if both of these are related. The server is accessible on Windows 10 and below. Windows 11 21H2 is still able to connect. Windows 11 with 22h2 getting this error. Only option is to uninstall the 22H2 update. Tried doing both recommendation above, but it did not work. Added registry fClientDisableUDP SET TO 1 and tried copying the mstsc.exe and mstscax.dll. No success.

George Khairallah 121 Reputation points

2022-10-03T23:39:10.937+00:00

This feels like an isolated case. Is this happening on multiple workstations? All within the same domain? What about a workstation that’s not joined to the domain?

Can you check whether the wksprt.exe process exists, if it does kill it.

Try clearing any entries related to your rdgateway in your credential manager on the workstation?

ITPro-714 1 Reputation point

2022-10-04T01:02:04.547+00:00

-Thanks George for the support -
Yes, this is happening to multiple workstations that are on Windows 11 version 22H2. All workstation are on workgroup. wksprt.exe process does not exist on any of the workstations. Also, cleared any saved entry in rds and credential manager. Tried connecting by manually typing in the gateway, server, username and password with same result. Password and credentials are correct. I did test the same configuration using the microsoft remote desktop app from the microsoft store. The remote desktop app does work. Just having issue with mstsc. It seems weird that by uninstalling Windows 11 22H2 update I was able to start using mstsc for rdp again.

We have other workstation on Windows 10 and Windows 11 21H2 version. They are able to connect just fine. It's weird that the errors are different. But the only similarity for the fix was to uninstalling Win11 22H2 update this allowed the affected workstation to connect.

Just wanted to see if anyone else is having this same error.

George Khairallah 121 Reputation points

2022-10-04T01:45:34.763+00:00

Curious about a few items, not sure if missed it in some of your replies:

are you connecting to a RDS Desktop deployment or a RemoteApp (Published App) deployment?

if RemoteApp, is your collection setup via the control panel or via web browser? Is the result the same on both?

can you try to connect via the HTML5 web client and see if you are able to connect?

As far as I know, the workarounds presented here are related to the initial connection and not the authentication.

Microsoft RDS development team reached out to me directly to work on this issue and if this credential problem is another unintended side effect of 22H2, I can probably add it to the list.

They are unable to reproduce the problem on their end, but the issue exists in over 26 RDS deployments we gave on 2012R2, 2016 and 2019.

ITPro-714 1 Reputation point

2022-10-18T22:55:38.5+00:00

Hey George, sorry for the late response. We are not using RemoteApp. What I meant was the Microsoft Remote Desktop application from the Microsoft Store. I was able to test the connection and remote into the server using this as a temporary solution.

Rene Scott Simonsen 1 Reputation point

2022-11-17T06:45:52.12+00:00

Thank you for this fix. I also reported this issue to Microsoft 7 months ago when it was still beta. I guess multiple reports of an issue isn't a showstopper to prevent worldwide rollout :)
Link to my report in feedback hub: https://aka.ms/AAiq8vr

AdminGISIT 1 Reputation point

2022-11-30T21:41:03.28+00:00

I installed the update shown below this morning hoping MS would have fixed this issue, but no joy:

"2022-11 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5020044)"

Here's what I'm now running after today's update:

After my computer rebooted, I again had to modify my registry as outlined above int JeffCleath-8569's post and my AWS RDS in now functioning again.

My clients connect to their Diamond (tax software) via RDS which is hosted in AWS via Central Square here in Canada.

Hopefully Windows and AWS are able to address this issue soon.................

George Khairallah 121 Reputation points

2022-11-30T21:53:14.637+00:00

The fix that will address his is issue will be KB900417

If you are interested, you may see our advisory, which we are keeping up to date on this matter. We worked directly with the Microsoft RDS development team on this. We have an internal patch for this KB and have verified that the hotfix will resolve the issue. It will be released in the 4th week of January 2023
https://support.gotomyerp.com/portal/en/community/topic/active-windows-11-22h2-update-breaks-gotomyerp-connection-23-9-2022

Stuart Elliott 141 Reputation points

2023-02-20T10:54:27.7266667+00:00

I've just started experiencing this today for some obscure reason, some 5 months later, the registry addition solution still applies.

Get your sh*t together MickeySoft.

EDIT: I'm guessing it's related to KB5022845 which just got installed, that apparently contains a fix KB5022360 that was mean to remedy this issue.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

23 additional answers

Manny 6 Reputation points

2022-10-15T23:37:41.527+00:00

Hi Rodrido,

RDP looks deceptively simple but there is alot to it. Have been working with RDP protocol for over 10 years and always learning new things.

UDP isnt required too make it work BUT provides numerous benefits. UDP is a packet oriented protocol so if the user has poor Internet connection or using wireless or congested WiFi it will help.

The other issue is that as PC start using HD, 2k and 4k (displays) the bandwith needs can be huge and when you compound latency on top of that then it becomes unusable. UDP also supports some sort of compression that greatly reduces bandwidth so if you have many users on bandwidth limited connections then its also a good idea. (Dont forget to set Qos on router as email, cloud docs and syncing can chew ALL of your bandwidth rendering your rdp connections useless).

Hope that helps
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Johnny Wong 5 Reputation points

2023-04-05T15:59:20.4733333+00:00

Today is April 5th 2023 and it is not working. It WAS working back in February. OS build 22621.1413 had to go back to the Registry Edit method. Can you guys (MS) stop messnig up mtsc
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
George Khairallah 121 Reputation points

2022-09-27T19:45:02.457+00:00

So, we opened a ticket with Microsoft about this, and turns out, their solution was a link referring me back to this thread, on which I commented. ¯_(ツ)_/¯. A bit odd that they're not acknowledging that this is an issue with this patch.

My understanding is that changing that registry to 1 would actually not use the UDP. Would anyone know whether this would cause any "unreliability" in the RemoteApp connection if it is left turned off?
Please sign in to rate this answer.
Brandon Chapman 181 Reputation points

2022-09-28T16:54:40.517+00:00

UDP support was added to...I think a Windows 7 version of mstsc.exe (version 9200 or 9600). From my limited understanding, I think UDP allows the RDP connection to remain connected even if it doesn't get an acknowledgement from the remote server, as TCP requires a full handshake between client and server before it does anything.

So disabling UDP just means that it only uses TCP to connect, and that it needs a stable connection to to the server at all times to maintain the handshake.

George Khairallah 121 Reputation points

2022-09-28T16:58:17.217+00:00

Thanks for that Brandon,
That is also my understanding of the UDP protocol for the RDP connection. So I think I'm on the right track in not wanting to disable it.
We're a hosting provider; We don't have control over our customer's connections, so we want to have every connection stabilizing technology available to be active.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Jeff Cleath 181 Reputation points

2022-09-27T20:55:44.453+00:00

I have heard from others that changing this registry could lead to performance issues with file downloads and video from Remote Desktop environment, especially with poor or long distance connections. I personally have been using this setting for about 4 months and have had no issues. I have very good internet connectivity remotely and am only about 40 miles from the server environment.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Windows 11 22H2 - Cant connect to a RDS server after update

23 additional answers

Your answer