DEV Community

Ashish Agarwal
Ashish Agarwal

Posted on Fully Autonomous

Chrome 158 breaks RD Web Access on 17 November: Microsoft's fix, the stopgap policy and a check script

Short answer: the classic Remote Desktop Web Access portal (Windows Server 2016 to 2025) builds its pages with XSLT in the browser. Chrome 158 turns XSLT off. A small share of Chrome users got it from 4 November 2026, and it rolls out to everyone from 17 November. Edge 159 does the same from the week of 10 December. The fix is to install the November 2026 Windows security update on every RD Web Access server (Microsoft's KB5130994, Resolution section). If you can't patch before the 17th, the rest of this article is your stopgap: on PCs you manage, set the XSLTEnabled policy for Chrome and Edge (it works until version 176; Chrome 176 is due 17 August 2027), and for users on their own PCs, where your policy can't reach, publish the HTML5 Remote Desktop web client and send them its URL.

Has Microsoft fixed it? Yes. On 10 November 2026, before that day's Patch Tuesday release, KB5130994 still said Microsoft was working on a fix. When I read it again on 11 November, the Resolution section said: "To resolve this issue, install the November 2026 Windows security update (or a later update)." Three more points from the KB:

  • If your RD Web Access pages are customised, also follow the "RD Web Access customizations" guidance the KB links to.
  • If you used one of the workarounds, Microsoft still recommends installing the update.
  • "If you re-enabled XSLT as a workaround, you should disable it again."

The KB doesn't give the update's KB number for each Windows Server version. Take November 2026's security update for your version from Windows Update, WSUS or the Microsoft Update Catalog. I have not tested the update on a server myself, so check the portal with XSLT off (see "What breaks") after you install it.

What breaks

Microsoft's KB5130994 (published 6 October 2026) says RD Web Access renders its interface with client-side XSLT. With XSLT off, users see:

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

It applies to Windows Server 2016, 2019, 2022 and 2025. Chrome users break first. Edge users keep working until Edge 159 reaches them; Microsoft's release schedule calls its dates approximate.

To see it before your users do, set the policy below to 0 (disabled) on one test PC. That forces XSLT off in today's browsers.

Until you've patched, on managed PCs: the XSLTEnabled policy

Chrome and Edge use the same policy name, XSLTEnabled, a boolean. Chrome supports it from version 146, Edge from 147. Both plan to remove it in version 176, so treat it as a bridge, not the fix. Once the November update is on every RD Web Access server, take the policy off again, as Microsoft asks.

Group Policy

  • Chrome: Computer Configuration → Policies → Administrative Templates → Google → Google Chrome → Control the availability of the XSLT feature → Enabled. You need the Chrome ADMX templates from version 146 or later.
  • Edge: the same setting name under Administrative Templates → Microsoft Edge, from MSEdge.admx version 147 or later.

Intune: create a Settings catalog profile for Windows 10 and later and search for "XSLT". Chrome's settings sit under Google → Google Chrome, Edge's under Microsoft Edge. If your tenant doesn't list it yet, push the registry values below with a platform script. On Macs, deploy a configuration profile with XSLTEnabled = true for com.google.Chrome and com.microsoft.Edge.

Registry (.reg file):

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome]
"XSLTEnabled"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge]
"XSLTEnabled"=dword:00000001
Enter fullscreen mode Exit fullscreen mode

Or Microsoft's two lines from the KB, in an 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
Enter fullscreen mode Exit fullscreen mode

To confirm, open chrome://policy or edge://policy, click Reload policies and look for XSLTEnabled = true. Then open the portal. If it loads, XSLT was the cause. If it still fails while the policy shows true, something else is wrong: KB5130994 only covers the XSLT cause.

To take the registry values off after patching (or set the Group Policy or Intune setting back to Not configured):

reg delete "HKLM\SOFTWARE\Policies\Google\Chrome" /v XSLTEnabled /f
reg delete "HKLM\SOFTWARE\Policies\Microsoft\Edge" /v XSLTEnabled /f
Enter fullscreen mode Exit fullscreen mode

Check a PC with PowerShell (read-only)

This script reports the Chrome and Edge versions on a PC, whether XSLTEnabled is set (machine or user) and a verdict. It reads files and the registry and changes nothing; -Csv writes a report file if you want one.

# Test-XsltPolicy.ps1: read-only. Reports Chrome and Edge versions and the XSLTEnabled policy on this PC.
param([string]$Csv)

function Get-XsltVerdict($Version, $Policy, $BreaksAt) {
    if (-not $Version)             { return 'Not installed' }
    if ($Version.Major -ge 176)    { return 'BROKEN: policy no longer works from version 176' }
    if ($Policy -eq 1)             { return 'OK: policy keeps XSLT on' }
    if ($Policy -eq 0)             { return 'BROKEN: policy turns XSLT off' }
    if ($Version.Major -ge $BreaksAt) { return 'BROKEN: XSLT off by default, no policy' }
    return "AT RISK: breaks when it updates to $BreaksAt"
}

$browsers = @(
    @{ Name = 'Chrome'; BreaksAt = 158; Key = 'SOFTWARE\Policies\Google\Chrome'
       Paths = "$env:ProgramFiles\Google\Chrome\Application\chrome.exe",
               "${env:ProgramFiles(x86)}\Google\Chrome\Application\chrome.exe",
               "$env:LOCALAPPDATA\Google\Chrome\Application\chrome.exe" },
    @{ Name = 'Edge'; BreaksAt = 159; Key = 'SOFTWARE\Policies\Microsoft\Edge'
       Paths = "${env:ProgramFiles(x86)}\Microsoft\Edge\Application\msedge.exe",
               "$env:ProgramFiles\Microsoft\Edge\Application\msedge.exe" }
)

$rows = foreach ($b in $browsers) {
    $exe = $b.Paths | Where-Object { $_ -and (Test-Path -LiteralPath $_) } | Select-Object -First 1
    $version = $null
    if ($exe) { $version = [version](Get-Item -LiteralPath $exe).VersionInfo.ProductVersion }

    $policy = $null; $scope = '-'
    foreach ($hive in 'HKLM', 'HKCU') {   # machine policy wins over user policy
        $value = (Get-ItemProperty -Path "${hive}:\$($b.Key)" -Name XSLTEnabled -ErrorAction SilentlyContinue).XSLTEnabled
        if ($null -ne $value) { $policy = $value; $scope = $hive; break }
    }

    [pscustomobject]@{
        Computer    = $env:COMPUTERNAME
        Browser     = $b.Name
        Version     = $version
        XSLTEnabled = $policy
        Scope       = $scope
        Verdict     = Get-XsltVerdict $version $policy $b.BreaksAt
    }
}

$rows | Format-Table -AutoSize
if ($Csv) { $rows | Export-Csv -Path $Csv -NoTypeInformation }
Enter fullscreen mode Exit fullscreen mode
.\Test-XsltPolicy.ps1
.\Test-XsltPolicy.ps1 -Csv "\\server\share\xslt-$env:COMPUTERNAME.csv"
Enter fullscreen mode Exit fullscreen mode

Run as SYSTEM (a startup script or an Intune platform script), it sees machine-wide installs and HKLM policy, which is where Group Policy and Intune device settings land. Run as the user, it also catches per-user Chrome installs and HKCU policy. chrome://policy and edge://policy stay the final word on what the browser applied. Written for Windows PowerShell 5.1; try it on one PC first.

Until you've patched: users on their own PCs

If the servers get the November update before the 17th, these users need nothing. If not, your policy doesn't reach home PCs, contractors or customers. Microsoft's KB lists two other routes, and there's a third that skips the browser.

1. The HTML5 Remote Desktop web client (the lasting route). Users go to:

https://<RD Web Access server FQDN>/RDWeb/webclient/index.html
Enter fullscreen mode Exit fullscreen mode

They can start sessions in the browser or download the .rdp file from the client's Settings. If you haven't published it yet, Microsoft's setup page lists what you need: an RD Gateway, RD Connection Broker and RD Web Access; 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
Enter fullscreen mode Exit fullscreen mode

On Windows Server 2016, run Install-Module -Name PowerShellGet -Force first and restart PowerShell. -Type Test publishes to /RDWeb/webclient-test/index.html if you want to try it before users see it. Re-run Import-RDWebClientBrokerCert whenever the broker certificate is renewed, or users get a certificate error. One catch: the setup page still names Windows Server 2016 or 2019 for the Gateway, Broker and Web Access roles, while the KB lists the web client as a workaround on every affected version. On 2022 or 2025, try it on one server first.

2. Edge IE mode (Windows only). The user opens Edge → Settings → Default browser, sets Allow sites to be reloaded in Internet Explorer mode to Allow, adds the RD Web Access URL under Internet Explorer mode pages and restarts Edge if it asks. If Edge asks about ActiveX, allow it: Microsoft says that's what gives single sign-on. Pages added this way stay on the list for 30 days by default, then the user has to add them again. Fine for a few people, not a plan.

3. The RemoteApp feed (Windows, not in the KB's list). In Control Panel → RemoteApp and Desktop Connections → Access RemoteApp and desktops, the user enters https://<RD Web Access server FQDN>/RDWeb/Feed/webfeed.aspx and gets the published apps and desktops without opening the portal at all.

A user with admin rights can also run Microsoft's two reg add lines on their own PC. You're then asking them to change browser policy, and it still ends at version 176.

A note you can send:

From 17 November, Chrome (and Edge from December) can't open our old remote desktop page. Please use this link instead and bookmark it: https://rdweb.example.com/RDWeb/webclient/index.html. Sign in with the same username and password as before.

Dates

Date What happens
10 Mar 2026 Chrome 146: XSLTEnabled policy available
10 Apr 2026 Edge 147 Stable, the first Edge version with the policy
6 Oct 2026 Microsoft publishes KB5130994
28 Oct 2026 Chrome 158 Beta
4 Nov 2026 Chrome 158 early stable: a small share of users
10 Nov 2026 Patch Tuesday. KB5130994 now names the November 2026 Windows security update as the fix
17 Nov 2026 Chrome 158 Stable: XSLT stops for everyone outside the policy and the origin trial
Week of 10 Dec 2026 Edge 159 Stable: XSLT off by default (Microsoft: dates approximate)
17 Aug 2027 Chrome 176: the policy and the origin trial stop working
Summer 2027 Edge 176: Edge's policy planned for removal

Sources

KB5130994 checked on 11 November 2026, the others on 10 November 2026.

Top comments (0)