Starting November 17, 2026, Google will remove support for XSLT to prevent potential security risks on Chromium-based browsers (including Google Chrome and Microsoft Edge). This change will prevent Classic UI screens in Acumatica ERP from loading in these browsers.
If your instance still relies on Classic UI, action is required before November 17, 2026.
What is the impact?
The severity of disruption depends on how much your instance relies on Classic UI. Any screen still running on Classic UI will stop loading in Chrome or Edge. If your team uses a mix of Modern and Classic UI, some workflows will be affected while others continue normally.
NOTE (Updated July 2026): Acumatica has delivered a fix that allows Classic UI to continue loading on Chromium-based browsers after November 17, 2026, in the latest patches for 2025 R1 and later versions. SaaS customers on 2025 R1 or later will receive this patch automatically within the next two to three weeks. PCS customers on 2025 R1 or later need to apply the patch manually before November 17, 2026.
Recommended Actions
If you are on Acumatica 2024 R2 or earlier:
- Upgrade to 2025 R1 or later to receive this fix.
- Use Mozilla Firefox as a temporary workaround until you can upgrade.
If you are on Acumatica 2025 R1 or later:
- (mid-July 2026) SaaS customers are receiving the fix automatically. No action is required.
- PCS customers need to apply the patch before November 17, 2026. Instructions and links are available on the community patches page: https://community.acumatica.com/patches-322.
- Plan your migration to Modern UI. Classic UI is being deprecated in 2026 R2.
Staying Updated
Monitor the Knowledge Base Article for the latest updates on this fix and its availability timeline.
Update – October 1, 2026
A recent, unexpected Chromium change caused this issue to surface earlier than anticipated. The previous Acumatica fix addressed Chromium’s planned removal of XSLT; however, this additional change modified XSLT behavior before its removal and requires an updated fix. Our engineering team immediately investigated and expedited the following patches:
- 2026 R1: October 6
- 2025 R2: October 8
- 2025 R1: October 8
Customers using Classic UI in Chrome, Edge or any other chromium based browser should apply the patch for their version when available. Until then, Firefox can be used as a temporary workaround OR alternative workarounds mentioned in this KB article. Customers on 2024 R2 or earlier should upgrade to a supported version or use Firefox.
