I have attached the list of rules we implemented as part of the benchmarking.Īny help will earn my forever love and gratitude!!! Since AVD is so new, and even a quick name change has got me struggling with scouring the internet for anyone else experiencing this issue. So it is limited to the Windows version of the Remote desktop client.Īny ideas would be greatly appreciated, other wise we are stuck with removing these rules one by one to try find the culprit which could take weeks. Any ideas what I might be missing.Īnother interesting point is that remote apps launch fine on the Web version of AVD, and on IOS the apps launch no worries. Screenshot is of all the services that we disabled as part of the GPO but it may not be that, as CIS reccomendations were quite large and contained a lot of settings. So some security setting we have implemented has caused this isssue. Specifically it was GPO that was created based on the CIS Benchmarking Tool. We have confirmed that this issue has occured due to GPO. Its as if its never able to present the application. The User can even send a CTRL Alt Delete function which they can use to Lock the Computer, then they can unlock it, but it takes them straight back to the same stuck preparing windows screen. The screen freezes for the user at preparing Windows, but as far as we can tell, the users connection is successful, the remote app launches on the VM itself, but from the Remote Desktop Client, the user is stuck on the blue logon screen. We have an issue where Remote Apps will launch, but then get stuck at Preparing windows. Something in there has broken our environment in a strange way. Until we were required to pass the CIS Benchmark for Security. Just wanted to see if anyone else is having this same error.We are deploying a POC / Build out of AVD in my companies environment. But the only similarity for the fix was to uninstalling Win11 22H2 update this allowed the affected workstation to connect. 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. For the last part, is this the Remote Desktop app that is preinstalled (see image below) If yes, we must have Windows 11 Pro or Windows 10 Pro devices to enable and use Remote Desktop. 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. See: Send feedback to Microsoft with the Feedback Hub app for details. 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 |