Everyday Use
What Updates Actually Change
Security fixes, features and changes you did not want arrive through the same mechanism. How to tell them apart, and when postponing is reasonable.
Updates can change background processes and usage patterns; on managed work computers, Monitask explains the separate idea of PC activity tracking in further details.
Updates get postponed because they are disruptive and because people cannot tell which ones matter. They are not all the same thing, and the differences determine how urgent each one is.
The kinds of update
Security updates
Fixing flaws that allow a machine to be compromised.
These are the ones that matter, and they are frequently bundled with everything else, which is part of why people postpone them.
Why they are urgent: once a flaw is patched, its details become public. Attackers read the patches to find out what was fixed, and then target machines that have not applied it. The window between a patch being released and being widely exploited is short, which makes "I'll do it next month" a genuine exposure rather than a preference.
Bug fixes
Correcting things that do not work as intended. Low risk, occasionally important if you are affected.
Feature updates
New functionality, and where most of the disruption comes from — changed interfaces, moved settings, new defaults.
These are the ones worth postponing briefly to let problems surface.
Driver and firmware updates
Fixing hardware behaviour, and occasionally fixing security flaws below the operating system.
Firmware for a router is the most commonly neglected update in a household and one of the more consequential. See your home network.
Definition updates
For security software — new signatures for new threats. Frequent, small, and there is no reason to delay them.
Why updates sometimes break things
Understanding this makes the trade-off clearer.
A change in the system can break an application that depended on the previous behaviour.
A driver update can be worse than the one it replaced, particularly for older hardware.
Feature changes remove or move things people relied on.
Disk space and interrupted installs cause their own problems.
The failures are real and they are much rarer than the discussion suggests. The visible cases are the ones that go wrong; the silent majority apply and work.
A reasonable position
Not "always immediately" and not "never".
Security updates: apply promptly. Within days. The exposure is real and it grows.
Definition updates: automatic, always.
Feature updates: wait a week or two if you can, and let problems surface. Then apply. Do not defer indefinitely, because security fixes eventually arrive only in newer versions.
Driver updates: only when there is a reason — a fault, a new device, a known fix. Do not update drivers that are working.
Firmware: when released, particularly for routers, and read the notes first.
Major version upgrades: after checking that the software you depend on supports the new version.
Reducing the disruption
Choose when they install. Both major systems allow active hours, so restarts do not arrive mid-task.
Do not postpone repeatedly. Postponing until the system forces it produces exactly the disruption you were avoiding, at a worse moment.
Back up before a major upgrade. Not before every update — before the ones that change the system version. See cloud storage and backup.
Leave space. Updates need room and a full drive causes failures.
Do not interrupt one in progress. An update stopped mid-way is one of the few reliable ways to genuinely break an installation. If it appears stuck, check whether the drive light is active before concluding anything. See restarting and rebooting.
When an update causes a problem
Establish that it was the update. Did the problem start immediately afterwards, and does it recur?
Roll back, which both systems support for a limited period after a major update.
Roll back a driver specifically, which is separate and frequently the actual culprit.
Check whether the application needs its own update to work with the new system version.
Report it. Feedback mechanisms exist and they do influence fixes.
Do not disable updates permanently because one caused a problem. That trades a temporary irritation for a permanent exposure.
When updates stop
The device has reached the end of its support period, which is the deadline that matters more than any performance consideration.
A machine no longer receiving security updates should not be used for banking, email or anything sensitive, however well it runs. See when a device stops receiving updates.
Check whether your applications have stopped too. A browser that no longer updates on your system is the most exposed thing on the machine.
Reading the release notes
Worth two minutes before a significant update.
Security fixes are usually listed with severity, and a critical one is a reason to apply promptly rather than wait.
Known issues tell you whether your hardware or software is affected.
Changes to features warn you about what will move.
Manufacturers publish these, and almost nobody reads them.
The short version
Security updates are the ones that matter, and the window between a patch and its exploitation is short.
Feature updates are worth delaying a week or two — and not indefinitely, because security fixes eventually arrive only in newer versions.
Do not update drivers that are working.
Router firmware is the most neglected update in a household and one of the more consequential.
And never interrupt an update in progress — that is one of the few reliable ways to actually break a system.
For broader technical standards and computing references, see NIST Information Technology Laboratory.