![]() It's weird that the errors are different. We have other workstation on Windows 10 and Windows 11 21H2 version. It seems weird that by uninstalling Windows 11 22H2 update I was able to start using mstsc for rdp again. I did test the same configuration using the microsoft remote desktop app from the microsoft store. Tried connecting by manually typing in the gateway, server, username and password with same result. Also, cleared any saved entry in rds and credential manager. wksprt.exe process does not exist on any of the workstations. Yes, this is happening to multiple workstations that are on Windows 11 version 22H2. New DWORD value: fClientDisableUDP SET TO 1 HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client You may have to take ownership of the 22H2 versions of the files in order to be able to overwrite those files.ĮDIT: JeffCleath-8569's fix is even better!!! Make the following registry change and restart your computer: ![]() 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'll have to use Task Manager to end mstsc.exe because you won't be able to close the program by clicking the X.Ĭonnecting directly to another computer/server with mstsc.exe (no broker or gateway) works fine. 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". This is definitely an issue with Windows 11 22H2-specifically the mstsc.exe and mstscax.dll files that come with it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |