Restarting, Shutting Down and Rebooting: What Each One Does

"Have you tried turning it off and on again" is a joke because it works. What it does, and why it works, is worth understanding — because the four ways of turning a computer off are not equivalent, and the wrong one sometimes fixes nothing.

The four options

Restart — the system closes everything, shuts down, and starts again immediately. A complete fresh start.

Shut down — on modern Windows, this is not a full shutdown. Fast Startup saves part of the system state to disk so the machine starts faster next time. Which means shutting down and turning on again can leave the same problem in place, while a restart clears it.

This surprises people, and it is why "I already turned it off" does not always count.

Sleep or hibernate — everything stays where it was, in memory or saved to disk. Nothing is cleared. Useful for convenience, useless for fixing anything.

Hard reset — holding the power button or pulling the plug. Cuts power immediately with nothing saved. A last resort, and it carries a small risk of file corruption if the machine was writing at the time.

The practical rule: when something is wrong, restart. Not shut down, not sleep.

Why restarting fixes things

Not magic, and the reasons are specific.

Memory is cleared. Programs that leaked memory release it. Anything stuck in a bad state is gone.

Processes are killed. A background process consuming the processor or holding a file open stops existing.

Temporary state resets. Network connections, device handles, caches — all rebuilt from scratch.

Pending updates complete. Many updates only finish applying during a restart, which is why the machine asks.

Drivers reload. A device that has stopped responding gets reinitialised.

What it does not fix: a hardware fault, a corrupted file, a full disk, a failing drive, or malware. If restarting fixes something and it comes back within hours, the restart is treating a symptom.

Does restarting delete anything?

No. Saved files are on the drive and a restart does not touch them.

What you can lose is unsaved work. Anything typed and not saved lives in memory, and memory is cleared. Most applications now recover unsaved documents automatically, and it is not guaranteed.

Photos, documents and downloads are not affected. This is a common worry and it is unfounded.

The exceptions:

A hard reset while the machine is writing can corrupt the file being written. Rare, and it is the reason to prefer a proper restart.

A reset that is not a restart. "Reset this PC" in Windows is a reinstall, not a restart, and it can remove your files depending on the option chosen. The wording is unfortunate and people confuse them.

Some public or managed computers are configured to wipe changes on restart. If you are on a shared machine, save to a drive of your own.

Restarting safely

Close applications first, or at least save. The system will usually prompt, and applications occasionally block the shutdown waiting for a response you never see.

Let it finish. A restart that appears stuck at a spinning indicator is frequently applying updates. Give it time — updates can take a long time on an older machine, and interrupting mid-update is one of the few ways to genuinely break an installation.

How long is too long? If the drive activity light is still flickering, it is doing something. If nothing has changed for a very long time and there is no drive activity, it may genuinely be stuck.

If you must force it, hold the power button for around ten seconds. Then let it start normally and check that everything is intact.

Should you restart every day?

No, and there is no need.

Modern systems handle long uptimes well. A machine left running for weeks is not damaged by it.

What actually benefits from a periodic restart:

Applying updates, which is the strongest reason. Many security updates only take effect after one.

Clearing accumulated slowness, if you notice it. Some applications leak memory over days.

A machine that is genuinely misbehaving.

A reasonable habit: restart weekly, or whenever the system asks. Beyond that it is preference.

Sleep rather than shut down is fine for daily use and it is what most laptops are designed around. Battery consumption during sleep is small, and hibernate is available where it is not.

The one argument for shutting down: a machine that is off uses no power. Over a year that is a real if modest amount.

Restarting is not a maintenance strategy

Worth saying, because it becomes one by default.

If restarting fixes a recurring problem, find out why. Something is leaking, crashing or stuck, and the restart is postponing it.

Look at: what is running at startup, whether the drive is nearly full, whether the machine is overheating, and whether one particular application is always involved.

A machine that needs a daily restart to remain usable has a fault, not a habit.

Restart or reset — the words that get confused

Terminology varies and the consequences differ enormously.

Restart / reboot — same thing. Off and on again. Nothing is lost.

Reset — depends entirely on context. In Windows, "Reset this PC" reinstalls the system with an option to keep or remove your files. On a phone, "reset settings" and "factory reset" are very different. On a router, holding the reset button erases the configuration.

Refresh, repair, restore — all mean different things in different places.

Before pressing anything labelled reset, read what it says it will do. The word alone tells you nothing, and the difference between restart and reset is the difference between nothing lost and everything lost.

The short version

Restart clears memory and state. Shut down on Windows may not, because of Fast Startup.

When something is wrong, restart — not shut down, not sleep.

Nothing saved is deleted. Only unsaved work in memory is lost.

Restarting daily is unnecessary. Weekly, or when the system asks, is enough.

And if a restart is the only thing keeping the machine usable, that is a fault to investigate rather than a routine to keep.

For current Windows procedures and troubleshooting steps, see Microsoft Support.