Updating to Windows 11 22H2 Breaks RemoteApp

Updating to Windows 11 22H2 Breaks RemoteApp


As per gotomyerp's standard procedures, we always try to stay ahead of the curve on what is coming. 
As per our recent testing of the new Microsoft Windows major feature release 22H2, we discovered that this breaks the functionality of RemoteApp connections.

The symptom could be that the connection would get stuck on "Loading the virtual machine"

Latest Update: 02/14/2023

A patch from Microsoft has now been released. The KB reference has changed since the internal release, and it is now included in the following KB: KB5022360 (Which is an optional preview)

As of 02/14/2023, KB5022845 has been released, which will install as part of the regular Windows updates. Users who are facing an issue, should make sure to apply all available Windows Updates are installed, which should include KB5022845, and the issue will be resolved.

For additional updates and details on this issue, please see the advisory


Since gotomyerp uses Microsoft's technologies, we are affected by changes that they release to us, as a software publisher. Unfortunately, sometimes Microsoft releases updates that have not been sufficiently tested and causes functionality to break. Back in 2018, there was a very similar incident where, again, gotomyerp was ahead of the curve and has written workarounds for an issue that stemmed from Microsoft releasing a bad update.
This time around, it is a similar scenario, and the noise has already started from the community regarding this issue. You can see here and here and here


If you are on this article, you are looking for this solution

Permanent Solution

Ensure that you install all your pending Windows updates. 
The specific Windows update which resolves the issue is KB5022845 (which includes improvements which were previously in the Preview update KB5022360)

Make sure to look for the following update:
2023-02 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5022845)

Once installed: Reboot your computer, and you will get a successful login.

If you had previously disabled UDP, we highly recommend that you now re-enable it after installing the update to maximize your connection reliability and performance. 
To do this:
  1. Download the UDPforRDP Fix
  2. Right-click and select "Run As Administrator"
  3. Click Enable UDP

Workaround 1 (Obsolete): Revert Back to 21H2

You may be able to revert back to your previous update. To do so, you may need the assistance of your IT. This option may not always be possible.
As a courtesy, we are including a YouTube Video that walks you through these steps

Newly purchased devices with Windows 11 will come pre-installed with the 22H2 Feature Pack, with no option to uninstall or revert. If that is the case, we recommend installing the utility below
gotomyerp cannot assist with Operating System restoration or workstation level troubleshooting. This should be handled by your internal IT personnel.

Workaround 2 (Obsolete): Apply Temporary Registry Key

This registry change adds one key that disables UDP, which is the cause of this issue. 
This workaround is non-intrusive, and easily reversible once the permanent HotFix is released.

Use our Utility (for most users)

      Who should use this?
  1. If you are a small company without an IT department
  2. If you are not a technical person

The utility is simple to run, and must be "Run As Administrator". It allows for both enabling and reversing the workaround when the permanent HotFix is released.

Request Access to the UDPforRDP Fix
MD5 Hash: 98AD9016D4ECD3777A3A589C1A0831F5

A log file of what was done can be found in %TEMP%\UDPforRDPToggle.log

Make the Change Manually (for IT Pros)

      Who should use this?
  1. You are an IT professional
  2. If you prefer to do this manually
  3. If you are comfortable around the registry
  4. If you are using the information to create a Group Policy Preference throughout your domain to apply to all your users at the same time.

To make this change manually, add the following key:
HKLM:SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client\fClientDisableUDP
Value: 1

This change can also be completed on a domain by using a Group Policy Preference, and can be done by your IT team, to target all your user's workstations at once.

Once the policy is create, set the scope to the workstation or Security groups containing the workstations in question.
This setting can be reversed by changing the value data from 1 to 0, or just deleting the "fClientDisableUDP" key.

While we have extensively tested this fix internally, gotomyerp is providing this solution as a courtesy, and is not responsible for any issue resulting to the target workstations as a result. Please use it at your own risk, or refer to the first solution to revert your OS back to the previous version.