Hibernation Failure 0x00000290: The Real Fix
Your PC won't hibernate and throws error 0x290. Nine times out of ten it's a driver or power setting issue. Here's how to nail it fast.
Yeah, That Error Sucks
You click hibernate, wait a few seconds, and boom — error 0x00000290 with a message that says the system failed to hibernate. I've seen this on Dell Latitudes, ThinkPads, and home-built rigs. The culprit here is almost always a misconfigured power setting or a driver that doesn't play nice with sleep states.
The Fix That Works 90% of the Time
Skip the registry tweaks and BIOS resets for now. Start here.
Step 1: Kill Fast Startup
Fast Startup is a hybrid shutdown feature that often stomps all over hibernation. Disable it.
- Open Control Panel → Power Options → Choose what the power buttons do.
- Click Change settings that are currently unavailable (you need admin rights).
- Uncheck Turn on fast startup (recommended).
- Click Save changes and reboot.
Step 2: Run Powercfg to Reset Hibernation
Open a command prompt as admin. Then run these commands:
powercfg /h off
powercfg /h onThis tears down the hibernation file entirely and rebuilds it fresh. I've fixed a dozen machines with just this one-two punch.
Step 3: Check for Driver Conflicts
If the error persists, look at your graphics and chipset drivers. Outdated NVIDIA or AMD display drivers are notorious for blocking hibernation. Also check storage drivers — Intel RST (Rapid Storage Technology) has caused this on recent laptops.
Update via the manufacturer's site, not Windows Update. For Intel RST, try rolling back to a version from 2021 or earlier if the latest breaks things.
Why This Works
Fast Startup essentially uses the hibernation file to boot faster — but it holds a lock on it. When you try to hibernate normally, the system can't write a new hibernation file because the old one is still reserved. Disabling Fast Startup releases that lock. The powercfg reset clears any corruption in the hibernation file itself, and updating drivers removes the last common roadblock.
Less Common Variations of the Same Issue
Sometimes the problem is deeper. Here's what else I've seen cause 0x00000290:
Hybrid Sleep Enabled
If Hybrid Sleep is on, it can conflict with hibernation. In Power Options → Advanced settings, find Sleep → Allow hybrid sleep and set it to Off.
Third-Party Power Management Software
Lenovo Vantage, Dell Power Manager, and HP Support Assistant often override Windows power settings. Uninstall or disable any custom power management tool temporarily. If that fixes it, configure hibernation through that tool instead of Windows.
Corrupted System Files
Rare, but worth checking. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an admin command prompt. This catches the 1-in-50 cases where a system file got hosed.
BIOS/UEFI Settings
On older systems, look for S3 (Suspend to RAM) vs S4 (Hibernate) in the BIOS. If S3 is disabled, hibernate won't work. On modern UEFI systems, check that Fast Boot is disabled in the firmware — it's a separate setting from Windows Fast Startup.
How to Prevent This from Coming Back
- Leave Fast Startup off. It saves maybe 2 seconds on boot and causes endless sleep-related bugs.
- Keep your chipset and storage drivers updated. Set a monthly reminder to check manufacturer sites.
- After Windows feature updates, rerun
powercfg /h on. Major updates sometimes reset or corrupt the hibernation file. - Avoid using both Hibernate and Sleep interchangeably. Stick to one mode. Mixing them increases the chance of hitting this error.
That's it. Nine times out of ten, it's Fast Startup or stale drivers. Hit these steps in order, and you'll be back to hibernating without the 0x290 headache.
Was this solution helpful?