Fix Hibernate Not Working in Windows 11 and 10: Enable, Rebuild and Diagnose Power Issues

Before changing hibernation settings​

Hibernate writes the current Windows session from RAM to the system drive’s hidden hiberfil.sys file, then powers the PC down. A successful hibernation test should leave the computer apparently off: fans, display, and normal activity LEDs should stop. Pressing the power button later should restore your apps and documents where you left them.

Have the following ready:

• An administrator account. The repair commands require elevation.
• Enough available space on the Windows system drive. A full hibernation file consumes a substantial amount of disk space because it stores the active session.
• A few minutes to restart the computer after driver or hibernation-file changes.
• Saved work before testing. Hibernation is designed to preserve your session, but troubleshooting should never be the only copy of unsaved work.

Warning: Disabling hibernation deletes the existing hibernation file. Do not do this while a previous hibernated session needs to be resumed. It also makes Fast Startup and Hybrid Sleep unavailable until hibernation is enabled again.

Check whether your PC can hibernate​

Do not begin by changing registry values or downloading “hibernation repair” utilities. Windows already includes the diagnostic tool needed to determine whether the machine and current configuration can use hibernation.

1. Right-click Start and select Terminal (Admin) on Windows 11, or Windows PowerShell (Admin) / Command Prompt (Admin) on Windows 10.
2. Approve the User Account Control prompt.
3. Run:
   powercfg /a
4. Read the result carefully.

Look for an available state that includes Hibernate. If Windows reports that hibernation is unavailable, it normally gives a reason, such as firmware configuration, a missing hibernation file, or a platform capability limitation.

A result saying that Hibernate has not been enabled is repairable with the next section. A result saying that firmware does not support the state is different: Windows cannot create support for hibernation when the computer’s firmware or hardware does not expose it. Check for a BIOS/UEFI update from the PC manufacturer and consult the manufacturer’s support material for the model before changing deeper power settings.

Some modern PCs use a Modern Standby power model instead of the older S3 sleep model. That does not automatically mean hibernation is broken. The important result here is whether Windows lists hibernation as available and explains any unavailable state.

Enable Hibernate and restore it to the Power menu​

First, enable the feature at the operating-system level. In the same elevated Terminal, PowerShell, or Command Prompt window, run:

powercfg /hibernate on

Then force Windows to use a full hibernation file:

powercfg /hibernate /type full

This distinction matters. Windows can use a reduced hibernation file for Fast Startup, but a reduced file does not support normal user-initiated hibernation. A full file supports Hibernate, Hybrid Sleep where available, and Fast Startup.

Run the check again:

powercfg /a

Hibernate should now be shown as available if the PC supports it.

Next, add the command to the visible Power menu.

1. Open Search, type Control Panel, and open it.
2. Select System and Security.
3. Under Power Options, select Choose what the power buttons do.
4. Select Change settings that are currently unavailable.
5. Under Shutdown settings, select the Hibernate checkbox.
6. Select Save changes.

You can now test from either of these locations:

• Start > Power > Hibernate
• Press Windows key + X, then select Shut down or sign out > Hibernate

If the Hibernate checkbox is absent even after powercfg /hibernate on and powercfg /hibernate /type full, rerun powercfg /a. The explanation in that output is more useful than repeatedly reopening Control Panel. On a work-managed PC, an organizational policy may also hide the command; contact the organization’s IT administrator rather than attempting to override management settings.

Rebuild a damaged hibernation file​

If Hibernate is listed and selectable but the PC fails to save the session, restarts instead of resuming, shows a blank screen after resume, or returns to a fresh sign-in session, recreate the hibernation file.

Warning: The following commands remove the current hibernation file. Close programs and save all files first. If the PC is currently in a hibernated state, start it normally and sign in before continuing.

1. Open an elevated Terminal, PowerShell, or Command Prompt window.
2. Disable hibernation:
   powercfg /hibernate off
3. Restart the PC using Start > Power > Restart. Use Restart, not Shut down, so Windows and drivers start from a clean state.
4. After sign-in, open another elevated command window.
5. Re-enable hibernation:
   powercfg /hibernate on
6. Set the hibernation file to full mode again:
   powercfg /hibernate /type full
7. Run:
   powercfg /a
8. If Hibernate is available, select Start > Power > Hibernate and wait until the PC fully powers down.
9. Press the physical power button. The expected result is that the same desktop session returns, including the apps that were open before hibernation.

This reset is preferable to manually deleting hiberfil.sys. Windows owns that protected system file and creates it automatically when hibernation is enabled.

Review Fast Startup, sleep, and hibernation timers​

Fast Startup and normal hibernation use related technology, but they are not the same operation:

• Hibernate saves your entire signed-in session so it can be restored later.
• Fast Startup applies to a normal Shut down operation. It saves the Windows kernel session to speed the next boot, but closes your apps and signs you out.
• Sleep keeps the session in memory and uses power while the computer is sleeping.

A PC that “wakes immediately” may actually be entering Sleep or Hybrid Sleep rather than completing a Hibernate transition. Confirm the test command is Hibernate, not Sleep.

Check Fast Startup​

Fast Startup normally does not need to be disabled for standard hibernation to work, especially after you have set a full hibernation file. However, temporarily turning it off is a useful diagnostic if the issue occurs after selecting Shut down, if the PC restarts unexpectedly, or if boot/resume behavior is confusing.

1. Open Control Panel > System and Security > Power Options.
2. Select Choose what the power buttons do.
3. Select Change settings that are currently unavailable.
4. Under Shutdown settings, clear Turn on fast startup (recommended).
5. Select Save changes.
6. Restart once and test Hibernate again from Start > Power > Hibernate.

If this makes no difference, you can return to the same screen and re-enable Fast Startup. If it does resolve a shutdown-related issue, leave it off until you have updated the relevant drivers and firmware.

Review the idle hibernation timeout​

The timeout controls automatic behavior when the PC is idle; it does not prevent you from choosing Hibernate manually from the Power menu.

On Windows 11, open:

Start > Settings > System > Power & battery > Screen, sleep, & hibernate timeouts

Review the sleep and hibernation timing options shown for battery and plugged-in use.

On Windows 10, open:

Start > Settings > System > Power & sleep

Then select Additional power settings to reach the classic Power Options controls.

For either version, the classic path gives access to the active plan’s advanced settings:

1. In Power Options, find the active plan and select Change plan settings.
2. Select Change advanced power settings.
3. Expand Sleep.
4. Review Sleep after, Allow hybrid sleep, and Hibernate after for both battery and AC power where those options are present.
5. Select Apply, then OK after making a deliberate change.

Do not set every timer to zero or “Never” as a blanket fix. Set an interval that matches how you use the PC, then test manual Hibernate separately. That keeps automatic idle behavior from masking a failed manual hibernation transition.

Identify wake sources and power blockers​

If the computer appears to hibernate but comes back on right away, gather evidence immediately after the unexpected resume. Open an elevated command window and run:

powercfg /lastwake

This reports the most recent wake source where Windows can identify one. Then run:

powercfg /waketimers

Wake timers can bring a PC out of a low-power state for scheduled work. Also check devices currently armed to wake the system:

powercfg /devicequery wake_armed

Common entries include network adapters, USB keyboards, USB mice, Bluetooth devices, and docking-station components. A device being listed does not prove it caused the specific wake, but it gives you a focused list to investigate.

To stop a listed device from waking the PC through PowerCfg, use its exact name from the output. For example:

powercfg /devicedisablewake "exact device name"

Use this cautiously. Disabling wake on a keyboard, mouse, or network adapter can make it impossible to wake the PC using that device. Pressing the physical power button should still be the primary resume method.

To restore wake permission later, run:

powercfg /deviceenableawake "exact device name"

If the problem is that the PC refuses to enter an automatic low-power state, rather than waking after manual Hibernate, run:

powercfg /requests

This lists active application and driver power requests. Do not use powercfg /requestsoverride as a first response. Overriding a request can interrupt legitimate activity such as media playback, remote access, backups, or device work. Identify and update, close, or reconfigure the named software or driver first.

Update or roll back the drivers most likely to affect power transitions​

Drivers participate in hibernation and resume. Prioritize updates for the components involved in the transition:

• Graphics adapter
• Chipset or platform driver package
• Storage controller or NVMe driver
• Wi-Fi, Ethernet, Bluetooth, and docking-station drivers
• USB controller and external-device drivers

Windows 11 driver updates​

1. Open Start > Settings > Windows Update > Advanced options.
2. Under Additional options, select Optional updates.
3. Open Driver updates if it appears.
4. Select relevant driver updates and choose Download and install.
5. Restart the PC even if Windows does not specifically request it.
6. Test Hibernate again.

Windows 10 driver updates​

1. Open Start > Settings > Update & Security > Windows Update > Advanced options.
2. Return to Windows Update and select Check for updates.
3. If available, select View optional updates.
4. Open Driver updates, select appropriate updates, and choose Download and install.
5. Restart and retest.

If Windows Update does not offer a newer driver, use the PC manufacturer’s support site for a laptop or prebuilt desktop, or the component manufacturer’s official site for a custom-built PC. Match the driver to the exact Windows version and architecture. Avoid driver-download sites that are not the manufacturer’s official source.

If hibernation began failing immediately after a driver update, roll back that specific device driver:

1. Right-click Start and select Device Manager.
2. Expand the relevant category, such as Display adapters or Network adapters.
3. Right-click the affected device and select Properties.
4. Open the Driver tab.
5. Select Roll Back Driver, choose a reason if asked, and confirm.
6. Restart before testing Hibernate.

If Roll Back Driver is unavailable, Windows has no previous driver package stored for that device. Update it from the computer or component manufacturer instead.

When the problem is not fixed​

Use the symptom to choose the next action:

• Hibernate is absent and powercfg /a says the firmware does not support it: Windows cannot enable the unavailable hardware state. Check the PC manufacturer’s BIOS/UEFI updates and model-specific documentation.
• Hibernate is absent but powercfg /a says it is disabled: Run powercfg /hibernate on, then set /type full and enable the Hibernate checkbox in Control Panel.
• Hibernate starts but resume gives a black screen, reboot, or lost session: Rebuild the hibernation file, update the graphics, chipset, and storage drivers, then test with nonessential USB devices and docks disconnected.
• The PC resumes immediately: Test manual Hibernate from the Start menu, inspect powercfg /lastwake, powercfg /waketimers, and powercfg /devicequery wake_armed, then address the identified device or scheduled wake source.
• Only attached displays, printers, scanners, or docks fail after resume: Disconnect and reconnect the affected device, then update its driver. Restarting the PC is an appropriate recovery step if the device does not reinitialize.
• The issue began after a driver update: Roll back the affected driver and restart. Do not roll back unrelated drivers.
• The PC is managed by work or school: Leave policy-controlled power settings to the IT administrator, particularly if Hibernate is unavailable only on the managed device.