Users see an error page that reads roughly: "Unable to display RD Web Access. An unexpected error has occurred that is preventing this page from being displayed correctly." The RDS deployment may be running normally. The failure is in the browser, which can no longer render the portal page.
Microsoft does not treat this as a browser bug. The KB says browsers across the industry are dropping XSLT for more secure alternatives, and it describes the symptoms as an expected result of that security work. For now Microsoft lists three workarounds and says it is working on a fix, with more information to come. It gives no patch, build number or date.
Why the portal breaks
The classic RD Web Access interface is rendered in the browser with XSLT. The server sends XML, and the browser's XSLT processor turns it into the page users see. If browser policy turns that processor off, the page cannot be built.
The XSLT feature covers two things that browsers are now removing: the XSLTProcessor JavaScript API and the XSL processing instruction in XML documents. Google's Chrome Enterprise policy documentation says the XSLTEnabled policy controls the availability of the XSLT feature (the XSLTProcessor Javascript API and the XSL processing instruction). Microsoft's Edge policy documentation describes the Edge policy the same way.
Summary: RD Web Access depends on a browser feature that Chromium-based browsers are removing. Admins who have already hardened their browsers will see the problem first.
The timeline: this is likely to spread
The KB describes the failure as happening when XSLT is "disabled through browser policy." That is how most organizations will hit it today. Browser defaults are changing too, though.
- Edge: Microsoft added the
XSLTEnabledpolicy in Edge 147. Neowin reported that Microsoft wants enterprise customers to use the policy to evaluate the effect of disabling XSLT. Microsoft's Learn page says the policy is temporary and will be removed in a future Edge version. It gives no removal date. - Chrome: Several published timelines say XSLT stops working on Chrome Stable on November 17, 2026. One tracker of Google's schedule says XSLT will stop working on Stable for all users other than Origin Trial and Enterprise Policy participants. Third-party guides agree on the dates but not on the version numbers. Google's original October 2025 schedule tied the stable cutoff to Chrome 155. Later guides cite Chrome 158 for the same November 17 date and put the end of the exceptions at Chrome 176 in August 2027. Google's own Chrome Enterprise policy page says the policy is a temporary measure, and will be removed in M164. Rely on the dates (mid-November 2026 for default-off, August 2027 for the end of the policy exception) rather than the milestone numbers until Google's current schedule confirms them.
Analysis: This is our inference, not something the KB says. Once Chrome Stable turns XSLT off by default, a managed Chrome machine with no XSLT policy may fail the same way a deliberately hardened one does today. Microsoft has not published a matching default-off date for Edge. Edge is built on Chromium, though, so expect Edge to follow and watch Microsoft's announcements. In practice, the KB's "browser policy" trigger probably won't stay limited to locked-down fleets.
Summary: Today this mostly affects hardened browsers. Based on Google's published dates, plan for it to affect ordinary Chrome users from mid-November 2026.
Workaround 1: Turn XSLT back on (temporarily)
This is the quickest fix and brings back the browser feature the portal needs. Set the XSLTEnabled policy to 1 on the client. You can do that through Group Policy or with these registry commands from an elevated Command Prompt.
Microsoft Edge:
reg add "HKLM\SOFTWARE\Policies\Microsoft\Edge" /v XSLTEnabled /t REG_DWORD /d 1 /f
Google Chrome:
reg add "HKLM\SOFTWARE\Policies\Google\Chrome" /v XSLTEnabled /t REG_DWORD /d 1 /f
Then:
- Restart Edge or Chrome.
- Go to the RD Web Access site.
- Check that the page loads.
Group Policy details for Edge: Microsoft Learn lists the policy as Control the availability of the XSLT feature under Administrative Templates/Microsoft Edge, in MSEdge.admx. It is a Boolean policy stored as a REG_DWORD named XSLTEnabled under SOFTWARE\Policies\Microsoft\Edge. Other details from the same page:
| Edge policy detail | Value |
|---|---|
| Supported Edge versions | 147 and later (Windows, macOS) |
| Android / iOS | Not supported |
| Mandatory policy | Yes |
| Recommended policy | No |
| Dynamic refresh | Yes |
| Applies to a profile signed in with a Microsoft account | No |
What each setting does:
- Enabled: XSLT is available regardless of browser defaults.
- Disabled: XSLT is unavailable regardless of browser defaults.
- Not configured: the browser's defaults and any field trials decide.
The last row of the table matters for troubleshooting. If a user says "I set it and nothing changed," check whether they are signed into an Edge profile with a personal Microsoft account. Microsoft's documentation says the policy does not apply to those profiles.
Things to weigh:
- You are reversing a security setting your organization probably chose on purpose. Scope the exception narrowly, record it, and set a review date.
- Both vendors call the policy temporary. Google says the Chrome policy goes away at a set future milestone. It postpones the problem but does not fix it.
- The commands above set the policy for the whole machine. If only some users need RD Web Access, target the setting with Group Policy instead of applying it to the whole fleet.
Workaround 2: Use the HTML5 Remote Desktop web client
If you don't want to weaken browser policy, the RD web client is a separate endpoint and doesn't need XSLT. Microsoft's example URL is:
https://rdweb_server_FQDN/RDWeb/webclient/index.html
Steps for users:
- Go to the web client URL.
- Sign in. Your available remote resources should appear.
- Either launch a session in the browser or download the RDP file.
- To download it, select Settings in the top-right corner, choose Download the rdp file, then select OK.
- The
.rdpfile should appear in the Downloads folder.
The catch: this only works if an administrator has already deployed and published the web client. Installing RD Web Access does not install it. Microsoft's setup documentation requires RD Gateway, RD Connection Broker and RD Web Access roles, per-user client access licenses (CALs) rather than per-device, and trusted public certificates on RD Gateway and RD Web Access. If your deployment uses per-device CALs, plan the licensing work before you announce this option to users.
Workaround 3: Load the portal in Edge's Internet Explorer mode
IE mode uses the old Trident rendering engine, which still runs the portal as it was designed. To set it up:
- Open Microsoft Edge.
- Go to Settings and more (…) > Settings > Default browser.
- Under Internet Explorer compatibility, set Allow sites to be reloaded in Internet Explorer mode (IE mode) to Allow.
- Next to Internet Explorer mode pages, select Add and enter your RD Web URL.
- Restart Edge if prompted.
- Open the RD Web portal.
First-run prompt: The first time the portal opens in IE mode, Edge may ask whether to allow ActiveX. Microsoft says to select Allow, because that permission lets the portal use the signed-in user's credentials for single sign-on.
Things to weigh: This sends users back to a legacy engine and requires an ActiveX approval. For a large fleet, it is usually better to deploy the site through your Enterprise Mode site list than to have each user follow these steps. That is general practice, not a step from this KB.
Triage checklist for the help desk
- Confirm the error. The KB covers the "Unable to display RD Web Access" message in Edge or Chrome. It does not claim to cover every RD Web failure.
- Check the policy. Open
edge://policyorchrome://policyon the affected machine and look forXSLTEnabled. - Test it. If enabling XSLT brings the page back, you have found the cause, but you still need a lasting fix.
- Choose a path: a temporary policy exception, a web client you have already deployed, or IE mode for the users who need it.
- Watch for Microsoft's fix. No date has been announced.
The bigger picture
The KB is written as a workaround article, but the broader message is that the classic RD Web Access page depends on a technology that major browsers are retiring. Neowin reported that besides Chromium, two other major browser engines, WebKit (used in Safari) and Gecko (Firefox), are getting rid of the language soon, too.
None of the three workarounds lasts long. The XSLT policy is temporary in both browsers, IE mode is a compatibility layer, and the HTML5 client needs deployment work that many RDS environments never did. Microsoft's promised fix is what will matter, and admins should have a plan in place well before the browser policy exceptions end in August 2027.
Bottom line: If your users reach RDS through the classic RD Web Access page, check browser policies now, consider deploying the HTML5 web client if it isn't already in place, and keep a short-term XSLT exception ready for Chrome's November 2026 change.
Update: Microsoft reportedly sets mid-November cutoff for Edge as well as Chrome (October 9, 2026)
WindowsReport reports that Microsoft 365 Message Center post MC1491832 now says both Microsoft Edge and Google Chrome will disable XSLT support in mid-November 2026. That is more specific than the original KB’s browser-policy framing and, if confirmed in tenants’ Message Center notices, means the exposure is not limited to Chrome or to organizations that deliberately disabled XSLT themselves.
The practical change is especially important for Edge-based RDS environments: admins should test the classic RD Web Access portal in a browser configuration where XSLT is unavailable before mid-November, rather than assuming Edge will retain the feature longer. The existing temporary policy override, HTML5 web client, and IE mode options remain the listed mitigations.
WindowsReport also says Microsoft intends to keep Edge’s IE mode available until at least 2029. That extends the likely availability of the legacy-engine fallback, but it does not turn IE mode into a long-term replacement for modernizing the RD Web Access experience.
References
- Microsoft Warns Chromium Changes Will Break RD Web Access in Edge and Chrome Windows Report · 2026-10-09T13:38:37+00:00
- Take action to prevent RD Web Access rendering failures Microsoft - Message Center · 2026-10-08 12:00 PT
- Microsoft is removing XSLT support in Edge - Neowin neowin.net