NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Module 10 — Operating System, Software and Account TroubleshootingLesson 4 of 4
6 min readBeginner

Where you are: Module 10 — Operating System, Software and Account Troubleshooting · Checkpoint · Based on Chapter 10 of Dr. Tahseen Al Doori's Troubleshooting Essentials.

Recap

Software faults follow a sequence from the simplest action to the most disruptive: record the exact error, restart, isolate (one file, one user or all), update, clear caches, disable add-ons and test in safe mode, back up then repair or reinstall, and search the vendor's knowledge base. For web applications, a private window, a different browser, a site-specific cache clear and the status page separate browser faults from website faults. When a fault follows an update, roll back the smallest thing that works, report it to the vendor and pause that update only until a fix arrives; never leave a system permanently unpatched. Login faults usually come from Caps Lock, layout, lockouts, expiry, saved credentials or the clock. Never ask for or share a password. Malware is a security incident: isolate, do not pay or interact, escalate.

Knowledge check

An application crashes on start for every user of one computer, but works on other computers. Which step is most likely to find the cause quickly?

An online timesheet fails in Chrome and Edge, on several computers, for everyone. What does this suggest?

After an overnight update, a laptop's Wi-Fi adapter disappears from the system. What does the book recommend first?

A user's account is locked after many failed attempts. What is the correct action?

A computer shows constant pop-ups, a new unknown program and disabled security software. A ransom message has not appeared. What should you do?

Lab: Triage five tickets (simulated)

Goal. Apply everything in Chapter 10 to five fictional tickets: decide the most likely cause, the first safe action, the next steps in the book's order, and whether to escalate.

Safe setup. This is a paper exercise. Do not try any of the actions on your own device or a production system. No real accounts, passwords or malware are involved.

The tickets (all fictional).

TicketReport
T1"The photo editor closes every time I open one particular image. Other images are fine."
T2"The college portal shows a blank page in my usual browser. My friend says it works for her."
T3"Since this morning's update, my laptop restarts whenever I connect the docking station."
T4"My new password works on the website but my email app on my laptop keeps saying it's wrong."
T5"A window says my files are locked and gives a countdown to pay. Should I click 'Decrypt'?"

Steps.

  1. For each ticket, write a one-sentence problem statement using the Chapter 4 template as far as the information allows.
  2. Name the category and the most likely cause from Chapter 10.
  3. Write the first safe action and the next two steps in the book's order.
  4. State any safety or security rule that applies (data backup, passwords, permissions, malware).
  5. Decide: resolve at your level, or escalate, with a reason.

What to record. A table with columns: Ticket · Problem statement · Likely cause · First action · Next two steps · Rule that applies · Resolve or escalate (why).

Completion criteria. All five tickets are completed; every first action is safe and reversible; T5 is isolated and escalated with no interaction with the message; no row asks for or uses a password; T3 includes a report to the vendor and a temporary pause rather than permanent switch-off.

Answers explained

  1. a — every user on one computer, but not other computers, points to that installation; safe mode with add-ons disabled tests the most common cause, while passwords, the monitor and vendor outages do not fit.
  2. c — failing in every browser, on every computer, for everyone rules out one user's extensions, one laptop's cache and keyboard layout; check the service's status page and the network.
  3. b — a sudden fault straight after an update calls for rollback and a report to the vendor; permanent switch-off is forbidden, reinstalling everything is excessive, and DNS is unrelated.
  4. d — the book's action for a lockout is to wait or ask an administrator; more guessing extends the lockout, passwords are never requested, and new accounts bypass policy.
  5. a — several malware symptoms together, especially disabled security software, are a security incident; waiting, weakening protection or paying for unknown tools all make it worse.

Lab check. T1: one file only, so suspect the file; open a copy or earlier version, then update the application. T2: works for others, so test a private window and a different browser, then clear that site's cache; resolve. T3: update-related driver fault; roll back the dock or display driver (or uninstall the update), report to the vendor, pause briefly per policy, install the corrected version later. T4: saved old credentials in the email app; the user updates the saved password themselves, no password is shared; resolve. T5: ransomware; do not click anything, disconnect from the network, report to IT security immediately; escalate.

Sources

  • Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), Chapter 10 (§10.1–10.5, Security Reminder, Review Questions); §4.6 (problem statement template); §13.1 (escalation triggers)