Classic RD Web Access XSLT deprecation — permanent fix and release timeline for Windows Server 2022?

Joel Taylor 0 Reputation points
2026-10-20T12:47:14.05+00:00

We operate customer-facing classic RD Web Access portals (/RDWeb/Pages) on Windows Server 2022. Customers sign in to access published applications and desktops, download .rdp files, and launch sessions using the native Windows Remote Desktop client (MSTSC).

Customers are seeing browser warnings about XSLT removal. We have reviewed Microsoft’s KB5130994, “RD Web Access fails to load when XSLT is disabled in Microsoft Edge or Google Chrome,” which states that Microsoft is working on a fix:

https://support.microsoft.com/en-us/servicing/os/windows/docs/2026/10/kb5130994-rd-web-access-fails-to-load

We understand the documented workarounds. However, we do not manage our customers’ devices or browsers, so we cannot reliably require browser policy changes, extensions, or IE mode. We are also evaluating the HTML5 web client with .rdp downloads.

Could Microsoft clarify:

Is a supported update planned for classic RD Web Access on Windows Server 2022 that removes its dependency on native browser XSLT?

Is there an estimated release date, target cumulative update, or preview available for testing?

  1. Where should we monitor announcements and availability of the fix?

Our goal is a centrally deployed solution that preserves .rdp downloads and native Remote Desktop sessions without requiring customers to change their browser configuration.

Thank you for any guidance that will help us plan before browser XSLT support is removed.

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Daphne Huynh (WICLOUD CORPORATION) 2,540 Reputation points Microsoft External Staff Moderator
    2026-10-21T02:50:39.9866667+00:00

    Welcome to Microsoft Q&A!

    Thank you for pointing out the discrepancy. Your concern is valid because the current documentation is not fully consistent on this point.

    The “Applies to” section of the Remote Desktop web client administration article includes Windows Server 2022. However, the same article's documented prerequisites still state that RD Gateway, RD Connection Broker, and RD Web Access should be running on Windows Server 2016 or Windows Server 2019.

    At the same time, KB5130994 applies to Windows Server 2022 and recommends the HTML5 Remote Desktop web client as a workaround for the classic RD Web Access XSLT dependency. This creates understandable uncertainty when planning a Windows Server 2022 deployment.

    Based on the currently published documentation, I can confirm the following:

    • The Remote Desktop web client supports a workflow in which users can launch remote resources in the browser or download an .rdp file to be handled by a locally installed RDP client. Administrators can also configure the deployment to restrict users to the .rdp download method.
    • The web-client deployment should use per-user RDS CALs rather than per-device CALs. Please notes that per-device CALs aren't supported by the web client.
    • Publicly trusted certificates should be configured for the RD Gateway and RD Web Access roles.
    • The RD Connection Broker certificate must be imported into the web-client configuration. Please also states that this step needs to be repeated whenever the RD Broker certificate is renewed or replaced.
    • Microsoft Entra Application Proxy is supported, while Web Application Proxy isn't supported by the web client.

    However, the available public documentation does not explicitly confirm that a deployment in which RD Web Access, RD Gateway, and RD Connection Broker all run on Windows Server 2022 meets the documented prerequisite. The administration article still specifically identifies Windows Server 2016 or Windows Server 2019 for those roles, even though its “Applies to” section includes Windows Server 2022.

    For that reason, I would be cautious about interpreting the “Applies to: Windows Server 2022” heading alone as confirmation that the Windows Server 2016/2019 prerequisite is outdated.

    You can still pilot the solution in a non-production environment and validate the following:

    1. Publish the latest web-client package as a test deployment. A test publishing option that makes the client available through the /RDWeb/webclient-test/ URL.
    2. Confirm that users can sign in and access the remote resources published to them.
    3. Validate the .rdp download workflow and confirm that the downloaded resource can be handled by the intended locally installed RDP client.
    4. Validate authentication, certificates, RDS licensing, and RD Gateway connectivity for your environment.
    5. Confirm that the workflow behaves as expected with your published desktops and RemoteApps.
    6. Re-test the workflow using the customer-managed browsers and devices that are representative of your production environment.

    I understand that what you are ultimately looking for is a definitive Microsoft confirmation rather than simply an interpretation of the currently published documentation. This is especially important when you are making a production decision that may affect your customers. Unfortunately, this is also where there is a limitation to what I can responsibly confirm through Microsoft Q&A.

    Microsoft Q&A is primarily a public community support forum. I can help interpret Microsoft's published documentation, provide documented configuration, troubleshooting guidance, and identify inconsistencies such as the one you have found. However, when the published documentation itself is ambiguous, a forum response cannot establish or change Microsoft's official product support boundaries.

    In this case, the available documentation does not explicitly say that the Windows Server 2016/2019 prerequisite is outdated, nor does it clearly confirm that the exact RDS topology you described, with these roles running on Windows Server 2022, is formally supported. Therefore, I don't want to give you a definitive “yes, this configuration is supported” based on an assumption.

    I realize that this may not be the definitive confirmation you were hoping for, particularly when you are trying to plan a production deployment. However, I would rather be transparent about what can and cannot currently be confirmed from the published documentation than present an interpretation as an official Microsoft support statement that could later prove inaccurate for your environment.

    If you require formal confirmation of the supportability of your exact Windows Server 2022 topology before deploying it to customers, I recommend opening a Microsoft Support request and providing the complete RDS topology, role placement, Windows Server versions, and relevant deployment details. This would be the more appropriate channel for an environment-specific supportability question that cannot currently be resolved from the publicly available documentation.

    In the meantime, piloting the HTML5 Remote Desktop web client in a non-production environment can still be useful for validating the technical workflow, including resource access, authentication, certificates, RD Gateway connectivity, and the .rdp download/native-client launch behavior. However, successful testing should be treated as technical validation of your particular environment rather than, by itself, confirmation of Microsoft's formal support position.

    I hope this helps clarify both what is currently documented and why I cannot responsibly provide a definitive confirmation regarding the Windows Server 2022 prerequisite based on the information currently available.

    References:

    Set up Remote Desktop web client for users | Microsoft Learn

    RD Web Access fails to load when XSLT is disabled in Microsoft Edge or Google Chrome | Microsoft Support

    Get started with the web client for Remote Desktop Services | Microsoft Learn

    If you find it useful, please click Accept Answer.

    Thank you for choosing Microsoft Q&A.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-10-20T12:48:16.2366667+00:00

    Microsoft has committed to fixing classic RD Web Access, including on Windows Server 2022, but has not published a release date, target cumulative update, or preview package.

    Current status

    • KB5130994 applies to Windows Server 2016, 2019, 2022, and 2025.
    • Microsoft confirms that classic RD Web Access performs client-side XSLT processing and states that it is working on a fix.
    • The advisory does not identify the implementation of that fix, a target Windows Server cumulative update, a preview, or an estimated delivery date.^1^

    KB5130994 is a support advisory, not an update package. Therefore, its publication does not mean the permanent fix has already shipped.

    Browser deadline

    Microsoft Edge’s published schedule is:

    • Edge 157: XSLT disabled by default in Canary, Dev, and Beta.
    • Edge 159: XSLT disabled by default in Stable.
    • The temporary XSLTEnabled policy is planned for removal in Edge 176, Summer 2027.^2^

    Consequently, browser policy is only a transition measure, not a permanent solution for an unmanaged customer population.

    Centrally deployable option available now

    For the requirement to retain downloaded .rdp files and launch them with the native Remote Desktop client, Microsoft’s documented interim server-side option is the Remote Desktop HTML5 web client:

    1. Publish the HTML5 client under: https://<RDWeb-FQDN>/RDWeb/webclient/index.html
    2. Users sign in and open Settings.
    3. Select Download the rdp file, then OK.
    4. The .rdp file is downloaded and can be opened with MSTSC.

    This avoids the classic portal’s XSLT-rendering dependency while preserving native-client launch through downloaded files.^1^

    There is an important documentation discrepancy to validate before making this the production replacement: the current web-client installation article lists RD Gateway, Connection Broker, and RD Web Access on Windows Server 2016 or 2019 as prerequisites, although KB5130994 applies to Server 2022 and explicitly directs affected environments to this client.^3^ For a Server 2022-only deployment, test it in a non-production RDS farm and obtain confirmation through Microsoft Support before treating it as the long-term supported architecture.

    Where applicable, the basic publication commands are:

    Install-Module -Name RDWebClientManagement
Install-RDWebClientPackage
Import-RDWebClientBrokerCert "C:\Certificates\RDBroker.cer"

# Validate first at /RDWeb/webclient-test/
Publish-RDWebClientPackage -Type Test -Latest

# Publish after validation
Publish-RDWebClientPackage -Type Production -Latest

    Where to monitor

    Monitor these official locations:

    1. KB5130994 — the advisory says that more information will be added when available; this is the most specific status page for the XSLT issue.^1^
    2. Windows Server 2022 update history — lists each released update and its documented fixes and known issues.^4^
    3. Windows Server 2022 release health — provides current servicing notifications and known-issue status.^5^
    4. Edge Beta release notes — tracks changes to the XSLT rollout and temporary policy retirement schedule.^2^

    Until KB5130994 names a servicing release or update package, there is no publicly committed Windows Server 2022 CU or preview to deploy for the classic /RDWeb/Pages portal.

    References

    1. RD Web Access fails to load when XSLT is disabled in Microsoft Edge or Google Chrome
    2. Release notes for Microsoft Edge Beta Channel
    3. Set up the Remote Desktop web client for your users
    4. Windows Server 2022 update history | Microsoft Support
    5. Windows Server 2022
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.