Windows 11 hibernate not working — the machine going to sleep instead of hibernating, hibernate missing from the power menu, or the computer not waking from hibernate — is one of those issues that seems complicated but usually isn’t. Most cases come down to hibernate being disabled in Windows or a driver incompatible with the deep power-off state hibernate uses. You’ll find the complete rundown in our Complete Guide to Fixing Windows, Browser, and Software Errors.
Quick orientation: hibernate saves the full RAM contents to disk (hiberfil.sys), then fully powers off. On wake, Windows reads that file back into RAM and resumes exactly where you left off. Sleep keeps RAM powered. If hibernate isn’t available at all: it needs to be enabled first. If it fails on resume: a driver or hardware issue is usually the culprit.
Step 1: Enable hibernate
Hibernate is disabled by default on many Windows 11 machines, especially those with SSDs or Fast Startup enabled. Administrator Command Prompt:
powercfg /hibernate on
After running this: the hibernate option should appear in Start → Power → Hibernate. If it still doesn’t appear: go to Settings → System → Power & battery → “Additional power settings” (classic Control Panel) → “Choose what the power buttons do” → “Change settings that are currently unavailable” → check “Hibernate” under Shutdown settings → Save changes.
Hibernate missing from the power menu
Even with hibernate enabled via powercfg, it won’t appear in the Start menu Power button if it’s not checked in Control Panel’s shutdown settings. The two-step process (enable via powercfg, then show in menu via Control Panel) is the complete fix. Both steps are required.
Computer won’t wake from hibernate
If the machine hibernates successfully (powers fully off) but won’t wake: this is almost always a driver issue. A driver that doesn’t support hibernation correctly either prevents resume or causes a crash during the resume process.
Common problematic drivers: GPU drivers (NVIDIA and AMD both have hibernate-related bugs that periodic driver updates address), Wi-Fi adapter drivers, and USB controller drivers. Update the GPU driver first — it’s the most frequent cause. If updating doesn’t help: check Event Viewer → Windows Logs → System for error events that occurred at the exact time of the failed resume attempt. These events name the driver or component that caused the failure.
Hibernate file size and disk space
The hiberfil.sys file that stores RAM contents is sized at 75% of installed RAM by default. On a machine with 32 GB RAM: that’s 24 GB of disk space dedicated to hibernation. If the disk is nearly full: hibernate fails because Windows can’t write the full RAM contents.
Check hiberfil.sys size: File Explorer → C: → View → Hidden items → find hiberfil.sys → check size. If disk space is critically low: free space elsewhere before hibernating. The hibernate file size can be reduced: powercfg /hibernate /size 50 (reduces to 50% of RAM) — though this may cause issues if RAM usage at hibernate time exceeds the file size.
Fast Startup and hibernate — the interaction
Windows’ Fast Startup uses a form of hibernate for the shutdown process — it saves the OS kernel state to disk for faster startup. This is separate from full hibernate (which saves all running applications). Fast Startup and full hibernate can conflict in some configurations.
If hibernate fails after enabling Fast Startup or vice versa: try disabling Fast Startup (Control Panel → Power Options → “Choose what the power buttons do” → uncheck “Turn on fast startup”) → test hibernate. On many machines, disabling Fast Startup makes full hibernate more reliable.
Hibernate on laptops: battery threshold
Laptops automatically hibernate when battery drops below a critical level. This “critical battery action” can be set in Power Options → your plan → “Change plan settings” → “Change advanced power settings” → Battery → Critical battery action → “Hibernate.” This protects the session when the battery dies rather than losing unsaved work.
If the laptop never hibernates even at critical battery: the critical battery action may be set to “Sleep” or “Shut down” instead. For laptops used away from power: setting critical battery action to “Hibernate” is highly recommended.
SFC and system file check
Hibernate infrastructure (the drivers and system files that manage the hibernate/resume process) can become corrupted. Administrator Command Prompt:
sfc /scannowIf SFC reports repaired files: restart → test hibernate. Corruption in the power management subsystem files is a less common cause of hibernate failure but worth checking when driver updates and disk space haven’t resolved the issue.
Our guide on Windows startup issues covers wake-from-hibernate boot failures that look like startup problems. For the driver update process that resolves hibernate compatibility, our GPU driver guide covers the update path for NVIDIA and AMD drivers. Microsoft’s hibernate documentation covers the powercfg /availablesleepstates command that lists all sleep states the current hardware supports and whether any are blocked by hardware or driver constraints.
Checking available sleep states
Administrator Command Prompt:
powercfg /availablesleepstatesThis lists every sleep/hibernate state the system supports, and — critically — explains why any states are unavailable. If hibernate (S4) shows “Not Available,” the output explains the specific reason:
- “The following sleep states are not available on this system: Hibernate” followed by “The system firmware does not support hibernation” — BIOS/UEFI doesn’t support it; enabling hibernate in BIOS setup may help
- “A driver has reported that it is not compatible with hibernation” — a specific driver name is listed; update or remove that driver
- “The hiberfile is not large enough to store the memory state of the system” — increase hiberfil.sys size or free RAM before hibernating
The powercfg /availablesleepstates output is the most direct path to understanding exactly why hibernate isn’t working — it names the problem explicitly rather than requiring guesswork.
Hibernate vs Modern Standby
Newer Windows 11 machines (especially those designed for Always-On functionality like Surface devices and certain premium laptops) use Modern Standby (S0 Low Power Idle) instead of traditional sleep states. On these machines: hibernate may not be supported or may behave differently because Modern Standby is the platform’s primary low-power state.
Running powercfg /availablesleepstates on a Modern Standby machine typically shows S0 available but may show S3 (traditional sleep) and S4 (hibernate) as not supported. Hibernate can sometimes be enabled on these systems through BIOS settings, but it’s architecturally different from traditional hibernate on older hardware.
Hibernate failing for specific users but not others
If hibernate works for administrator accounts but not standard user accounts: it’s a Group Policy or permissions issue. Standard users are sometimes restricted from initiating hibernate through policy. gpedit.msc → Computer Configuration → Windows Settings → Security Settings → Local Policies → User Rights Assignment → “Allow log on locally” and related power management policies. In enterprise environments: IT controls these policies.
Scheduled hibernate
Windows Task Scheduler can trigger hibernate at a specific time or after a period of inactivity. Create a Basic Task → Action “Start a program” → Program: rundll32.exe → Arguments: powrprof.dll,SetSuspendState 1,1,0. This initiates hibernate regardless of the power button settings. Useful for automatically hibernating machines that might otherwise sleep and drain battery overnight.
Hibernate and connected devices
USB devices sometimes prevent hibernate from completing. A USB device that doesn’t support hibernate correctly holds the power state open. Device Manager → right-click any USB hub or input device → Properties → Power Management → uncheck “Allow this device to wake the computer.” Preventing USB devices from interrupting hibernate ensures the machine completes the hibernate process without being interrupted by USB device state transitions.
External hard drives and some USB devices also need time to complete ongoing operations before hibernate writes RAM to disk. If a large copy operation is in progress when hibernate triggers: the operation pauses, hibernate writes state, and on resume the operation may fail because the drive’s state isn’t consistent with the paused operation. Completing large transfers before hibernating avoids this scenario.
Hibernate and pagefile / virtual memory
When hibernate writes RAM to disk, it also needs to handle virtual memory (the pagefile). If the pagefile is on a different drive from the Windows installation: hibernate needs to coordinate data from multiple drives. This adds complexity and occasionally causes hibernate failures on multi-drive configurations. Ensuring the pagefile is on the Windows drive (usually C:) simplifies the hibernate process and can resolve failures on machines with unusual storage configurations.
Hibernate on desktop PCs: specific considerations
Desktop PCs are less commonly used with hibernate than laptops, but hibernate has genuine benefits for desktops too — resuming exactly where you left off after a power outage (if on a UPS) or after needing to move equipment. For desktops: ensure the PSU provides adequate power during the hibernate write (the system is active and writing to disk during the initial hibernate sequence before powering off). PSUs that aggressively reduce power during what appears to be shutdown can interrupt the hibernate write.
Hibernate and BitLocker
BitLocker-encrypted drives and hibernate interact correctly on most configurations, but BitLocker’s key management can occasionally cause slow resumes from hibernate or failures to resume. If hibernate resumes consistently but shows a long pause before displaying the login screen: BitLocker’s TPM authentication during resume is the likely cause. This is normal behaviour and not a failure; it can be slightly optimised through BitLocker’s startup settings (using PIN at startup instead of TPM-only) but the delay is architecturally expected.
Reducing hiberfil.sys size to free disk space
If hibernate is necessary but disk space is limited: reduce the hiberfil.sys allocation. Administrator Command Prompt:
powercfg /hibernate /size 40
This reduces the file to 40% of RAM. The system dynamically manages what fits — if RAM usage at hibernate time exceeds the allocated file size, Windows compresses data aggressively. The minimum effective size is typically 30-40% of RAM for typical workloads. Below this, hibernate fails when memory usage is high. Test at the chosen size with your typical workload before relying on it.
| Problem | Cause | Fix |
| Hibernate missing from power menu | Not enabled or not shown in settings | powercfg /hibernate on; show in Control Panel shutdown settings |
| Hibernate fails to complete | Disk full, driver incompatibility, or USB device | Free disk space; run powercfg /availablesleepstates; update drivers |
| Won’t wake from hibernate | GPU or driver resume failure | Update GPU driver; check Event Viewer at resume timestamp |
| Not available on this hardware | Modern Standby or BIOS restriction | Check BIOS; run powercfg /availablesleepstates for specific reason |
| Works for admin, not standard user | Group Policy restriction | Check Local Policy power management settings |
Hibernate is a powerful feature for workstation users who want to resume their entire session without keeping the machine running. The powercfg /availablesleepstates command is the single most informative diagnostic step — it tells you directly whether the hardware supports hibernate and, if not, exactly why. From there, the fix is almost always either enabling hibernate (if the hardware supports it but Windows has it off), or addressing the specific driver or disk space issue the command identifies.
For users deciding between sleep and hibernate: hibernate saves battery completely (zero power draw) but takes longer to resume (typically 10-30 seconds longer than waking from sleep). Sleep is faster but draws a small amount of power. For machines left inactive for hours or overnight: hibernate is the more power-efficient choice. For machines left inactive for 30 minutes during a meeting: sleep is more convenient. Configuring both — sleep for short inactivity, hibernate after extended inactivity — is possible through Power & Sleep settings (Settings → System → Power & battery) and gives the best of both behaviours automatically.
Hibernate after a Windows upgrade
Hibernate failures that started immediately after a Windows 11 major update are usually caused by the update changing power management defaults or installing a generic driver that replaced a manufacturer-specific one with better hibernate support. After an update that breaks hibernate: check Device Manager for any drivers that changed from a manufacturer-specific to a Microsoft-provided generic version → find and reinstall the manufacturer’s driver for those devices → test hibernate again.
One genuinely useful but little-known powercfg command for hibernate troubleshooting:
powercfg /sleepstudyThis generates an HTML report in the current directory showing a detailed history of all sleep and wake events, battery drain, and any failures during power state transitions. If hibernate has been failing intermittently: the sleep study report shows every failure with timestamps and device names, making it much easier to identify patterns (always fails at midnight? always fails when a specific USB device is connected?) than investigating Event Viewer manually.
To wrap up: hibernate is one of Windows’ less visible features that works quietly for years and then suddenly fails — usually because a driver update or Windows update changed something in the power management stack. The powercfg commands in this guide (particularly /availablesleepstates and /sleepstudy) provide the specific diagnostic information that makes the fix obvious rather than requiring trial-and-error across multiple settings and drivers. Hibernate is worth getting right; the ability to resume a complex work session instantly rather than spending 10 minutes reopening applications and documents is a meaningful productivity benefit. See also VPN Slow Internet for a related case.
