Fix ERROR_VOLSNAP_HIBERNATE_READY 0x000002F9

What's going on here?

You tried to hibernate your Windows PC or laptop, and you got this: ERROR_VOLSNAP_HIBERNATE_READY (0X000002F9). The message says "The system is now ready for hibernation" but then nothing happens, or you're stuck with a black screen or an error pop-up.

I see this most often after a forced shutdown — like when your laptop ran out of battery, or you held the power button to shut it down. It can also happen right after a big Windows Update, or if you have backup software that's making a Volume Shadow Copy snapshot.

The real problem: Windows is waiting for a Volume Shadow Copy snapshot to finish. It's a kind of safety lock. The system won't hibernate until that snapshot is closed. But sometimes the snapshot gets stuck. Here's how to break the lock.

Fix 1: The 30-second fix — just reboot

This sounds simple, but it works more often than you'd think. A normal restart clears the stuck snapshot.

1. Save any open files.
2. Click Start > Power > Restart. Not Shut Down. Restart.
3. Wait for Windows to fully reload.

After the restart, try hibernating again. Go to Start > Power > Hibernate. If it works, you're done. If you still see the error, move to Fix 2.

Fix 2: The 5-minute fix — disable and re-enable hibernation

This forces Windows to drop all pending snapshots and recreate the hibernation file. You'll need to open Command Prompt as admin.

1. Press the Windows key and type cmd.
2. Right-click Command Prompt and choose Run as administrator. Click Yes on the User Account Control pop-up.
3. Type this command and press Enter:

   powercfg /h off

   You won't see any message, but the command ran silently. If you get an error like "Access denied", double-check you're running as admin.

4. Close the Command Prompt window.
5. Restart your computer. Do not skip this restart. It clears the stuck snapshots.
6. After Windows comes back, open Command Prompt as admin again.
7. Type this command and press Enter:

   powercfg /h on

8. Close the Command Prompt.
9. Try hibernating now. Go to Start > Power > Hibernate.

If the error is gone, you're all set. If not, we need to dig deeper.

Fix 3: The 15-minute fix — check for stuck VSS writers

The Volume Shadow Copy service can have "writers" that get stuck — like your system restore or backup software. We'll check and restart them.

Step 3a: Run a VSS diagnostic

1. Open Command Prompt as admin (same way as before).
2. Type this command and press Enter:

   vssadmin list writers

   You'll see a long list of writers. Look for any that say State: [1] Stable or State: [5] Waiting for completion. If you see State: [9] Failed, that's the culprit.

   Here's an example of a failed writer:

   Writer Name: 'System Writer'
      Writer Id: {something}
      Writer Instance Id: {something}
      State: [9] Failed
      Last error: No error

   If you see any failed writer, write down its name. Then go to Step 3b.

3. If all writers show Stable, still run the next command anyway — I've seen cases where the list looks fine but the service is hung.

Step 3b: Restart the Volume Shadow Copy service

1. Press Windows key + R, type services.msc, and press Enter.
2. Scroll down until you find Volume Shadow Copy. Right-click it and select Restart. If Restart is grayed out, click Stop, wait 10 seconds, then click Start.
3. Close the Services window.
4. Restart your computer.

Step 3c: (If still failing) Disable backup software temporarily

Backup tools like Acronis, Macrium Reflect, or even Windows Backup can hold snapshots open. If you have any backup software:

1. Right-click its icon in the system tray (near the clock) and choose Exit or Quit.
2. Open Task Manager (Ctrl + Shift + Esc), find any processes from that software, and End Task them.
3. Try hibernating again.

If it works now, you know the backup software was the problem. You can re-enable it after your next normal shutdown.

What if nothing works?

I've only seen a few cases where none of these fixes helped. In those rare cases, the problem was a corrupt hibernation file or a driver issue. Here's the nuclear option:

1. Boot into Safe Mode. To do that: hold the Shift key while clicking Restart from the Start menu. Then go to Troubleshoot > Advanced options > Startup Settings > Restart. After the restart, press 4 for Safe Mode.
2. In Safe Mode, open Command Prompt as admin.
3. Run:

   powercfg /h off

4. Restart normally.
5. Then re-enable hibernation with powercfg /h on.

If even that fails, you might have a failing disk or a corrupt system file. Run sfc /scannow from an admin Command Prompt — it checks for corrupted Windows files and fixes them. That's a last resort, but it has saved me more than once.

Final thought

This error is annoying but not dangerous. Your data is safe — Windows just won't let you hibernate until the Volume Shadow Copy is done. Most people fix it with the simple restart or the powercfg command. Try those first. You'll be back to normal in under 5 minutes.