Fast Startup vs Full Shutdown: Which One Causes Your Weird Bugs

What Fast Startup actually does when you press Shut Down

Fast Startup arrived with Windows 8 as a boot-time optimization: instead of shutting down cold, Windows logs off your session and then writes the kernel session, the loaded drivers and device state into hiberfil.sys — the same file classic hibernation uses. On the next power-on it reads that image back, which is why a hybrid boot feels snappier than a cold one. The price is that shutdown stops being a clean slate: a driver that wedged itself into a bad state on Monday is still there on Tuesday, because its state was frozen mid-flight. That is the entire trade — faster boots in exchange for a system that never fully resets.

Confusingly, Restart does not use Fast Startup: a reboot deliberately tears everything down and starts from scratch, which is why "have you tried restarting" works better than "have you tried shutting down". Windows Update knows the difference too, and schedules restarts rather than shutdowns whenever it needs a clean state. So when shutdown-and-power-on fixes nothing but a restart fixes everything, you have already found your culprit.

The weird bugs this one setting quietly causes

Most Fast Startup victims never connect the dots, because the symptom list reads like random bad luck rather than one root cause. The pattern is always the same: a glitch appears, shutdown does not clear it, restart does — and nobody asks why. These are the failures we keep seeing on machines where "shutting down" has not been real for months.

• Dual-boot and live-USB systems: Windows leaves NTFS volumes "dirty" inside the hibernation image, and Linux then mounts them read-only or refuses to mount them at all
• Audio, Wi-Fi and GPU drivers stuck in a bad state until an actual restart — the classic "shutdown doesn't fix it, reboot does" pattern
• USB drives and memory cards that won't eject because a stale kernel session still holds handles to them
• BitLocker, virtualization and some VPN clients behaving oddly after "shutdown", because they expect a cold boot
• Windows Update installations that only complete after a restart, since staged updates target the real boot path
• A hiberfil.sys eating roughly 40% of your RAM worth of disk for a boot speedup you may not even notice on an SSD

How to do a real shutdown — once or forever

For a one-off clean power-off, hold Shift while clicking Shut Down, or run shutdown /s /t 0 from the Run box or a terminal; both bypass the hybrid path completely. Holding Shift while choosing Restart gives you the full teardown plus the advanced boot menu when you need it. If the bugs are chronic, disable the feature itself: Control Panel → Power Options → "Choose what the power buttons do" → "Change settings that are currently unavailable", and untick "Turn on fast startup (recommended)". On a modern NVMe SSD the boot-time saving is a few seconds at most — you are trading very little for a machine that genuinely resets when you tell it to.

If you never use hibernation anyway, powercfg /h off in an admin terminal removes hiberfil.sys entirely and kills Fast Startup as a side effect — on a 32 GB machine that frees over 12 GB of disk. You can bring hibernation back later with powercfg /h on; nothing about it is destructive. The only group who should think twice is laptop owners who rely on hibernation for battery-safe sleep on the road.

Questions and Answers

Read next