What Shut down actually does
Windows saves the kernel session and the associated driver state to a hibernation file called hiberfil.sys. Microsoft Learn's Fast Startup documentation describes it the same way. On the next power-on, Windows resumes that saved kernel session instead of starting a new one.
Microsoft's power-state documentation adds that Windows signs the user out and closes user applications, then writes the kernel session and loaded kernel drivers to the hibernation file. Your apps and desktop session are gone. The kernel and driver state isn't. Think of it as reloading a save file rather than starting a new game.
Fast Startup is not new. Reporting on the topic notes that Microsoft's driver documentation says it has been the default shutdown transition since Windows 8.
Fast Startup isn't the only way a shutdown works. A full shutdown can be requested explicitly, and Fast Startup can be switched off. Some machines also have it unavailable. The behavior described here applies to the Fast Startup path.
What Restart does differently
Microsoft's guidance is that a restart produces a full shutdown state for Windows, not the S4-style hybrid transition Fast Startup uses. The next boot initializes a new kernel session and reloads drivers as Windows comes back up. Microsoft's Fast Startup article states plainly that the Fast Startup setting doesn't apply to Restart. Strictly, that quote is from Microsoft's troubleshooting note as relayed in the research. The point stands either way: Restart ignores the shortcut.
Microsoft also explains why this matters for updates. When you restart, you typically want a completely new Windows state, for example because you installed a driver or replaced Windows components that can't be swapped without a full restart. This is why a pending-restart prompt can still be waiting for you after you shut down. Reporting on a related Microsoft article (KB4011287) says some Windows updates may not complete after Shutdown because Fast Startup hibernates the system instead of performing the full shutdown they require.
How the four power options compare
These are the normal behaviors. Individual devices can differ.
| Option | Open apps kept? | Fresh kernel and drivers? | Notes |
|---|---|---|---|
| Shut down (Fast Startup on) | No | No | Kernel and drivers saved to hiberfil.sys |
| Restart | No | Yes | Bypasses Fast Startup |
| Sleep | Yes | No | Low power, quick return |
| Hibernate | Yes | No | Session saved to disk, uses less power than Sleep |
Microsoft Support describes Sleep as using very little power, starting up faster and returning you to where you left off. It describes Hibernate as using less power than Sleep, with a slower resume. Microsoft also notes that Hibernate might not be available on all PCs. That detail comes from the Microsoft Support page covered in the source packet, not from the search results above.
Problems a restart may clear
A MakeUseOf piece by Afam Onyimadu says these problems can survive a nightly shutdown:
- Wi-Fi that won't reconnect
- Bluetooth earbuds that refuse to pair with the PC
- display flicker
- audio cutouts
- a laptop that feels sluggish
- an update prompt that keeps coming back
His reasoning is that a driver stuck in a bad state can be reloaded in that same state after a shutdown. That's plausible, and Restart is cheap and quick to try. Still, nothing in Microsoft's documentation ties these symptoms to Fast Startup. Treat Restart as a low-effort first test, not a diagnosis.
Microsoft Support's own advice is in the same spirit. If devices misbehave after sleep or hibernate, you may need to reconnect them or restart the PC. You should also make sure drivers are current.
Limits: when Restart won't help
Onyimadu himself admits that Restart won't fix failing hardware, corrupted files or a driver that is simply faulty. If the problem comes back after a clean restart, stop restarting and start troubleshooting. Check for driver updates, review Event Viewer and run hardware diagnostics.
One of his claims is more of an opinion than a fact. He suggests restarting at least once a week even when everything works. That's reasonable housekeeping, but Microsoft doesn't require it. The same article says some device glitches respond better to a full power-off, so the picture isn't one-size-fits-all.
How to get a clean boot
Option 1: Restart
Select Start > Power > Restart. Check whether the symptom is still there. If it isn't, a stale kernel or driver state was a likely culprit, though not a proven one.
Option 2: Full shutdown from Run
- Press Windows key + R.
- Type
shutdown /s /t 0and press Enter. - Save your work first, because the command doesn't prompt you.
Microsoft documents this as a way to shut down without Hybrid Shutdown. The /hybrid switch is the one that asks for the Fast Startup-style shutdown. Other guides also list holding Shift while clicking Shut down as a one-off bypass. That tip comes from secondary sources, not Microsoft, so use it with that in mind.
Option 3: Turn off Fast Startup
- Open Power Options in Control Panel.
- Click Choose what the power buttons do.
- Click Change settings that are currently unavailable.
- Clear the Turn on fast startup (recommended) checkbox, if it's listed.
Microsoft's troubleshooting note says disabling Fast Startup isn't recommended as a general fix. Treat this as a preference or a diagnostic step, not a tweak everyone should make. The trade-off is a slower boot.
One warning for people who like terminal commands. Turning off hibernation entirely with powercfg /hibernate off is not the same thing. Turning hibernation off with powercfg /hibernate off removes hiberfil.sys entirely and also disables both Hibernate and Fast Startup. Unticking the Control Panel box leaves Hibernate available.
Check your uptime
Open Task Manager, go to Performance > CPU and look at Up time. If it shows several days even though you shut down last night, there hasn't been a full kernel restart. Microsoft's documentation says uptime between kernel reboots may be significantly longer because Fast Startup preserves the kernel, drivers and services across shutdowns. That's why this matters for IT admins too. Reporting from one admin-focused site notes that LastBootUpTime won't reset after a Fast Startup shutdown the way it does after a Restart, which can skew uptime and reboot-compliance reports.
Bottom line
- Shut down with Fast Startup on preserves kernel and driver state. Restart discards it.
- When Windows says it needs a restart, restart. Shutting down may leave updates unfinished.
- If a glitch survives a shutdown, restart once before doing anything drastic.
- If the problem comes back after a restart, it needs real troubleshooting.
- Disabling Fast Startup is optional, and Microsoft doesn't recommend it as a default fix.
The old IT advice to turn it off and on again still works. Just make sure "off" actually means off.
References
- Why restarting Windows can fix problems that shutting down won't MakeUseOf · 2026-11-19T17:00:17+00:00
- Fast startup causes hibernation or shutdown to fail in Windows 10 or Windows 8.1 - Windows Client | Microsoft Learn learn.microsoft.com
- Shut down, sleep, or hibernate your PC | Microsoft Support support.microsoft.com