Learn Understand first, then practice while the concept is still fresh.

M49 - System Updates & Patching

Explain a safe update workflow for Windows and Linux, apply updates deliberately, and verify whether a reboot is still required afterward.

SysAdmin

System Updates & Patching

Explain a safe update workflow for Windows and Linux, apply updates deliberately, and verify whether a reboot is still required afterward.

30 min BEGINNER BOTH Curriculum-reviewed
Prerequisites
Module M37 - Package Management: CLI
What you should be able to do after this
  • Explain a safe update workflow for Windows and Linux, apply updates deliberately, and verify whether a reboot is still required afterward.

Updates Are Operational Work, Not Just Button Clicking

Applying updates is not only about “being current.” It is about reducing risk while preserving stability.

A useful update workflow usually includes:

  1. understand what environment you are updating
  2. install updates deliberately
  3. verify the result
  4. confirm whether a reboot or service restart is still needed

That is true on both Windows and Linux.

1. Prepare Before You Patch

The exact process depends on the system, but good habits are broadly consistent:

  • know whether the machine is personal, lab, or production-like
  • understand whether a reboot window is acceptable
  • make sure important work is saved or backed up
  • if possible, test first on a less critical machine

The more important the system, the more important this preparation becomes.

2. Windows Update Thinking

Windows systems are commonly updated through the built-in Windows Update workflow, and managed environments may add centralized tooling on top of that.

For learning purposes, the key questions are:

  • what updates were installed?
  • when was the system last patched?
  • does the machine still need a restart?
Inspect installed hotfixes

Get-HotFix | Select-Object -First 10

This is not the whole enterprise patching story, but it is a useful way to inspect recent update state from PowerShell.

Linux package managers expose update steps directly through the terminal.

3. Linux Update Workflow

On Debian- and Ubuntu-style systems, package management and operating-system updates are closely related.

On Windows, the same caution applies: install, then verify.

Typical Linux patching flow

sudo apt update sudo apt upgrade sudo apt autoremove

When major dependency or package replacement changes are involved, some systems may require a fuller upgrade path. The main learning point is to understand the difference between refreshing package metadata, applying updates, and cleaning no-longer-needed packages.

4. Reboot and Verification

Installing updates is not the end of the job.

You still need to know:

  • did the update complete successfully?
  • are critical services healthy?
  • is a reboot still pending?

On Linux, one common indicator is:

Check whether a reboot is required

cat /var/run/reboot-required

If the file does not exist, the command may report that fact, which itself is useful information.

On both platforms, checking service state after updates is often as important as applying the updates in the first place.

Patch Predictably

The strongest update habit is not “patch instantly no matter what.” It is “patch deliberately, then verify.” A rushed update without verification can create a different kind of outage.

What You Just Learned

  • Safe patching includes preparation, installation, verification, and reboot awareness.
  • Windows and Linux expose update state differently, but the operational questions are similar.
  • Get-HotFix can help you inspect installed update information on Windows.
  • apt update and apt upgrade play different roles on Linux.
  • Reboot requirement and service health should be checked after updates, not assumed.

Next, the curriculum moves into more advanced remote-access and administration workflows.