Unable to display RD Web Access: Chrome 158 and Edge 159 turn off XSLT

Unable to display RD Web Access
An unexpected error has occurred that is preventing this page from being displayed correctly.

Short answer: Chrome 158 turns off XSLT, which the RD Web Access portal (Windows Server 2016–2025) needs, so users see "Unable to display RD Web Access". It reaches some Chrome users from 4 November 2026 and everyone from 17 November; Edge 159 follows in mid-December. Set the XSLTEnabled policy for Chrome and Edge by Group Policy or Intune now, then move users to the Remote Desktop web client or the RemoteApp feed before the policy ends in 2027.

Why it happens

RD Web Access builds its pages in the browser with client-side XSLT (Microsoft KB5130994, 6 October 2026). Chrome 158 removes XSLT: early stable reaches a small share of users on 4 November 2026, stable rolls out from 17 November, and Chrome Beta 158 has had it off since 28 October. Microsoft Edge 159 turns XSLT off by default in Stable from mid-December 2026 (MC1509789). Microsoft says it's working on a fix for RD Web Access but gives no date. Until then, the XSLTEnabled policy keeps XSLT working, but only until Chrome and Edge 176 (Chrome 176: 17 August 2027).

Fix

Stop-gap on a few PCs, from Microsoft's KB (elevated Command Prompt):
```
reg add "HKLM\SOFTWARE\Policies\Google\Chrome" /v XSLTEnabled /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Edge" /v XSLTEnabled /t REG_DWORD /d 1 /f
```
Restart the browser and open chrome://policy or edge://policy: XSLTEnabled should show true. Then open the portal again.
Many PCs: in Group Policy, go to Computer Configuration → Policies → Administrative Templates → Google → Google Chrome → Control the availability of the XSLT feature → Enabled, and set the same policy under Microsoft Edge. You need the ADMX templates from Chrome 146 or Edge 147 or later. In Intune, search the Settings catalog for XSLT (Microsoft Edge and Google Chrome), or deploy the two registry values with a script. On Macs, push a configuration profile with XSLTEnabled = true for com.google.Chrome and com.microsoft.Edge.
Lasting fix: publish the Remote Desktop web client, which Microsoft lists as a workaround, at https://<server FQDN>/RDWeb/webclient/index.html. It needs an RD Gateway, per-user CALs and publicly trusted certificates on the RD Gateway and RD Web Access roles. Export the RD Connection Broker certificate as a .cer file, then on the RD Web Access server (elevated PowerShell):
```
Install-Module -Name RDWebClientManagement
Install-RDWebClientPackage
Import-RDWebClientBrokerCert C:\temp\broker.cer
Publish-RDWebClientPackage -Type Production -Latest
```
On Windows Server 2016, run Install-Module -Name PowerShellGet -Force first and restart PowerShell.
No RD Gateway? Give users the RemoteApp feed instead of the portal: on Windows, open Control Panel → RemoteApp and Desktop Connections → Access RemoteApp and desktops and enter https://<server FQDN>/RDWeb/Feed/webfeed.aspx. The published apps and desktops then appear in the Start menu and open in the normal Remote Desktop client.
Edge IE mode also works (Microsoft's third workaround): Edge → Settings → Default browser → set Allow sites to be reloaded in Internet Explorer mode to Allow, add the RD Web Access URL under Internet Explorer mode pages and restart Edge. Approve ActiveX if Edge asks: it enables single sign-on.

Watch out

The policy is temporary. Chrome and Edge 176 remove it (Chrome 176: 17 August 2027), so use it to buy time, not as the fix.
Group Policy and Intune don't reach personal or home PCs. Send those users the web client URL or the feed URL before 17 November.
Chrome users break first, from 4 November. Edge users keep working until Edge 159 reaches them in mid-December.
Microsoft is working on a fix in RD Web Access itself. When it ships, install it on every RD Web Access server; this page will be updated.

Sources

Did this fix it?

Other errors breaking soon

All "breaking soon" fixes