What to check before a software update

An update notification can arrive at an inconvenient moment, which makes two poor responses tempting: install without looking, or postpone indefinitely. A short preparation routine can preserve the security value of timely updates while reducing avoidable surprises.

CISA advises users not to delay software updates because they can fix security flaws. The checklist here adds planning context; it does not override urgent provider notices, workplace policy, or instructions for a managed device.

Confirm where the update came from

Open the device or application’s own settings rather than following a link in an unexpected email, message, or advertisement. Check that the product name and version are the ones you use. For a work device, the update may be controlled by an administrator, and a personal installation could interfere with that process.

Read the provider’s release or support note when the update affects an essential application, accessory, or file format. Focus on supported devices, known prerequisites, and changes that affect your workflow. A social-media post about another model is not a substitute for the documentation for yours.

Protect the current state

Save open work, close active transactions, and allow enough time for restarts. Check that the relevant backup process has completed and that you know how to restore a small test file. A backup icon by itself does not establish that every location is covered.

Make sure the device has the power, storage, and stable connection specified by the provider. Do not free space by deleting material you have not backed up. On a portable device, use a trusted power source and avoid beginning an installation immediately before travel or a critical call.

Understand dependencies

List the few things that must still work afterward: perhaps a printer, security tool, assistive technology, or work application. Check current compatibility information when the provider publishes it. This is especially useful for a major operating-system change rather than a routine patch.

If the device controls safety-sensitive equipment or is managed by an organization, follow the responsible operator’s process. General consumer guidance is not enough for medical, industrial, or regulated systems.

Know the recovery route

Find the official support page before the installation, not after a problem occurs. Record the model, current version, update name, and time. If the provider offers a rollback or recovery procedure, understand its limits. Do not assume every update can be reversed without data loss.

After installation, check the essential tasks you listed. Confirm that security tools are active and that pending updates have finished rather than repeatedly restarting the device in the middle of a process.

Avoid turning caution into permanent delay

A checklist should make action clearer, not create an excuse to ignore security maintenance. For ordinary supported devices, automatic updates can reduce long gaps. CISA’s software update guidance emphasizes installing updates promptly and using automatic updates where practical.

Keep the record brief: date, version, successful restart, and any issue that needs follow-up. That is enough to distinguish a completed update from a notification you merely dismissed.

Source and scope

Security context is drawn from CISA Secure Our World. Always use the current documentation supplied by the software or device provider for installation and recovery steps.