Windows Latest highlighted the distinction in a September 18 report, explaining that Fast Startup preserves the Windows kernel session during a normal graphical shutdown and restores it at the next power-on. Microsoft’s own Windows power-state documentation makes the same point more precisely: a requested shutdown normally uses Fast Startup when it is available, while a restart requires a full Windows shutdown sequence.
For users and administrators, the result is simple. A normal Shut down can leave the kernel-side state saved in hiberfil.sys; Restart throws that saved session away and initializes Windows again. That is why “restart the PC” remains the right first step for many support procedures, even for a machine that was powered off overnight.
Fast Startup saves the kernel, not your desktop
Fast Startup was introduced with Windows 8 to reduce boot times, particularly on machines with mechanical hard drives. Windows signs the user out and closes user applications, then writes the kernel session—commonly called session 0—and loaded kernel drivers to the hibernation file. At the next startup, Windows restores that reduced hibernation image rather than building the kernel environment from nothing.
This is different from full hibernation. A full hibernation file can preserve a user’s desktop session, including running applications and memory contents. Fast Startup does not reopen the apps that were running when the user selected Shut down; it retains only the operating-system portion needed to accelerate the next boot.
That separation explains a common source of confusion in Task Manager. A user can shut down a PC, start it the next morning, and see an uptime value that appears to stretch across both days. With Fast Startup, Windows did not complete the same kernel reset that a restart would have performed.
Microsoft describes Fast Startup as the default transition for a requested Windows shutdown, but that does not mean it operates on every PC. It depends on hibernation being enabled, and organizations can turn it off through configuration or policy. It is also routinely disabled on some dual-boot systems because mounting a Windows volume from another operating system after a hybrid shutdown can create filesystem risks.
Restart clears the Windows session—but “cold boot” is the wrong term
Windows Latest describes Restart as a cold boot. That wording overstates what happens. In PC terminology, a cold boot usually means starting a machine from an off state after power has been removed or reset; Restart is generally a warm reboot. The motherboard and attached devices may not go through exactly the same electrical reset path as they would after power has been fully removed.
But the distinction is not academic. Microsoft’s system-power documentation says a restart produces a full shutdown state for Windows, rather than the S4-style hybrid transition used by Fast Startup. The kernel session is ended instead of being written to disk for restoration. The next boot has to initialize a new kernel session and reload drivers as Windows comes back up.
That makes Restart the better choice for software-state problems, including:
- A network adapter, Bluetooth radio, audio device, USB peripheral, or graphics driver that has stopped responding correctly.
- A Windows service that is stuck, or a system component that remains unstable after an application has closed.
- A Windows update, driver installation, or security product deployment that explicitly requires a restart.
- Troubleshooting procedures where an administrator needs to know the next boot started with a new Windows kernel session.
It does not guarantee that every hardware or firmware problem disappears. A misbehaving device can retain state across a warm reboot, and a fault in UEFI firmware, a docking station, external storage, RAM, or the physical device itself may survive a restart. In those cases, a full power-off cycle—sometimes including disconnecting AC power or removing a battery where appropriate—can still be materially different.
The safe conclusion is narrower: Restart is the most reliable built-in way to reset Windows itself. It is not a universal substitute for removing power from every component connected to a PC.
The command-line full shutdown is real—and differs from the Start menu
The most useful detail in the Windows Latest report is the command for bypassing Fast Startup without changing its global setting:
shutdown /s /t 0
Microsoft’s troubleshooting documentation explicitly identifies this as a full shutdown command. In other words, the command ends Windows normally without preparing the saved Fast Startup image. It is a workable option for administrators, lab operators, and power users who need the next physical power-on to begin from a fresh Windows kernel session but do not want to disable Fast Startup permanently.
The related command is the opposite:
shutdown /s /hybrid /t 0
Microsoft documents /hybrid as the option that prepares a device for Fast Startup. That matters because it undercuts a surprisingly common assumption: shutdown.exe does not merely mimic clicking Start, Power, Shut down. The plain command-line shutdown path is a full shutdown by default; adding /hybrid requests the faster hybrid behavior.
There is one operational trap. Adding /f forces applications to close without allowing them to prompt for unsaved work. IT scripts sometimes use it to prevent a deployment from hanging on a user session, but it should not be treated as a harmless enhancement to either command. A zero-second timeout is enough to make the shutdown immediate once Windows has handled ordinary application-close requests.
Users who prefer a graphical route can also hold Shift while selecting Shut down, which requests a full shutdown rather than the Fast Startup path. For fleets, however, the better approach is usually consistency: either manage Fast Startup through policy and power settings, or document the required restart and shutdown procedure in the support runbook.
Fast Startup’s benefit has narrowed on SSD-equipped PCs
Fast Startup was designed in an era when many consumer Windows systems booted from slow spinning disks. Saving a reduced kernel image to disk and restoring it later could shave a noticeable amount of time from startup. The feature remains useful on older hardware and systems where startup time still affects how people use the machine.
On a modern NVMe-based Windows 11 PC, the payoff can be far smaller. Firmware initialization, device enumeration, security checks, startup applications, endpoint protection, and network sign-in may consume more time than the kernel restoration Fast Startup avoids. That does not make Fast Startup harmful by default, but it does make the trade-off less automatic than it was on Windows 8-era hardware.
For enterprise administrators, the larger consideration is predictability. A shared workstation, developer test system, dual-boot computer, or endpoint with recurring driver issues may be easier to support when every shutdown is a full shutdown. A standard office laptop that simply needs to get to the sign-in screen quickly may be better served by leaving the default behavior alone and using Restart when maintenance requires it.
Microsoft does not broadly advise users to turn off Fast Startup as routine maintenance. Its own documentation presents the feature as a boot-time optimization. The stronger recommendation is procedural: do not tell a user to “turn it off and on again” when the fix requires Windows to rebuild its kernel state. Tell them to restart.
What support instructions should say
The most durable lesson from this report is about language. “Shut down and turn it back on” is ambiguous on a Fast Startup-enabled Windows system. It can mean a hybrid shutdown followed by restoration of the prior kernel session—the exact outcome that may preserve the condition a help desk is trying to clear.
For ordinary troubleshooting, support documentation should specify Restart. For a clean powered-off state, it should specify a full shutdown, such as Shift+Shut down or shutdown /s /t 0. For a hardware-level reset, it should spell out whether the device must remain off, unplugged, or disconnected from peripherals.
Windows’ labels still make Shut down sound more final than Restart. In practice, with Fast Startup enabled, Restart is the command that gives Windows the cleaner beginning.