TL;DR
2026.03.To avoid data corruption and UI problems in Accruent MC it is urgent that you update to using the "Desktop App for MC" immediately.
On purpose by Google Chromium, 1% of users will start experiencing March 2026 and by September 2026 100% of users will be experiencing. You need to start using the "Desktop App for MC" before it affects you.
And after you do, you won't ever want to go back to a browser for MC.
Permanent solution
Our "Desktop App for MC" a general release product as of version 3.1. While this release is in beta, the problems (described below) starting March 2026 with Chromium are so bad, we recommend you upgrade to using this no additional charge?It is included for all customers that have paid up SMA for their MC product through Asset Pro Solutions Inc. DBA Maintenance Connection Canada or ITIQPro Inc. product today.
If you want to be on our beta, and we recommend you do, contact support@MaintenanceConnection.ca and state "beta, Desktop App for MC V3". For more info and to get the product see Desktop App for MC - So much better than in a browser
Products affected (without the Desktop App for MC):
- Accruent's MC, all versions from MC 1.0 to MC 2025 (Verified explicitly on MC 2025, MC 2022, MC 8.9, MC 6, MC 3.5). See experience section below for more details on how it affects.
- This is not just against Accruent's software, it is against a wide number of other web applications on the internet, their results will vary depending on how they use this browser feature.
Sometime likely in Oct 2026 or later, any temporary work around fixes will cease to work. If you are using a temporary fix, make sure you switch to "Desktop app for MC" before October 2026.
Switching to Edge or Brave or Chrome (whichever you aren't currently using) won't work, they use the Chromium engine.
Switching to Firefox or Safari won't work - they have had this issue going back many years and is one of several reasons that neither Firefox nor Safari are compatible.
Does not affect:
- MCe (all products and versions)
- Software that doesn't use the deprecated event.
Announced by Chrome in 2019:
In 2019 with subsequent announcements after, (see https://developer.chrome.com/docs/web-platform/deprecating-unload) effects starting in 2025 for major web applications and 2026 for all remaining web applications such as Accruent's MC. As you can see on that link, as of May 5th, 10% of people and sites will be affect. That means if Chromium/Google picks your URL - everyone will have the problem. If they don't pick your URL then statistically 10% of your users will be affected. And as you can see at the link, they have not published the algorithm for how they are picking which site and who will be affected, just the statistical probability.
Experience if you aren't running in the "Desktop App for MC":
Random UI failures, each time in and/or each user may experience one or more of:
- you hit the save button, but data is not actually saved
- data does not visually update properly
- buttons, like Save or Cancel, do not show up
- Sections of the page, like toolbar, do not show up
They aren't technically random, but they do seem to be based on timing. So something that works 'this time' doesn't work 'next time'. So it has the effect of being random.
We suspect, at times, it will appear consistent for a while, a while perhaps meaning days, due to page caching, but we are no longer focused on defining the specifics of the problem.
It will be frustrating for Accruent as they may think they have fixed all the issues only to find out that some where 'hidden' and only show up for some people. Our Desktop App for MC fixes it from the opposite direction - by getting rid of the problem at the source.
In the developer tools 'console' the browser even tells you when it is purposely corrupting the UI:
Cause, Chromium (Chrome, Edge and more):
Chrome (Chromium) 146.0 on March 10th has picked 1% of page loads to break a feature than MC has used heavily since version 1. This means that if a given page in MC has 5 'page loads,' you have a 5% chance that 'this time' something will be broken.
Google promises that 2026.09.22 (Sept 22) 100% will be broken unless you set the special option. They are not yet saying when that special option is removed, but based on past experience it will likely be at least a few weeks after Sept 22, 2026 and likely 1 to 4 months, but this can't be relied on so, as below, there are 2 permanent solutions being worked on, one by Accruent and one by us.
More information from Chromium directly talking about why they are doing this (no benefit to Accruent MC users), how they are doing, when they are doing it (including the 1% on March 10th and so on until Sept 22)
https://developer.chrome.com/docs/web-platform/deprecating-unload
Solutions:
Available now, "Desktop App for MC"
The best solution. And an excellent product you should be using even without this problem.
This provides permanent solution, and is especially important for customers who:
- will be willing to upgrade to Accruent's fix, as above, when Accruent has it ready. For them, this solution, though permanent, can be treated as a temporary fix if you want, turning the need to upgrade from a requirement before Chromium breaks them permanently, into a 'upgrade when convenient for you'. However - once you try it, you probably won't ever want to go back because of the many other benefits we've taken advantage of since 2017.
- are not ready to upgrade to newer Accruent MC due to a multitude of very good reasons known to them and sometimes us, and in most cases, Accruent. Most are around changes or bugs that break their critical functionality, others are around having a very large amount of custom code that can not easily be upgraded to newer fork points, others are around an external app they have created that interfaces with MC (like our LoginHub, DataHub, API, MCe etc.., do) and requires changes to work with the new version of MC, new details of which not known until Accruent releases their release that fixes this.
- who own their Accruent MC but are not under SMA with Accruent and are are therefor not eligible to receive any upgrade
Our beta of V3.1 was release May 1st 2026 (30 days ahead of the target date in this document.)
This is an 'included at no additional cost' product for customers who already have their MC under SMA through us. For other users with Accruent MC we have options to come to us for SMA.
This also will be bringing soon the benefits of the Desktop App for MC on Mac and Linux.
Accruent, new version no date yet:
Accruent is working on a new version that fixes it. This is going to take them a lot of work to get it done and done correctly.
We will update this page as soon as we get updates from Accruent (last verified 2026.05.01) and when we have a version from them ready for customers that fixes it. We intend to upgrade our SaaSs to this as soon as it is available and tested. This should work on all platforms Accruent MC runs on.
Temporary Solutions.
A browser setting in every user's browser
This solution, according to Chromium, should work until at least Sept 21 2026, and (not according to Chromium) likely until the end of October or November 2026. But you wont' get the other benefits of the "Desktop App for MC"
On an individual browser you can set:
1. Type the following in on the browser URL line. (This works for Chrome and Edge, edge will change the 'chrome;' part to 'edge:')
chrome://flags/#deprecate-unload
2. Choose disable
3. Click on restart
Corporate policy (As in, server/software applied corporate policy)
If you are able to implement a corporate policy that blocks upgrades of Chrome and Edge past versions 145 (so for clarity, do not allow 146 or higher), implementing this will be a good temporary solution that won't require the above for any users that have not yet upgraded. If unable, a corporate policy that sets the flag to Disabled should work for all browsers under corporate policy control until at least October 2026, after which you need at least one of the two permanent solutions.