NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Module 5 — Quick-Win ChecksLesson 2 of 4
Video lesson

Checks 3 and 4: Restart, Settings and Input

BeginnerVideo lesson
9 min readBeginner

Where you are: Module 5 — Quick-Win Checks · Lesson 5.2 · Based on Chapter 5 (§5.3–5.4, §5.6) of Dr. Tahseen Al Doori's Troubleshooting Essentials.

What you'll be able to do

  • Restart at the right level (application, device, network equipment) and power-cycle network equipment in the book's order.
  • Explain the four things a restart does that resolve transient faults, and its key limitation.
  • Carry out the settings and input check (Check 4), including selection, mute, Caps Lock, date and time, and account status.
  • Explain why an incorrect system clock causes login and secure-website errors.

Watch: Checks 3 and 4: Restart, Settings and Input

The video follows a fictional finance user whose laptop has a frozen video-call app, silent calls and a payroll website that refuses to sign them in. Three symptoms turn out to have three simple causes. As you watch, ask yourself:

  • Why does the book specify a full restart rather than sleep?
  • In what order should a modem and router be power-cycled, and why?
  • How could a wrong clock stop someone signing in?

Check 3: Restart

Save work before any restart. A restart closes every open program. Always ask the user first and give them time to save their documents. A quick win that loses someone's unsaved work has created a new problem.

The book describes three levels of restart. Start with the smallest that could help and move up only if it does not:

  1. Close and reopen the application. If only one program is misbehaving, this may be enough, and nothing else is disturbed.
  2. Restart the device fully. The book is specific: a restart, not sleep or hibernation. Sleep and hibernation are designed to preserve the system's current state so that you can carry on where you left off, which is exactly the state you are trying to clear.
  3. For network faults, power-cycle the network equipment in order. To power-cycle a device means to turn it fully off, wait, and turn it back on.

The power-cycle order

ModemWait 60 secondsRouterEnd device

The modem is the box that connects the premises to the internet service provider. The router shares that connection with the devices on the local network, and the end device is the laptop, phone or PC. Each device depends on the one before it, so each is brought up only once the one it depends on is ready. Restarting the router before the modem has finished reconnecting, for example, may leave the router without a working connection to share.

Beyond the book (2026 note): On Windows, "Shut down" and "Restart" are not the same. Microsoft documents that fast startup is the default when a shutdown is requested: the user is signed out, but the kernel's state is saved to disk and restored at the next start. A full shutdown happens when a restart is requested. So when a quick win calls for a full restart on Windows, choose Restart rather than Shut down and power on. Source: Microsoft Learn — System power states.

Why restarting works

The book gives four reasons a restart resolves so many faults:

1

Clears temporary memory

Leftover data and errors held in memory are wiped.

2

Ends stuck processes

Programs and background tasks that have frozen are stopped.

3

Reloads drivers and configuration

Device drivers and settings are loaded fresh.

4

Re-establishes network connections

Links to networks and online services are rebuilt.

Together these resolve many transient faults: problems caused by the system's current state rather than by a permanent defect.

But the book draws a firm line: a restart treats the symptom rather than the cause. If the same problem needs restarting again and again, the troubleshooter must continue and find the underlying cause, such as a memory leak (a program that keeps claiming memory and never releases it), a failing driver or an overheating component. Lesson 5.3 returns to this as "the workaround trap".

Check 4: Settings and input

Many faults are simply something set or selected wrongly. The book's questions:

  • Is the correct input, output, account, printer or display selected? A projector on the wrong input source looks exactly like a broken projector; a document sent to the wrong printer looks like a printing failure.
  • Are volume, brightness, mute and Caps Lock set correctly? A muted application, a screen at zero brightness or Caps Lock left on (which makes passwords fail) are among the most common "faults" reported.
  • Are the date and time correct? The book notes that incorrect clocks break logins and secure websites.
  • Has the password expired or the account been locked? Account problems are covered further in Module 10. Remember the book's security rule: never ask users to tell you their password.

Why a wrong clock breaks logins and websites

The book states the effect; here is the reasoning behind it.

Beyond the book (2026 note): Secure websites prove their identity with a digital certificate, and the certificate standard defines a validity period between a start date (notBefore) and an end date (notAfter) (RFC 5280, §4.1.2.5). If a computer's clock is far enough out, a valid certificate appears not yet valid or already expired, and the browser refuses the connection. Sign-in systems also use timestamps: in Windows domains, Kerberos authentication tolerates only a set difference between the computer's clock and the domain controller's, five minutes by default (Microsoft Learn — Maximum tolerance for computer clock synchronization).

Worked example

(Fictional scenario.) At 10:40 on Wednesday a finance user reports that their laptop "is broken". Their video-call app freezes, they cannot hear colleagues on calls, and the payroll website will not sign them in. They close the lid every night, so the laptop has not restarted for weeks. They returned from a trip abroad on Monday.

TimeStepWhat happened
10:45TestThe user saves their work; the app is closed and reopened. Still frozen.
10:50ImplementA full restart (the first in weeks). The app now runs smoothly.
10:55TestCalls are silent: the laptop's speakers, not the headset, are selected as the output device. Corrected.
10:57TheoryWhile abroad, the user changed the clock by hand instead of the time zone; the time is now hours wrong.
11:00VerifyTime corrected and set to update automatically; payroll sign-in works. The user confirms all three problems are gone.
11:05DocumentThe ticket records three causes and fixes, and advises restarting regularly. If the freezing returns, it will be investigated rather than restarted again.

Notice that three separate complaints were treated as three separate problems, each tested on its own, in keeping with the principle change one thing at a time.

Try it

Goal: practise Checks 3 and 4 safely on your own device.

  1. Save and close all your work first.
  2. Find where your operating system offers Restart and note how it differs from Sleep (and, on Windows, from Shut down).
  3. Open your sound settings and identify where the output and input devices are selected. Note which device is currently chosen.
  4. Find your date and time settings. Is the time set automatically? Is the time zone correct?
  5. Write a one-paragraph explanation, in your own words, of why a wrong clock can stop someone signing in.

Do not change network equipment that others are using, and do not change account or password settings.

You have finished when you can show where each setting lives on your device and have written your clock explanation.

Knowledge check

According to the book, what is the correct order for power-cycling network equipment?

Which of these is NOT one of the four things a restart does, according to the book?

A user's password is rejected on one device only, and you notice the keyboard's Caps Lock light is on. Which quick-win check does this belong to?

A shared laptop works properly only after a restart, and needs one almost every day. What does the book say this means?

Answers explained

  1. C. The modem comes up first, is given 60 seconds, then the router, then the end device, each after the one it depends on. The other orders start a device before what it depends on is ready.
  2. B. A restart clears memory, ends stuck processes, reloads drivers and configuration and reconnects to networks. It cannot replace failing hardware; a failing component is a possible underlying cause that a restart only masks.
  3. A. Caps Lock is listed explicitly under settings and input. It has nothing to do with cables, a restart or resources.
  4. D. Repeated restarts treat the symptom. The book names possible underlying causes such as a memory leak, a failing driver or overheating. Sleep would preserve the faulty state, and nothing suggests user error.

Key takeaways

  • Save work first, then restart at the smallest level that might help: application, device, network equipment.
  • Power-cycle in order: modem, wait 60 seconds, router, then the end device.
  • A restart clears memory, ends stuck processes, reloads drivers and reconnects, but it treats the symptom, not the cause.
  • Check 4 asks whether the right things are selected and set, including mute, Caps Lock, the clock and the account.

Sources