Get my free Blind Spot ScanCall 513-400-4072
Business

Update Errors, Crashes, and You

June 24, 2021 · Updated November 17, 2026 · 3 min read

In June 2021, an update to the Google app for Android started crashing on phones that installed it. According to 9to5Google’s coverage, after updating to version 12.23 some users saw the app close over and over, and features that depend on it, including Assistant, Lens and the Discover feed, stopped working as well. Google published steps to clear the app’s data as a workaround, then released version 12.24 to fix the crashes.

For most phone owners it was an annoyance that a later update fixed. In a business, the same pattern on laptops, servers or a line-of-business application can stop work. This article explains why updates go wrong and how to manage them so that one bad release does not reach every device at once.

Why do updates break things?

  • The update has a bug that the developer’s testing did not catch, as with the Google app.
  • Your device differs from what the developer tested: older hardware, an unusual driver or a manufacturer’s own modifications.
  • Something else on the device conflicts with it, such as security software, a plug-in or a business application that depends on old behavior.
  • The installation was interrupted by a reboot, a full disk or a dropped connection, leaving it half finished.
  • The hardware is too old for the new version, so the device is either left behind on an old release or struggles after the upgrade.

Why is turning updates off the wrong fix?

After a bad update, it is tempting to switch automatic updates off. That trades an occasional broken update for a permanent security gap. Updates regularly close vulnerabilities that attackers are already using, which is why CISA maintains a Known Exploited Vulnerabilities Catalog. The aim is to control when updates arrive, not to stop them.

How do you manage updates without surprises?

Test on a small group first. Windows Update for Business lets administrators set up deployment rings so updates reach a subset of devices before the rest of the organization, according to Microsoft Learn. Choose a pilot group that covers your common hardware models and the people who use your critical applications.

Delay rather than skip. The same documentation describes deferring updates for a set period, and pausing an update if you discover a problem during deployment so other devices do not install it until the issue is fixed.

Check known issues before approving. Microsoft lists known and resolved issues for each Windows version on its Windows release health page. Find the equivalent release notes or status page for every application you depend on.

Treat security fixes and feature updates differently. Security fixes should move through the pilot group quickly. Feature updates, which change how software looks and works, can wait until you have checked compatibility with your applications and told staff what will change.

Keep a way back. Before a major upgrade, make sure the device’s data is backed up and you know how to uninstall the update. For servers, a snapshot or image taken before patching makes a rollback quick.

Keep an inventory. Knowing which devices run which versions tells you who is affected when a bad update appears, and which older devices can no longer receive updates at all.

Make reporting easy. The first sign of a bad update is often someone saying an app keeps closing. A clear way to report it, and someone who looks for patterns across reports, turns one complaint into a quick pause instead of an office-wide outage.

Do phones and tablets need the same treatment?

The Google app problem happened on phones, which usually update themselves without anyone in IT watching. If staff use phones or tablets for email, scheduling or field work, include them in the plan:

  • enroll company devices in mobile device management so you can see their operating system versions and apply policies
  • keep a list of the business apps people rely on, so you know what to check when a new version misbehaves
  • know how to reinstall or roll back a critical app, and who to call at the vendor

Personal phones used for work need at least a minimum operating system version for access to company email and files, enforced through your email and identity settings.

What to do next

Write down how updates reach your computers today: automatically, by hand, or through a management tool. If every device updates at the same moment, set up a small pilot group and a short delay for everyone else, and check that you could roll back a bad update on a server. Patch management is part of our managed IT services, and you can request a Blind Spot Scan to see which devices are behind on updates.

Find the gaps
before attackers do.

The Blind Spot Scan is a free, no-obligation IT & security assessment from a local engineer. You keep the report either way.

  • Network, firewall & Wi-Fi review
  • Cybersecurity check
  • Backup & recovery test
  • Plain-English report with priorities

Book your free Blind Spot Scan

Prefer to talk? 513-400-4072

CallFree assessment