● A free public tool  ·  Built by Poptani Labs  ·  No sign-up  ·  Your data never leaves your browser
The Practical Lab · 5-minute read

Why 'turn it off and on again' actually works (and when it doesn't)

A round power button on an old Apple keyboard
Image: 'Apple M0116 power button.jpg' by Daniel beardsmore, Public domain, via Wikimedia Commons

Every IT support conversation seems to start the same way: have you tried turning it off and on again? It sounds like a brush-off, the tech-world equivalent of "have you tried not being ill?" But it is usually the first suggestion for a good reason — it fixes a surprisingly large class of problems, and the reason it works has nothing to do with magic. This is a research-based guide, not a hands-on test, drawn from the sources below. Save any open work before you restart anything.

What a restart actually clears

A computer's troubles are often not broken parts but broken states. A program can leak memory, grabbing RAM and never giving it back, so the machine slowly grinds as the pool drains. A process can get stuck waiting for an event that never arrives. A driver — the software between the operating system and hardware like Wi-Fi adapters, graphics cards and printers — can stop responding correctly, and closing the app that triggered it does not reload the driver. A restart ends all of it at once: RAM is flushed, every process is stopped, drivers are reloaded from scratch, and the network stack is rebuilt. Instead of asking a confused system to repair itself, you hand it a known-good starting point and let it build its state again.

Why shutdown is not the same thing

Here is the catch that trips up Windows users. Since Windows 10, a feature called Fast Startup means clicking Shut Down does not fully close everything down: Windows closes your apps and logs you out, but saves a snapshot of the kernel and drivers to disk, like a form of hibernation, and restores it at the next boot. That makes startup fast — but it also reloads whatever driver glitch or leaked state was in that snapshot. Restart, by contrast, bypasses Fast Startup entirely and performs a full boot cycle. If your PC is misbehaving after sleep or hibernation, or a device has stopped working, Restart is the option that actually starts clean. On a phone or a Mac the details differ, but the principle is the same: a true restart, not a nap, is what resets the state.

What a restart cannot fix

A restart is a reset of temporary state, not a repair. It will not fix a failing SSD or faulty RAM, replace a damaged cable, undo corrupted files, remove malware, or correct a bug that happens every time you run the same software. It also will not fix a settings problem — if the configuration itself is wrong, the machine will faithfully rebuild the same wrong state after every reboot. The diagnostic rule is simple: if a restart fixes it once and it never returns, it was a temporary state problem. If it returns after every restart, something underneath is broken, and the real fix is an update, a driver reinstall, a hardware check, or a malware scan. Restart first, by all means — but if you find yourself restarting daily, stop treating the symptom and go looking for the cause.

The first actual bug

Computing even has a literal version of this story. On September 9, 1947, operators of the Harvard Mark II, an electromechanical calculator built for the US Navy, traced a fault to Relay #70 in Panel F. Wedged between the relay contacts was a moth. They removed it with tweezers, taped it into the logbook, and wrote: "First actual case of bug being found." The logbook, moth still attached, is now in the Smithsonian's National Museum of American History. Two corrections keep the story honest: the word "bug" for an engineering fault predates the moth by decades — Thomas Edison used it in 1878 — which is exactly why the logbook joke lands; and Grace Hopper, who retold the story for the rest of her career, was not the person who found the insect. Sometimes the problem really is a bug. Most of the time, it is just a state — and a restart is the cheapest way to clear it.

Try This

Next time something on your computer misbehaves, try a real Restart before anything else — and save your work first. If the problem vanishes, it was state, and you are done. If it comes back after every restart, that is your signal to stop restarting and start investigating: updates, drivers, hardware, or a scan, in that order.

Related on Poptani Labs: The 3-2-1 backup rule: the simplest way to never lose your files, How to run AI locally on your computer, How a website actually works: from typed address to page on your screen. More in this category: The Practical Lab.

Sources: Syntech, why restarting matters and how Fast Startup differs; Why restarting fixes so many problems; Make Tech Easier, the first literal computer bug

← All posts