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 151 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 151 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 151 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 106 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

22 additional answers

George Khairallah 121 Reputation points

2022-09-23T14:54:49.147+00:00

We also found that disabling UDP On your RemoteApp collections resolves the problem without having to make any changes on the client side.

We're going the route of replacing the mstsc.exe and mstscax.dll instead of the registry change because we figured that these files will get replaced when MS releases the fix, but a registry change will not get revert unless the user does so, which would permanently disable UDP, probably affecting the stability of their connection.

We wrote a patch as a workaround for those who do not want to do any of the other workarounds
https://support.gotomyerp.com/portal/en/kb/articles/updating-to-windows-11-22h2-breaks-remoteapp

Cheers,
Please sign in to rate this answer.

3 people found this answer helpful.
John Thompson 11 Reputation points

2022-09-28T19:45:44.32+00:00

this works perfectly!!!! Thank you for this!

Michael Wills 1 Reputation point

2022-10-23T23:02:02.183+00:00

This one worked for me, too. Thank you!
Sign in to comment
George Khairallah 121 Reputation points

2022-09-29T17:14:02.137+00:00

A quick update on our ticket with Microsoft.
They have acknowledged this bug, and their team is working on it. no ETA on pushing a fix, but at least they are aware of it and is being worked on.

If/when we get any updates on the same, I will post it back here.
Please sign in to rate this answer.

3 people found this answer helpful.
Brandon Chapman 151 Reputation points

2022-09-29T23:09:53.737+00:00

I'm guessing it's either going to be part of the October or November cumulative update for Windows 11 22H2.

EDIT: Welp, it's not in the October update. Let's hope for November...

EDIT2: As George mentioned in another reply, it's looking like the 4th week of January 2023.

Michael 76 Reputation points

2022-10-04T19:46:00.483+00:00

I have a very simple desktop to desktop RDP connection over a VPN. Both computers are 22H2. Though my setup is much simpler than what is described above, I too experienced a black screen when trying to connect followed by a time-out. Occasionally I would get a PIN screen which would not recognize my PIN, then time-out. If I rebooted the remote Host machine, I could then log in and work but subsequent sessions would time out. I will admit I have a bad habit of closing an RDP session by closing with the Close "X" at the top of the screen. However, considering that my problems making the connection were somehow related to a current open session, I started Logging Out instead of X'ing out of the session. I haven't experienced a problem since. 48h, multiple connections. For what it's worth. I made no registry changes. I did not copy the 21H2 mstsc.exe and the .dll to the 22H2 install remote host. I just Log Out and subsequent sessions seem to open correctly.

William Sleeth 0 Reputation points

2023-06-19T18:34:43.6833333+00:00

How can i fix it if i can't get online
Sign in to comment
Yudara Gedara 11 Reputation points

2022-10-05T04:56:55.117+00:00

Hi Guys,

does anyone know, when will Microsoft release a fix for this issue?
Please sign in to rate this answer.

2 people found this answer helpful.
George Khairallah 121 Reputation points

2022-10-05T05:04:59.56+00:00

As of today, Microsoft still does not have a solution, as they are unable to reproduce it in their environment.

They are actively working on it though, we’ve provided them our environment for testing and repro.

Will post an update as soon as I find out anything new.

George Khairallah 121 Reputation points

2022-10-10T19:21:53.957+00:00

Hello everyone,
as promised, we received an update from the MS team today, and they finally found the root cause of the problem, and are working on a fix.
They will be sending us a private patch to test out. (no ETA at this time), but once we have more information, we'll let you know.

A solution is coming though!

AndresP 21 Reputation points

2022-10-13T07:30:29.237+00:00

Strange, this is NOT mentioned in https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-22h2 nor other W10/11 build Known issues lists. currently (13.10.2022)

George Khairallah 121 Reputation points

2022-10-13T13:22:31.097+00:00

True. I think it’s because they’re not considering it a widespread problem.

Microsoft was not able to reproduce this, so we had to give them access to our own environment.

I think the issue is only happening in a very particular configuration scenario.

I will ask them for some more details once they provide us the private patch to test out.

Jeff Cleath 46 Reputation points

2022-10-13T13:28:00.407+00:00

The issue is extremely easy to reproduce. Configure a firewall to only let ports 80 and 443 through to the RD Gateway server (and no access to any other servers or ports), and try to connect to the RD Gateway through the firewall with a Windows 11 computer with the update installed.

George Khairallah 121 Reputation points

2022-10-13T13:32:43.07+00:00

yup, I know. I have 26 deployments and 3000+ users connecting.

For some reason though, Microsoft was unable to reproduce the same in their environment.

My call was with the RDS Product manager, their lead developer and a few other developers, so I’m pretty sure they knew what they were talking about. :)

In any case, at least they have access to an environment that has the issue, and found the source, so I think we shall a have a solution in the near future.

Rodrigo C. Cortes Cano 6 Reputation points

2022-10-15T10:34:05.267+00:00

Hi!

what other ports would be required for it to work without modifications?

Thx.

George Khairallah 121 Reputation points

2022-10-15T15:15:19.597+00:00

In our case, disabling UDP listener on the RDGateway allows the connections through. With this workaround, you wouldn’t have to touch your workstations.

Manny 6 Reputation points

2022-10-15T18:25:01.59+00:00

I wouldn't advise that, as you will loose the benefits for the users that dont have that prob. (Reduced bandwidth and better performance in poor Internet connections)

Unless all users cant connect not a good idea.

George Khairallah 121 Reputation points

2022-10-15T18:27:04.26+00:00

I wasn’t advising it, hence why we’re working with MS on a proper solution. I was only responding to Rodrigo’s inquiry.

Rodrigo C. Cortes Cano 6 Reputation points

2022-10-15T20:48:24.137+00:00

HI!

i don't have idea but RDG need 3391 UDP open (searching i found this). If the solution is open in the RDG one port more is a better idea or not?

Thx

George Khairallah 121 Reputation points

2022-10-15T20:52:35.337+00:00

It does not require UDP/3391. That port is optional, and your connection will still work without it. However, It's not a good idea to disable it, as it contributes to the reliability of connections to your remote sessions.

I'm referring to the setting in the image attached.
Sign in to comment
Samah Kamal Eddine 11 Reputation points

2022-09-21T19:53:30.877+00:00

Is the RDS server updated as well? Make sure the latest Windows Server update is installed on the RDS server.
Please sign in to rate this answer.

1 person found this answer helpful.
Mmmax 171 Reputation points

2022-09-22T11:42:40.717+00:00

Yes, the RDS servers, both 2012 R2 and 2016 are up to date and I also restarted them.
I don't have any error message, just the loading is stuck on "Connecting to : servername --- Configuring Remote session..."

Luis Garcia 26 Reputation points

2022-09-22T13:39:55.94+00:00

Same problem with our 2012R2 RDS, the user had to Roll Back the update to sign in.

Samah Kamal Eddine 11 Reputation points

2022-09-22T13:45:59.857+00:00

Can you please check the error log? Check under system and application to see if there is anything being generated there that can be helpful?

Mmmax 171 Reputation points

2022-09-22T14:01:16.347+00:00

No any logs on Windows 11 neither on the RDS servers.
As said, it doesn't give any error, this is just stuck, loading for hours.

Minder Andreas (ID) 6 Reputation points

2022-09-22T14:12:58.183+00:00

Got the same issue here and there is an (on the client) Event 1041 RemoteApp and Desktop Connections: Remote application (xxx) is launched on RemoteApp and Desktop connection (xxx) but no stored credentials are used for single sign on. (Reason - RemoteApp and Desktop connection does not exist)
But the RDP farm does work in older Windows Versions. Any tips appreciated.

Brandon Chapman 151 Reputation points

2022-09-22T17:49:56.057+00:00

RDS server update doesn't fix the issue. Our RDS servers (brokers, gateways, session hosts) are on the September 2022 cumulative update level.
Sign in to comment