How to Fix the Windows Fast Startup Error 0xc00000d4

If Windows fails Fast Startup with error status 0xc00000d4, it usually means the system could not complete the hybrid boot process correctly. Fast Startup combines parts of shutdown and hibernation, so a problem with boot files, hibernation data, storage drivers, or system corruption can stop it from working.

The good news is that this error is often fixable without reinstalling Windows. In many cases, you can get the PC booting normally again by turning off Fast Startup, repairing system files, or clearing out corrupted hibernation data.

What the 0xc00000d4 Error Usually Means

Fast Startup is designed to make Windows boot faster by saving part of the system state when you shut down. On the next startup, Windows loads that saved state instead of starting everything from scratch. Error 0xc00000d4 appears when Windows cannot use that saved startup data safely.

• Corrupted hibernation or Fast Startup data
• Damaged system files
• Problems with storage drivers or disk errors
• Interrupted Windows updates or an improper shutdown
• Firmware or BIOS settings that conflict with Fast Startup

Try These Fixes in Order

1. Boot into Windows normally if you can. If the PC will not boot at all, use Windows Recovery Environment or installation media to reach troubleshooting tools.
2. Turn off Fast Startup in Control Panel.
3. Disable hibernation from an elevated Command Prompt to clear the hibernation file.
4. Run system file repairs with SFC and DISM.
5. Check the disk for errors.
6. Update or roll back storage and chipset drivers if the issue started after a driver change.
7. If needed, review BIOS or UEFI settings and Windows boot configuration.

1. Disable Fast Startup

The simplest fix is often to stop Windows from using Fast Startup entirely. If the saved startup state is corrupted, disabling the feature forces Windows to start cleanly instead of reusing bad data.

1. Open Control Panel.
2. Select Hardware and Sound, then Power Options.
3. Click Choose what the power buttons do.
4. Select Change settings that are currently unavailable.
5. Uncheck Turn on fast startup (recommended).
6. Click Save changes and restart the computer.

2. Disable Hibernation to Rebuild the Startup Data

Fast Startup depends on hibernation. Turning hibernation off deletes the hiberfil.sys file, which can remove corrupted startup data. This is one of the most effective fixes when the error is tied to the hybrid shutdown process.

1. Open the Start menu, type cmd, then choose Run as administrator.
2. In the Command Prompt, enter: powercfg /h off
3. Press Enter and wait for the command to complete.
4. Restart the PC.
5. If you want hibernation back later, use powercfg /h on in an elevated Command Prompt.

3. Repair Windows System Files

If Windows system files are damaged, the Fast Startup process may fail before booting fully. Running SFC and DISM can repair missing or corrupted files that affect startup behavior.

1. Open Command Prompt as an administrator.
2. Run: sfc /scannow
3. Wait for the scan to finish.
4. If SFC reports problems it could not fix, run: DISM /Online /Cleanup-Image /RestoreHealth
5. Restart the PC after the repair completes.

4. Check the Drive for File System or Disk Errors

If the system drive has bad sectors or file system corruption, Windows may fail while loading the saved boot state. Checking the disk can expose problems that standard repairs miss.

1. Open Command Prompt as an administrator.
2. Run: chkdsk C: /f
3. If Windows asks to schedule the check for the next restart, type Y and press Enter.
4. Restart the computer and let the scan complete.
5. If errors keep coming back, back up important files and test the drive more thoroughly.

5. Update Storage and Chipset Drivers

Fast Startup relies heavily on storage and motherboard chipset drivers. If the problem started after a driver update, a new driver may be conflicting with the boot process. If it started after an update and you have a restore point or previous driver available, rolling back can also help.

1. Open Device Manager.
2. Expand Storage controllers and IDE ATA/ATAPI controllers, and also check Disk drives and System devices.
3. Look for devices with warning symbols or recent changes.
4. Update the relevant drivers from Windows Update or the hardware manufacturer's support page.
5. If the issue began after a driver update, use the Roll Back Driver option where available.

6. Review BIOS or UEFI Settings

Some BIOS or UEFI settings can interfere with Windows boot behavior, especially after firmware updates or hardware changes. In particular, storage mode changes and boot mode mismatches can cause Windows to fail during startup recovery.

• Confirm the boot mode matches the Windows installation, such as UEFI vs Legacy/CSM.
• Check whether storage controller mode was changed from AHCI to RAID or the reverse.
• Load optimized defaults only if you know your current settings are not required for a custom setup.
• Update BIOS/UEFI firmware only if the manufacturer recommends it for your issue.

7. Use Windows Recovery if the PC Will Not Start

If the computer cannot reach the desktop, use Windows Recovery Environment to access repair tools. This lets you disable Fast Startup, run startup repair, or open Command Prompt even when normal booting fails.

1. Power on the PC and interrupt the boot process three times to trigger recovery, or boot from a Windows installation USB.
2. Choose Troubleshoot.
3. Open Advanced options.
4. Try Startup Repair first.
5. If needed, open Command Prompt and run the repair commands from the earlier steps.
6. Use System Restore if you have a restore point from before the error began.

When a Clean Boot or Reset Is Worth Considering

If the error appears after you have ruled out disk errors, system file corruption, and driver issues, the Windows installation itself may be badly damaged. At that point, a repair install or reset may be more practical than spending hours chasing the cause.

• Repair install: keeps files and many apps while replacing Windows components
• Reset this PC: reinstalls Windows and lets you keep or remove personal files
• Clean install: best for severe corruption, but requires backing up data first

How to Prevent the Error From Coming Back

• Shut down Windows normally instead of forcing power off whenever possible
• Keep chipset, storage, and BIOS firmware up to date from trusted sources
• Avoid changing boot and storage settings unless you know why they are needed
• Watch for drive health warnings and replace failing SSDs or hard drives early
• Leave Fast Startup disabled if it keeps causing boot issues on your PC

What to Try First if You Want the Short Version

If you only want the most likely fix, disable Fast Startup, then disable hibernation with powercfg /h off. If the error continues, run SFC and DISM, then check the disk. Those four steps solve many cases without needing deeper recovery work.