Check 5 and the Workaround Trap
Where you are: Module 5 — Quick-Win Checks · Lesson 5.3 · Based on Chapter 5 (§5.5–5.6) of Dr. Tahseen Al Doori's Troubleshooting Essentials.
What you'll be able to do
- Carry out Check 5: free storage, pending or recent updates, exhausted resources, and licence or account status.
- Use the book's time table to plan and pace a complete quick-win sweep.
- Distinguish a workaround, a fix and a root cause, with an example of each.
- Decide when a quick win must be followed by a full investigation.
Watch: Check 5 and the Workaround Trap
The video completes the five checks with storage, updates and resources, walks through the book's time table, and then follows a fictional shared PC that "needs a restart every afternoon" until someone recognises the pattern. Keep these questions in mind:
- Which three symptoms does a full disk typically cause?
- Roughly how long does the whole five-check sweep take?
- At what point does a successful quick win become a warning sign?
Check 5: Updates, storage and resources
The fifth check asks four questions:
- Is there enough free storage? The book is clear that a full disk causes crashes, failed saves and slowness. Programs need free space to write files and temporary data, and when there is none they fail in ways that often look unrelated to storage.
- Are updates pending, or did an update install just before the fault began? Pending updates may be needed to fix a known bug. An update that installed just before the fault is a recent change, and recent changes are prime suspects (remember Module 2's question, What changed?). Module 6 shows how to test that suspicion with rollback.
- Are memory or processor resources exhausted? If the system is overloaded, close demanding applications and see whether it recovers. Module 7 introduces the monitoring tools that show which programs are using the most memory and processor time.
- Are the subscription, licence or account still active? Software that suddenly stops working, or drops into a limited mode, may simply have an expired subscription or licence.
Freeing space safely
When the disk is full, the remedy is to free space, but carelessly deleting files can turn a slow computer into a broken one.
Protect data when freeing space. Make sure important files are backed up before anything is removed (the book's principle protect what matters). Use the operating system's own storage tools to see what is using space and to clear temporary files. Never delete files or folders you do not recognise, especially system folders; if in doubt, stop and ask.
The quick-win time table
The book summarises all five checks in one table:
| Check | Typical time | Faults commonly resolved |
|---|---|---|
| Power | 1 minute | Device appears dead; battery flat; strip switched off |
| Connections | 2 minutes | No display, no network, accessory not working |
| Restart | 2–5 minutes | Freezing, slowness, stuck applications, lost connection |
| Settings and input | 2 minutes | Wrong output, muted audio, login failures |
| Updates and resources | 5 minutes | Crashes, slowness, failed saves |
Added together, the typical times come to roughly 12 to 15 minutes for the complete sweep. In practice you stop as soon as one check resolves the fault, then move on to verification and documentation (Steps 6 and 7 of the method). If all five checks pass and the fault remains, they have still done their job: the obvious causes are ruled out, and you move on to isolation (Module 6) knowing that the simple answers have been eliminated.
Use the table in two ways. First, it helps you pace yourself: if you have spent twenty minutes on the power check, something is wrong with your approach. Second, the right-hand column helps you prioritise when a symptom points strongly to one check. "Muted audio" points to settings; "failed saves" points to storage. You still run the checks in order, but you know where to look most carefully.
The workaround trap
Quick wins are so effective that it is easy to stop too early. Chapter 5's key takeaway warns: if a quick win has to be repeated, it is a workaround, not a fix, and the root cause must still be found.
Chapter 12 of the book defines the terms precisely, with examples from a server that keeps stopping:
| Term | Meaning | Book's example |
|---|---|---|
| Symptom | What is observed going wrong | The server stops responding |
| Workaround | A temporary way to keep working | Restarting the server each morning |
| Fix | Correction of the immediate fault | Deleting old files to free disk space |
| Root cause | The underlying reason the fault occurs | Log files grow without limit because log rotation was never configured |
A workaround is not bad. It keeps people working while the real investigation happens, and sometimes it is the right immediate action. The mistake is to treat it as the end of the job. A restart that helps today is useful information; a restart that is needed every day is evidence that the root cause has not been found.
When a quick win needs full investigation
Treat a quick win as a starting point, not a finish, when:
- the same fault returns after the quick win (the book: a fault that keeps returning after a restart needs full investigation);
- the quick win has to be repeated on a schedule, such as every morning or every afternoon;
- the quick win resolves the symptom but you cannot explain why the fault happened.
In each case, record the quick win as a workaround in the ticket and continue with Steps 2 and 3 of the method.
Worked example
(Fictional scenario.) A shared office PC becomes very slow every afternoon.
- Monday: slow by mid-afternoon; a restart helps.
- Tuesday: slow again at the same time; restarted again.
- Wednesday: a technician notices the pattern. The restart is a workaround, not a fix, so the ticket stays open. Theory: one program is steadily consuming more memory the longer it runs (a memory leak), one of the underlying causes the book names.
- Thursday: watching memory use over the day confirms that one program's memory use climbs steadily from the morning. The vendor's release notes mention a fix for exactly this in a newer version; an update is planned and the user is told when it will happen.
- Friday: after the update, there is no slowdown all day. The user confirms. The ticket records the root cause, the update and a note to watch the program's memory use after future updates.
The restarts kept people working; the investigation stopped the problem returning.
Try it
Goal: run Check 5 on your own device without changing anything.
- Find how much free storage your device has and what is using the most space (use the operating system's built-in storage view).
- Find your update history. Note the date of the most recent update and whether any are pending.
- Open your system's resource monitor (for example Task Manager on Windows or Activity Monitor on macOS) and note the two programs using the most memory.
- Check whether any software you rely on has a subscription or licence with an expiry date.
- Do not delete files, uninstall updates or end processes you do not recognise.
You have finished when you have recorded all four results and can say whether your device would pass Check 5.
Knowledge check
According to the book, which set of symptoms is typically caused by a full disk?
Using the book's time table, which check typically takes the longest?
A server stops responding every few days, and the team restarts it each time. In the book's terms, the restart is:
A shared laptop has to be restarted every morning before it works properly. What should you do?
Answers explained
- A. The book links a full disk to crashes, failed saves and slowness. The other options match connections, settings and power faults respectively.
- D. Updates and resources is listed at about 5 minutes; a restart is 2–5 minutes, and the others take 1–2 minutes.
- B. Restarting keeps the service running temporarily but has to be repeated, so it is a workaround. The symptom is the server stopping; the root cause is still unknown.
- C. A quick win that must be repeated is a workaround, and the root cause must still be found. Closing the ticket ignores the evidence; replacing the laptop is a guess; sleep preserves the faulty state.
Key takeaways
- Check 5 asks about free storage, recent or pending updates, exhausted resources and licence or account status.
- Free disk space safely: back up first, use built-in tools, never delete what you do not recognise.
- The full sweep takes roughly 12 to 15 minutes; stop when a check resolves the fault, otherwise move on to isolation.
- If a quick win has to be repeated, it is a workaround, not a fix: keep investigating the root cause.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), §5.5–5.6, Chapter 5 Key Takeaway and Summary (with cross-references to §2.2, §2.3 and §12.1)
