Windows Update & Driver Troubleshooting

Windows 11 Troubleshooting & Administration

Chapter 7 · Windows Update & Driver Troubleshooting

Windows 11 Fundamentals 8 covered how updates and Storage Sense normally behave; this chapter covers what to do when an update fails outright, plus Device Manager — a tool Course 1 never opened at all.

SFC and DISM — Repairing Corrupted System Files

System File Checker (sfc /scannow) checks protected system files against a local reference copy and repairs any that don't match. But that local reference copy lives in the exact same WinSxS component store already introduced in Windows 11 Fundamentals 8's own Disk Cleanup material — and if the store itself is damaged, SFC has nothing healthy left to repair from.

# The real recommended order: repair the source SFC relies on first DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow

DISM's /RestoreHealth pulls replacement components directly from Windows Update (or a specified source) to repair the WinSxS store itself — the deeper fix, run first, so that SFC's own subsequent pass has a genuinely healthy source to repair from.

	What it actually checks	Repair source
SFC	Individual protected system files against a local reference copy	The local WinSxS component store
DISM /RestoreHealth	The WinSxS component store itself	Windows Update, or a specified alternate source

The Windows Update Troubleshooter — What It Actually Resets

Settings > System > Troubleshoot > Other troubleshooters > Windows Update runs an automated sequence that restarts the Windows Update-related services, clears the update cache, and resets several related components to their default state. It's a genuinely reasonable first step precisely because it's low-risk and quick — but it isn't a targeted fix for any specific cause, and running it repeatedly against an update failure it isn't actually addressing accomplishes nothing beyond resetting components that were never the problem.

Device Manager & Driver Error Codes

A yellow warning triangle over a device in Device Manager indicates a real problem, expandable into a specific numbered Code (Code 43, for instance, meaning Windows has stopped the device because it reported a problem) via that device's own Properties > General tab. Updating a driver offers "Search automatically" (checks Windows Update and locally cached drivers) or "Browse my computer" (pointing directly at a manufacturer-downloaded driver package) — the second option genuinely necessary whenever a manufacturer's own driver is newer or more specific than what Windows Update offers.

Driver Rollback — a Real, Time-Limited Option

A device's Properties > Driver tab includes "Roll Back Driver" — reverting to whichever version was in place immediately before the most recent update. This only works because Windows keeps exactly one previous driver package on hand for that purpose.

A grayed-out "Roll Back Driver" button doesn't mean there's no problem

The button is disabled whenever no previous driver package is stored — either because the current driver is the first ever installed for that device, or because a second update has since replaced the one rollback would have restored, or because a cleanup pass (including the Disk Cleanup material from Windows 11 Fundamentals 8) removed the stored copy. A grayed-out button means "no backup available to restore," not "everything is fine" — the real fix at that point is downloading and manually reinstalling a known-good driver version directly from the manufacturer.

The troubleshooter as a quick first pass, not a diagnosis

Running the Windows Update troubleshooter before digging into logs or manual fixes is reasonable — but if it reports "no problems found" and the update still fails, that's real information too: whatever's wrong likely needs SFC/DISM, a specific error-code lookup, or a manual update download, not another troubleshooter pass.

Hands-On Exercises

Exercise 1

Running sfc /scannow reports errors it "could not fix." Using this chapter's own explanation, describe the likely underlying cause and the correct next command to run.

📄 View solution

Exercise 2

A user updated a graphics driver two weeks ago, and it's been causing crashes ever since — but "Roll Back Driver" is grayed out. Using this chapter's own warn-box, explain why, and what the real fix is.

📄 View solution

Exercise 3

Explain why running the Windows Update troubleshooter three times in a row, with no change in the update's own failure, isn't a productive next step.

📄 View solution

Chapter 7 Quick Reference

DISM /RestoreHealth first, then SFC — SFC's own repair source (the WinSxS store) needs to be healthy before it can fix anything
The Windows Update troubleshooter resets components — a reasonable first pass, not a targeted diagnosis
Device Manager's numbered Code errors (e.g. Code 43) are specific and lookupable
"Roll Back Driver" only works because exactly one previous driver package is kept — grayed out means no backup exists, not that everything's fine
A grayed-out rollback button means a manual manufacturer-driver reinstall is the real fix
Next chapter: Networking Troubleshooting