Windows Server 2022 RD Web Access – XSLT Deprecation in Google Chrome

Florian Schleifer 0 Reputation points
2026-11-03T12:38:21.0166667+00:00

Hello

We are operating a production Remote Desktop Services environment based on Windows Server 2022 with RD Web Access and RD Gateway.

Our environment provides three access methods, all of which are required by our employees and external customers:

  1. Classic RD Web Access (/RDWeb) for authentication, RemoteApp listing and RDP file downloads.
  2. RemoteApp and Desktop Connections via Windows Control Panel (RemoteApp feed).
  3. HTML5 Remote Desktop Web Client (/RDWeb/webclient).

The classic RD Web Access interface uses browser-side XSLT transformations (Site.xsl), which Google Chrome has announced it will remove.

We are currently using Google Chrome 156 and already receive deprecation warnings.

We would appreciate clarification on the following questions:

  1. Is Microsoft planning to update the classic RD Web Access interface to remove its dependency on browser-side XSLT?
  2. Will such an update be provided for Windows Server 2022 and/or Windows Server 2025?
  3. Is there an official release date or roadmap for this change?
  4. If no update is planned, what is Microsoft's recommended and officially supported replacement for classic RD Web Access, including RemoteApp listing and RDP file downloads?
  5. How does Microsoft intend to ensure compatibility with future Chromium-based browsers after XSLT support is removed?

As this environment is used by both internal employees and external customers, maintaining all three access methods is essential.

Thank you for your assistance. We are operating a production Remote Desktop Services environment based on Windows Server 2022 with RD Web Access and RD Gateway.

Our environment provides three access methods, all of which are required by our employees and external customers:

  1. Classic RD Web Access (/RDWeb) for authentication, RemoteApp listing and RDP file downloads.
  2. RemoteApp and Desktop Connections via Windows Control Panel (RemoteApp feed).
  3. HTML5 Remote Desktop Web Client (/RDWeb/webclient).

The classic RD Web Access interface uses browser-side XSLT transformations (Site.xsl), which Google Chrome has announced it will remove.

We are currently using Google Chrome 156 and already receive deprecation warnings.

We would appreciate clarification on the following questions:

  1. Is Microsoft planning to update the classic RD Web Access interface to remove its dependency on browser-side XSLT?
  2. Will such an update be provided for Windows Server 2022 and/or Windows Server 2025?
  3. Is there an official release date or roadmap for this change?
  4. If no update is planned, what is Microsoft's recommended and officially supported replacement for classic RD Web Access, including RemoteApp listing and RDP file downloads?
  5. How does Microsoft intend to ensure compatibility with future Chromium-based browsers after XSLT support is removed?

As this environment is used by both internal employees and external customers, maintaining all three access methods is essential.

Thank you for your assistance.

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

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ronald Sabiiti 1,585 Reputation points Independent Advisor
    2026-11-03T13:36:39.3033333+00:00

    Hello Florian,

    The classic RD Web Access portal relies on browser-side XSLT transformations, so Google's planned removal of XSLT support may affect its functionality.

    Regarding your questions:

    Microsoft's plans: Current Microsoft guidance provides a temporary workaround but does not confirm a permanent redesign of classic RD Web Access.

    Windows Server 2022/2025: No specific update commitment for either version has been publicly confirmed.

    Release roadmap: No official release date or roadmap has been announced.

    Recommended alternative: Microsoft provides the HTML5 Remote Desktop Web Client for browser-based RemoteApp and desktop access. However, it should not be assumed to replace every classic RDWeb feature or the RemoteApp and Desktop Connections feed.

    Future browser compatibility: Microsoft currently documents a temporary Chrome Enterprise Policy workaround to re-enable XSLT:

    reg add "HKLM\SOFTWARE\Policies\Google\Chrome" /v XSLTEnabled /t REG_DWORD /d 1 /f

    Restart Chrome after applying the policy.

    For a production environment, I recommend retaining your existing configuration, testing the HTML5 client, and monitoring Microsoft's announcements for a permanent solution.

    Additional resources:

    If this information was helpful, please click Accept Answer.

    Thank you for choosing Microsoft Q&A.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Richard Warren 0 Reputation points
    2026-11-06T15:12:41.4533333+00:00

    Not sure on the M$ customisation policy for the pages but you can look into that

    Was this answer helpful?

    0 comments

  3. AI answer

    2026-11-03T12:38:47.5+00:00

    Microsoft has not announced a redesign of classic RD Web Access to remove its dependency on client-side XSLT. The current documented status is that Microsoft is working on a fix for the issue where RD Web Access fails to load when XSLT is disabled, and more information will be provided when available.

    No official release date, roadmap, or Windows Server version commitment is provided for Windows Server 2022 or Windows Server 2025 in the available documentation.

    What is documented today:

    1. Cause Classic RD Web Access depends on browser-side XSLT processing to render the interface. If XSLT is disabled by browser policy, RD Web Access fails to render by design.
    2. Current Microsoft workarounds
      • Temporarily re-enable XSLT in Microsoft Edge or Google Chrome by setting the XSLTEnabled policy to 1.
      • Use the HTML5 Remote Desktop web client (/RDWeb/webclient) to access published resources and download .rdp files.
      • Use Microsoft Edge in Internet Explorer mode for the RD Web portal.
    3. Recommended replacement path currently documented The only documented browser-based alternative for getting RDP files without relying on classic /RDWeb is the HTML5 Remote Desktop web client. The documented flow is:
      • Browse to /RDWeb/webclient/index.html
      • Sign in
      • View published resources
      • Use Settings > Download the rdp file to download the .rdp file
    4. Future Chromium compatibility Microsoft Edge documents XSLT deprecation as a high-impact change. It states that reliance on client-side XSLT should be treated as technical debt and that temporary mitigations such as the XSLTEnabled policy and origin-trial style mitigations are temporary and planned to stop functioning in Microsoft Edge 176. That means long-term compatibility for classic RD Web Access cannot be assumed if it continues to depend on browser-side XSLT.

    Based on the documented guidance, the supported direction today is to move browser-based access away from classic /RDWeb and use the HTML5 Remote Desktop web client where browser access and .rdp downloads are required.

    For the RemoteApp and Desktop Connections feed via Windows Control Panel, no change or replacement is described in the available documentation.

    Warning: re-enabling XSLT through browser policy or registry is a temporary workaround and should be treated as transitional, not a long-term solution.

    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.