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:
- 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.
- Current Microsoft workarounds
- Temporarily re-enable XSLT in Microsoft Edge or Google Chrome by setting the
XSLTEnabledpolicy to1. - Use the HTML5 Remote Desktop web client (
/RDWeb/webclient) to access published resources and download.rdpfiles. - Use Microsoft Edge in Internet Explorer mode for the RD Web portal.
- Temporarily re-enable XSLT in Microsoft Edge or Google Chrome by setting the
- Recommended replacement path currently documented
The only documented browser-based alternative for getting RDP files without relying on classic
/RDWebis 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
.rdpfile
- Browse to
- 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
XSLTEnabledpolicy 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.