Chrome is deprecating client-side support for XSLT, including the XSLTProcessor JavaScript API and the XSLT processing instruction, which K2 uses in design time and runtime experiences. Chrome plans to remove this support starting with version 158, scheduled for release on November 17, 2026. Fix packs will be released for supported K2 versions (5.7), (5.8), (5.9), (5.9.1), and later so that K2 will continue to function after the deprecation.
The following fix pack is available for download for Nintex Automation K2
We recommend installing the latest available fix pack as soon as possible. If you cannot do so before November 17, 2026, the following workarounds, based on Chrome’s own mitigation options, can help extend functionality temporarily.
Short Term (0–1 month): Enterprise Policy Controls
-
Enable XSLT through Chrome’s enterprise policy. Configure the policy dedicated to XSLT preservation via your Google Admin Console or Group Policy. (The exact policy name and registry key will be published once Chromium releases the feature.)
-
Google also offers an official XSLT Polyfill Extension. Administrators can force-install this extension via the Chrome Apps & Extensions Management policy to preserve functionality while migrating legacy web applications.
-
As a temporary manual fallback, open Chrome and go to chrome://flags/. Search for “XSLT” and select “Enabled” in the dropdown.
Note: We do not know how long this option will be available. Set it to Enabled as soon as possible.
Medium Term (3–6 months): Freeze Browser Versions
Prevent automatic updates by locking the browser to the last compatible version before the XSLT deprecation.
-
Google Chrome: configure the UpdatePolicies registry key and set Update{AppGuid} to 0 to disable updates.
-
Microsoft Edge: use the Update policy overrides to disable updates for specific browser versions.
-
Reference: see the Google Chrome Enterprise Policy List or Microsoft Edge Enterprise Policy Documentation for the appropriate Group Policy Object (GPO) templates.
Caution: This approach carries security risks, as users running older browser versions may be exposed to vulnerabilities that have been addressed in later releases.
Long Term: Upgrade to a K2 Supported Version and Fix Pack
We will be releasing fix packs for K2 versions (5.7), (5.8), (5.9), (5.9.1) and later, and Nintex K2 Cloud to follow the development practices from Google. As these fix packs are released, we will update this article and post links here. All versions from K2 (5.10) on will have this fix included.
Upgrade to the latest K2 fix pack available for your current version, so you’re on a build unaffected by the deprecation or upgrade to the latest version of Nintex Automation K2.