Share via

RD Client launch bug: empty Workspaces screen

정은 김 0 Reputation points
2026-03-28T06:34:24.1633333+00:00

Whenever I try to start a remote connection from scratch, it freezes on the empty ‘No Workspaces’ page. Interestingly, if the program is already running beforehand, the connection works perfectly. I’ve tested this thoroughly multiple times, and the issue only began after the recent patch—it never happened in previous versions. Does anyone know how to downgrade to an earlier release for the time being?

Windows for business | Windows 365 Enterprise
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Scott Nguyen 1,000 Reputation points Independent Advisor
    2026-03-28T07:43:31.1066667+00:00

    Hello.

    Thank you for giving your question.

    To provide the most precise guidance, could you please specify which Windows Update (KB number) or Remote Desktop app version was installed just prior to this issue occurring? You can find this in Settings > Windows Update > Update history.

    In the meantime, please find the recommended resolutions below:

    1. Cache Clearance

    Before proceeding with a downgrade, it is highly recommended to clear the client's local metadata, as "No Workspaces" freezes are frequently caused by corrupted cached discovery files.

    Clear App Cache:

    Navigate to: %LOCALAPPDATA%\Packages\Microsoft.RemoteDesktop_8wekyb3d8bbwe\LocalState (for the Store version) or %LOCALAPPDATA%\rdclientwp (for the MSI version).

    Delete the contents of these folders. Note: You will need to re-subscribe to your workspaces afterward.

    Toggle UDP: Recent patches have occasionally broken the RDP-over-UDP transport.

    Open Group Policy Editor (gpedit.msc).

    Go to: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client.

    Set "Turn Off UDP On Client" to Enabled.

    1. Downgrading the Software

    Depending on which version of the client you are using, the rollback method differs significantly.

    Option A: Remote Desktop Client (MSI / MSRDC)

    If you are using the standalone installer (typically for Azure Virtual Desktop or enterprise environments), you can manually install a previous release.

    Uninstall the current version via Control Panel > Programs and Features.

    Download a verified previous version (e.g., version 1.2.5623 or earlier) from the official Microsoft documentation:

    Option B: Roll Back a Windows Update

    If the issue was triggered by a Windows OS patch (Patch Tuesday March 2026), you can remove it:

    Go to Settings > Windows Update > Update history > Uninstall updates.

    Locate the most recent Security Update or Cumulative Update and click Uninstall.

    After restarting, "Pause updates" for 7 days to prevent the immediate re-installation of the faulty patch.

    If you prefer not to downgrade, many users find that launching the client with the /v: parameter via a shortcut or CMD directly to a specific host bypasses the "Workspaces" discovery hang entirely: mstsc.exe /v:your.server.address

    If you find my answer useful, please mark it as the "Accepted Answer" so other members can find the solution easily. Your help in supporting the community is much appreciated!

    Best regards,
    Scott Nguyen

    0 comments
  2. Q&A Assist
    2026-03-28T06:34:34.91+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The provided information does not include any supported method to downgrade the Windows App / Remote Desktop client or a documented workaround specific to the “No Workspaces” freeze after a recent patch.

    The only directly related guidance in the context for Remote Desktop issues after updates is to install newer cumulative updates that contain fixes, or to use Known Issue Rollback (KIR) Group Policy where provided. For example, for recent Windows 11 24H2 Remote Desktop freezes and disconnects, the documented remediation is to install the later updates that address the issue, or apply the KIR Group Policy if still on an affected build, not to downgrade:

    • Remote Desktop freezes after a January 2025 preview update are addressed in later updates such as KB5052093, KB5053656, and KB5055523.
    • For enterprise-managed devices, IT admins can deploy a Known Issue Rollback via Group Policy as described in the KB5050094 article.

    Because no downgrade procedure for the Remote Desktop client or Windows App is documented in the supplied material, only the following supported actions are covered by the context:

    1. Ensure the device is fully updated to the latest cumulative update that contains Remote Desktop fixes (for example, KB5052093, KB5053656, or KB5055523 for Windows 11, version 24H2 scenarios).
    2. If using an affected preview or earlier update, and if the environment is enterprise-managed, have an IT admin deploy the appropriate Known Issue Rollback Group Policy described in the KB5050094 article to mitigate Remote Desktop freezes and disconnects.

    No additional, supported downgrade path is described in the context.

    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.