Windows 8 Fast Startup and the Dual-Boot Lock Problem

The problem: your second operating system cannot see the disk

You shut down Windows 8, restart into Linux, and the Windows partition refuses to mount. The tool reports an unclean file system and demands a repair. The same symptom can block a BIOS or UEFI firmware update that expects a completely powered-off system.

The likely cause is Fast Startup, the hybrid boot behavior enabled by default in Windows 8 and later. It is not a full shutdown, and that difference matters when another operating system shares the same disk.

What Fast Startup actually does

When you choose Shut down, Windows does not close the kernel session completely. The kernel session is the core operating system state, including loaded drivers and system services. Instead of ending it, Windows writes that state to a file named hiberfil.sys on the system drive. User applications and user sessions are closed, but the system state is preserved on disk. On the next boot, Windows restores that saved session instead of initializing the kernel from scratch.

This differs from Restart, which always performs a full cold boot and reinitializes the kernel. It also differs from full hibernation in older Windows versions, which saved the entire user session. Fast Startup keeps only the system session, so the file is smaller and the resume is faster.

Why this creates trouble for dual-boot and firmware updates

Because the kernel session is saved rather than closed, Windows leaves NTFS volumes, the default Windows file system, in a state that another operating system interprets as dirty or in use. If Linux or another Windows installation writes to those partitions, it can corrupt data. Windows may mark the volume dirty and run a disk check the next time it accesses the drive fully.

Firmware updates that require a cold boot can also fail or behave unpredictably because the system never fully released hardware state during a Fast Startup shutdown.

Worked example: check and disable Fast Startup

Open an elevated Command Prompt. On Windows 8, press the Windows key, type cmd, right-click Command Prompt, and choose Run as administrator. You need administrator permissions because these commands change system power policy and can delete a system file.

First, confirm whether Fast Startup is available:

powercfg /a

Look for Fast Startup in the list of available sleep states. If it is missing, hibernation may be disabled or the device may use Connected Standby instead.

Next, inspect the hibernation file:

dir /a c:\hiberfil.sys

The file often occupies a substantial fraction of installed RAM. On a system with limited disk space, that can be meaningful.

To disable Fast Startup, turn off hibernation entirely:

powercfg /h off

This deletes hiberfil.sys and removes the Fast Startup option. The command typically returns silently on success, and hiberfil.sys no longer appears in the root of the system drive. Risk: boot times may increase on hard-disk systems, and hibernation is unavailable until you re-enable it.

To restore the original behavior later, run the same command in reverse:

powercfg /h on

If you want a smaller hibernation file without disabling the feature:

powercfg /h /type reduced

This reduces hiberfil.sys to roughly half of installed RAM.

To verify the change, shut down the computer, start the other operating system, and attempt to mount the Windows NTFS partition. It should mount without an unclean file system warning. You can also run powercfg /a again and confirm Fast Startup no longer appears as an available state.

Limitations and when to keep it enabled

• Fast Startup improves boot time most on hard-disk drives. Solid-state drive systems already boot quickly, so the gain is smaller.
• Systems with less than 4 GB RAM may lose a substantial amount of disk space to hiberfil.sys.
• Third-party full-disk encryption can interfere with the hibernation resume path. BitLocker is designed to work with Fast Startup.
• Tablets and convertibles using Connected Standby or Modern Standby do not use traditional Fast Startup; the mechanisms are mutually exclusive.
• Restart is always a full cold boot, so use Restart after driver changes or updates instead of Shut down when you need a clean kernel initialization.

Closing

Fast Startup is useful for single-boot Windows computers, especially on mechanical drives. If you share a disk with another operating system, or if a firmware update requires a true cold boot, disable hibernation with powercfg /h off and verify with powercfg /a and a cross-platform mount test.