Fast Startup is a Windows power feature that hibernates the kernel session at shutdown instead of closing it completely, so the next start resumes that saved state rather than initializing the operating system from scratch. It is enabled by default on most installations of Windows 10 and Windows 11 and is also known as hybrid boot or hybrid shutdown.
For Windows administration, Fast Startup matters because it changes what shutdown actually means. A machine that has been shut down with the feature active has not performed a clean boot, which affects driver updates, dual-boot setups, disk access from other operating systems and troubleshooting procedures that assume a fresh start.
How Fast Startup works
Fast Startup combines logoff and hibernation in a single shutdown sequence. When a user chooses Shut down, Windows first closes all user sessions and applications, exactly as a normal shutdown would. It then writes the remaining session 0 state, which contains the kernel, loaded drivers and system services, to the hibernation file hiberfil.sys on the system drive and powers off.
At the next power-on, the boot loader detects the saved image and reads it back into memory instead of loading and initializing the kernel and drivers one by one. Drivers receive a resume notification rather than a full initialization, and the system proceeds directly to the sign-in screen. The time saved depends mainly on storage speed and driver initialization cost; the benefit is largest on hard disks and modest on fast NVMe drives.
Fast Startup does not shorten firmware initialization. The UEFI or BIOS still runs its power-on self-test and hands control to the Windows boot manager as usual, so machines with slow firmware, many storage controllers or long network boot timeouts gain less. The savings occur only in the operating system phase of the boot, after firmware has finished.
Because the feature reuses the hibernation mechanism, it requires hibernation to be enabled. Running powercfg /h off deletes the hibernation file and removes Fast Startup at the same time.
Shutdown, restart and hibernate compared
The key administrative fact is that Restart always performs a full cold boot, while Shut down performs a hybrid shutdown when Fast Startup is on. This often surprises users who expect shutdown to be the more thorough option.
| Action | User session | Kernel and drivers | Next start |
|---|---|---|---|
| Shut down with Fast Startup | Closed | Saved to hiberfil.sys | Hybrid boot |
| Shut down without Fast Startup | Closed | Fully unloaded | Cold boot |
| Restart | Closed | Fully unloaded | Cold boot |
| Hibernate | Saved | Saved to hiberfil.sys | Resume with open apps |
| Sleep | Kept in RAM | Kept in RAM | Near-instant resume |
A full shutdown can be forced without changing settings by holding Shift while selecting Shut down, or by running shutdown /s /f /t 0. The Kernel-Boot event with ID 27 in Event Viewer records the boot type, where 0x1 indicates a hybrid boot and 0x0 a cold boot.
Configuring Fast Startup
Fast Startup can be controlled per machine through several interfaces, which allows both individual users and administrators managing fleets to set it consistently.
| Method | Location or command | Typical use |
|---|---|---|
| Control Panel | Power Options, choose what the power buttons do | Single computer, interactive change |
| Windows registry | HiberbootEnabled value under Session Manager Power key | Scripts and imaging |
| Group Policy | Require use of fast startup policy | Enforcing the feature in a domain |
| Hibernation command | powercfg /h off or on | Removing or restoring hibernation entirely |
| Device management | Configuration profiles or scripts in Microsoft Intune | Cloud-managed fleets |
The size of the hibernation file is a fraction of installed RAM, commonly around 20 to 40 percent depending on the hibernation file type. The reduced type, set with powercfg /h /type reduced, supports Fast Startup but not full hibernation, which saves disk space on systems that never hibernate.
When to disable Fast Startup
Fast Startup is beneficial on ordinary single-boot desktops and laptops, but several scenarios make disabling it the safer choice. The decision depends on whether a clean boot or exclusive disk access matters more than a few seconds of startup time.
| Situation | Recommendation | Reason |
|---|---|---|
| Dual boot with Linux | Disable | NTFS volumes stay in a hibernated state |
| Frequent driver or BIOS changes | Disable or use Restart | Drivers resume instead of reinitializing |
| Wake-on-LAN management | Test, often disable | Some adapters ignore wake packets after hybrid shutdown |
| Encrypted drives with pre-boot checks | Review behavior | Hibernated state interacts with unlock flow |
| Typical home or office PC | Keep enabled | Faster starts with little downside |
In dual-boot setups the risk is real data damage: when another operating system writes to an NTFS volume that Windows has hibernated, Windows may later resume with an outdated view of the file system. Many Linux distributions therefore mount such volumes read-only.
Common problems and misconceptions
Many support issues come from assuming that shutdown clears the system state. With Fast Startup active, faults in drivers or services can persist across shutdowns, and only a Restart truly resets them.
- Uptime does not reset after shutdown, so Task Manager may show days of uptime on a machine shut down every evening.
- Pending updates may require Restart, because some installation steps run only during a cold boot.
- Troubleshooting advice to turn it off and on fails when the user chooses Shut down instead of Restart.
- Peripheral and network adapters sometimes resume in a faulty state after a driver change.
- Fast Startup is not hibernation, since open applications and documents are not preserved.
Understanding it simply
Fast Startup makes a Windows computer start faster by not fully switching off its core. When you shut down, your apps close, but the heart of the system is saved to the disk. At the next start, Windows simply loads that saved state.
It is like keeping a stove’s pilot light burning so the burner lights faster. That is convenient most of the time. When something goes wrong, though, choose Restart for a truly fresh start.
Applied in practice
An IT administrator in a 200-seat office receives repeated reports that a new docking station driver does not take effect, even though users shut down their laptops every night. Event Viewer shows boot type 0x1 on every start, confirming that the machines are performing hybrid boots and never reinitializing the driver.
The administrator advises users to choose Restart after updates and configures the patch schedule to trigger restarts automatically. For the twenty workstations that are woken at night for maintenance, Fast Startup is turned off through a Group Policy registry setting, because their network adapters ignored wake packets after hybrid shutdown.
Docking issues stop within a day, and overnight maintenance completion rises to the expected level, while the remaining laptops keep their faster startup times.