Why updates break things, and what to do about it
Updating immediately and never updating are both bad policies. The workable version depends on what kind of update it is and how much a failure would cost you.
The advice to always update immediately is given because security patches matter and most people delay far too long. It's directionally right and slightly too simple, because some updates carry real risk of breaking a working setup.
Not all updates are the same thing
Security patches fix specific vulnerabilities, change little else, and are low-risk. Install these promptly. There is essentially no argument for delaying them, and once a vulnerability is public the window to exploit it opens fast.
Minor updates fix bugs and make small changes. Usually safe, occasionally alter behaviour you relied on.
Major version upgrades change architecture, drop support for older hardware or file formats, and redesign interfaces. This is where things break.
Driver updates are their own category. Frequently fix one thing and break another, and are the most common cause of a system that worked yesterday and doesn't today.
Why they break things
Dependency changes. Software sits on layers of other software. An update to one layer can break assumptions another made.
Removed features. Maintaining old functionality costs developer time. When usage falls below some threshold it gets cut, and you find out when you go to use it.
Changed defaults. Your settings may survive while the behaviour around them shifts.
Hardware support dropped. Particularly with operating system upgrades. Older peripherals lose drivers and simply stop working.
Insufficient testing against your configuration. Nobody can test every combination. Unusual setups break more often, which is a reason to be conservative if yours is unusual.
A policy that works
Security updates: immediately. The risk of delay outweighs the risk of breakage.
Minor updates: within a week or two. Long enough that serious problems surface publicly, short enough to stay current.
Major upgrades: wait, deliberately. A few weeks at minimum. Let other people find the problems. Before upgrading, search the version number alongside your specific hardware or the software you depend on — if there's a widespread issue, it'll be immediately visible.
Driver updates: only with a reason. If your hardware works, leave it. Update when you have a specific problem the release notes say is fixed, or when a new application requires it. "Newer is better" is not true for drivers.
Reducing the damage when it goes wrong
- Back up before major upgrades. A full system image if you can. This is the difference between an annoying evening and a lost weekend.
- Know the rollback path before you start. Operating systems usually allow reverting within a limited window. Applications often let you install a previous version, but not always — check first if it matters.
- Don't upgrade before something important. Never the night before a deadline. This is the most reliable rule in the whole article.
- Upgrade one thing at a time. If you update the OS, drivers and three applications together, diagnosing the failure is far harder.
- Read the release notes for major versions. Removed features are usually listed, and it takes two minutes.
The case against never updating
The "it works, leave it alone" instinct is understandable and becomes dangerous over time. Unpatched software accumulates known vulnerabilities, and known means documented publicly with working exploits available. Eventually your version falls out of support entirely and stops receiving fixes at all.
Anything that touches the internet — browser, operating system, anything accepting connections — needs to stay current. An offline machine running old software to drive a specific piece of hardware is a defensible exception. A daily-driver laptop three major versions behind is not.