Capstone: Diagnosing a Real Multi-Symptom Windows Issue

Windows 11 Fundamentals 12 set up a real workstation for "Priya," a freelance developer, and closed with an honest scope note: "no domain join, no Group Policy, no centrally managed update rings, no deep Registry work." Nine chapters later, this capstone returns to that exact same machine, some months on, now showing four real, simultaneous symptoms — and delivers on every one of those named gaps in turn.

The Symptoms, Reported Together

• The machine has been noticeably sluggish most afternoons.
• Priya's database client crashes several times a week, always suddenly.
• Her nightly project-backup task hasn't actually run in over a week.
• This morning, right after a Windows Update, the machine blue-screened on boot.

Four symptoms, investigated one at a time — but, as the investigation shows, not entirely unrelated.

Step 1 — The Afternoon Slowdown (Chapters 1 & 3)

Task Manager's Performance tab shows Disk at a sustained 100% active time each afternoon, with throughput only a few hundred KB/s — Chapter 3's own named misreading pattern. Resource Monitor's Disk tab, sorted by IOPS rather than raw throughput, identifies the database client itself issuing a huge volume of tiny read requests, PID noted for the next step.

Step 2 — The Crashing Database Client (Chapters 2 & 4)

Cross-referencing that PID and timestamp in Event Viewer, the client's own branch under Applications and Services Logs shows repeated Error-level entries — the same Source and Event ID each time — describing a failed read against a local cache file. Following that Source into the Registry (Chapter 4) turns up a corrupted value under the client's own HKCU branch, left behind by a bad update months earlier — no Settings or Control Panel equivalent exists for it at all, exactly the "no GUI" case Chapter 1's own four-layer table described. The key is exported first, then the value corrected directly.

Step 3 — Ruling Out Memory (Chapter 3, Revisited)

Before concluding the disk activity is the whole story, Resource Monitor's Memory tab is checked: Hard Faults/sec sit near zero throughout the afternoon slowdown, ruling out memory pressure as a contributing factor — the disk I/O from the corrupted-cache retries really is the whole explanation.

Step 4 — The Missing Backup Runs (Chapter 6)

Task Scheduler's History (enabled proactively, per Chapter 6's own tip-box, when the machine was first set up) shows the backup task being skipped every evening rather than failing — the exact "silently skipped, not failed" pattern that chapter warned about. Its Conditions tab confirms an "only start if on AC power" setting, and Priya has been working from the sofa on battery most evenings lately. The condition is removed.

Step 5 — The Local Policy Surprise (Chapter 5)

A well-meaning "optimization" utility Priya tried months ago turns out to have set a Local Group Policy value disabling a background service the backup task quietly depends on. gpresult /h confirms it directly by name — this machine was never domain-joined, so nothing here is overridden by a higher-precedence domain GPO; the local setting really is the final word, and reverting it in gpedit.msc resolves it for good.

Step 6 — This Morning's BSOD (Chapters 7 & 9)

The Blue Screen's Stop Code points at a display driver. Device Manager confirms a yellow warning triangle on the graphics adapter with a Code error, dated to right after this morning's update. "Roll Back Driver" is available this time — the update was recent enough that Windows still has the previous driver package stored — and rolling it back resolves the boot failure. WinRE launched automatically after the failed boot attempts; Safe Mode, tested first, confirmed the problem was driver-related rather than a deeper System file issue, before the rollback was even attempted.

Hands-On Exercises