[transreal]

This is the trouble with Google's aggressive auto-update policy. "Everyone is always on the latest" is mandated because everyone should have the latest security updates, but it works great except when it doesn't.

Another example is a recent issue where a Chrome update broke WebView based Android apps and stopped them from being able to make certain types of network requests. It was fixed in 2 weeks, but that 2 week period was full of unhappy customers and lost revenue.

I'm hoping the upcoming Chromium based Edge from Microsoft will allow IT Admins to control when a browser update is rolled out and give them more control over the update process.

Chrome auto-updates can be disabled for networks behind a firewall by blocking the update server address, but that's a very crude way, and doesn't allow for updating a test machine to see how the new version works, or updating to the latest minus 1 version.

[senderista]

This is not about auto-updates. Organizations which had disabled auto-updates were still affected. In this case Google changed Chrome behavior without changing the release version. That’s absolutely unacceptable.

[mimsee]

Couldn’t one setup to use Chrome Enterprise with group plolicy rules on when certain updates can happen?

[isostatic]

You could whitelist the test machine