Chrome 158 removes XSLT on 17 November 2026: which apps break, and each vendor's fix
Short answer: Chrome 158 reaches every Stable user on 17 November 2026, rolled out in steps.
From then on, pages that turn XML into HTML in the browser with XSLT show a blank page or raw XML, plus a warning banner.
Edge 159 does the same from mid-December 2026. On managed PCs the XSLTEnabled policy keeps XSLT
working until Chrome and Edge 176 (Chrome 176: 17 August 2027). Firefox and Safari still run XSLT today. Google says both
projects plan to remove it too, but neither has given a date.
Apps that break, and the fix for each
Each row links the vendor's own notice. Checked 31 October 2026. Know an app that breaks? Email the vendor's notice to hello@deadlinefix.com and it goes into the table.
| App | What breaks | Vendor's fix | Do this before 17 Nov | Source |
|---|---|---|---|---|
| Remote Desktop Web Access (Windows Server RDS) | The portal shows "Unable to display RD Web Access. An unexpected error has occurred…" | Microsoft says a fix is in progress, with no date. Workarounds: the XSLTEnabled browser policy, the HTML5 Remote Desktop web client, or Edge IE mode. | Push the policy to managed PCs and tell home users about the web client. Step-by-step fix. | Microsoft KB5130994 |
| Acumatica (Classic UI screens) | Classic UI screens stop loading in Chrome and Edge; mixed Modern/Classic sites lose only some workflows. | Patches: 2026 R1 (6 Oct 2026), 2025 R2 and 2025 R1 (8 Oct 2026). SaaS on 2025 R1 or later gets it automatically. 2024 R2 and older: no fix; Acumatica says upgrade or use Firefox. Classic UI is deprecated in 2026 R2. | On-premises: apply your version's October patch. Older versions: plan the upgrade now, and use Firefox meanwhile. | Acumatica community |
| Access Mosaic Case Management (before 26.1) | Forms show a blank screen instead of the form content, so form data can't be reached. | Mosaic 26.1 no longer needs browser XSLT. For Edge, the vendor suggests the XSLTEnabled policy as a temporary workaround. | Upgrade to Mosaic 26.1. Until then, set the policy on managed PCs. | The Access Group |
| Aras Innovator (all versions) | Grids, reports and other parts of the UI that the browser renders with XSLT. | Release 39 includes Aras's WebAssembly polyfill. Hotfix 12141 adds it to Releases 22–38. Releases 14–21: see the self-upgrade docs. Older releases are handled case by case. | Apply hotfix 12141 in staging, then production. Also review custom pages that call XSLTProcessor; the hotfix doesn't cover them. | Aras Support Bulletin |
| InterSystems products (some pages) | Pages that transform XML in the browser show raw XML or an empty page, plus Chrome's warning banner. | InterSystems says many of its products use some in-browser XSLT and promised official mitigation plans soon (post dated 15 Oct 2026). No product list or versions yet. | Test your own portals with XSLT turned off now (policy on a test PC), and watch for the vendor's notice. | InterSystems Developer Community |
| XML sitemaps and RSS/Atom feeds with an XSL stylesheet (WordPress core sitemaps, Yoast SEO, Rank Math and others) | Only the pretty view a person sees when opening the file in Chrome. It becomes raw XML or the banner. | Nothing breaks for Google, Bing or feed readers: they read the XML, not the styled page. | Nothing required. If you want the styled view back, Google's polyfill script works with one line in the XML. | Chrome for Developers |
| Admin pages of printers, routers and other devices that turn XML into HTML in the browser | A blank or raw-XML admin page on the device's own web interface. | Install a firmware update if the vendor ships one. Google also offers a Chrome extension that applies its polyfill to raw XML pages, for devices whose pages can't be changed. | Check each device's admin page with XSLT turned off. Keep the policy on the admin PCs until firmware is fixed. | Chrome for Developers |
Is your own app affected? Check before 17 November
- Turn XSLT off on one test PC: set the
XSLTEnabledpolicy to disabled (Chrome and Edge both read it), then open your apps. Whatever goes blank now will go blank for everyone on 17 November. - DevTools: open the app, then look in the Console and Issues panels for XSLT deprecation warnings. A Lighthouse audit flags it under Best Practices. Microsoft recommends this check in its Edge notice.
- In code: search for
new XSLTProcessorand for<?xml-stylesheet … type="text/xsl"in XML your servers send to browsers. - Across a company: Chrome Enterprise admins can use the Legacy Technology Report to see which internal sites still use XSLT.
The fixes, from quickest to lasting
- Buy time on managed PCs: set
XSLTEnabled= 1 for Chrome and Edge through Group Policy or Intune. It stops working in version 176, so treat it as a bridge. The exact registry paths and Intune settings are in our RD Web Access fix; they are the same for every app. - Public sites you run: Chrome's origin trial keeps XSLT on for your site until Chrome 176.
- Code you control: do the transform on the server and send HTML; or send JSON and render it with JavaScript; or load
Google's
xslt-polyfill(WebAssembly, replacesXSLTProcessor), or SaxonJS for XSLT 3.0. - XML you can't change (devices, vendor apps): Google's Chrome extension applies the same polyfill to raw XML pages. Otherwise, update or upgrade as each vendor says above.
RD Web Access users: want the fix worked out for your setup? I send the exact Chrome and Edge
policy for your Group Policy, Intune or registry, a PowerShell script that checks every PC, a note for your users and the HTML5
web client steps. No passwords or remote access needed.
Get the fix pack: $39
Get the fix pack: $39
Pay by card, no account needed. Within 24 hours; still broken, full refund.
Dates
| Date | What happens |
|---|---|
| 10 Mar 2026 (Chrome 146) | XSLTEnabled enterprise policy available for testing |
| 25 Aug 2026 (Chrome 152) | Origin trial opens for sites that need more time |
| 17 Nov 2026 (Chrome 158) | XSLT stops working on Stable for everyone outside the policy and the trial |
| Mid-Dec 2026 (Edge 159) | XSLT off by default in Edge Stable |
| 17 Aug 2027 (Chrome 176) | The policy and the origin trial stop working: XSLT is off for everyone |
Sources
- Chrome for Developers: Removing XSLT for a more secure browser
- Chromium Dash: milestone 158 schedule
- Microsoft 365 message MC1509789 (15 Oct 2026): XSLT off by default in Edge 159
- Microsoft KB5130994: RD Web Access fails to load when XSLT is disabled
- Acumatica community: Chromium XSLT deprecation affecting Classic UI (updated 1 Oct 2026)
- The Access Group: Browser changes impacting Mosaic forms
- Aras Support Bulletin: Hotfix 12141, browser compatibility alert (12 Jun 2026)
- InterSystems Developer Community: Test your site against Chrome's XSLT removal today (15 Oct 2026)
Independent tracker, not affiliated with Google, Microsoft or any vendor named. Vendor details as published by each vendor on the date checked.
Did this fix it?