Sleep or Hibernate Missing From Power Menu? Fix (11/10)

Open Command Prompt as administrator and run one command. It will tell you the exact reason, in a sentence, and you can stop hunting through Settings:

powercfg /a

It prints the sleep states your PC supports, and then — the useful part — every state it cannot use and why. "The system firmware does not support this standby state." "The current Device Guard configuration has disabled this standby state." "The hypervisor does not support this standby state."

That is your answer. Not a setting to find, an explanation.

And the most common modern reason is one nobody expects: a security feature you turned on. Core isolation and memory integrity rely on virtualization, and traditional sleep cannot coexist with it on many machines. Windows removes the option rather than offering one that would fail — without ever mentioning that it is making that trade on your behalf.

For Hibernate, the story is different and there is a second thing worth knowing: hibernate and Fast Startup are the same feature. Which means switching one off quietly costs you the other.

The Security Setting That Took Sleep Away

A customer came into Jake's shop because the Sleep option had disappeared from his laptop's power menu. Shut down and Restart were there. Sleep was simply gone, and closing the lid now did nothing useful.

He had done the reasonable things. He had been through Power Options twice, checked the lid-close behavior, updated Windows, and found several forum threads recommending registry edits he had sensibly declined to run.

Jake ran powercfg /a, which took about four seconds, and the machine explained itself:

Standby (S3)
    The current Device Guard configuration has disabled this standby state.

Three weeks earlier, prompted by a Windows Security notification, the customer had switched on memory integrity under Core isolation. It was the right thing to do — the notification had recommended it and it genuinely improves security.

Nothing warned him it would cost him Sleep. Windows made the trade and removed the option, and the two events were three weeks apart, so nobody would have connected them.

Ethan, when Jake described it: "That's a legitimate design decision reported terribly. Windows knows exactly why sleep is gone — it'll tell you in one line if you ask with the right command. It just won't tell you in the place you're actually looking, which is the Settings page with the missing option on it."

The customer chose to keep memory integrity and use Hibernate instead, which was the right call for him. But it was his call to make, and he had spent three weeks not knowing there was a choice.

Reading What the Command Tells You

Press the Windows key, type cmd, choose Run as administrator, and run powercfg /a. You get two lists: the states available on this system, and the states that are not, each with its reason.

What it says	What it means	What you can do
Device Guard configuration has disabled this state	Core isolation or memory integrity is on	A real trade-off — decide deliberately
The system firmware does not support this state	Your hardware never offered it, or it is off in the BIOS	Check firmware setup. Recent CPUs dropped S3 entirely.
The hypervisor does not support this state	Hyper-V, WSL2 or VM software is running underneath Windows	Disable the one you do not need, or accept it
Hibernation has not been enabled	Someone turned it off, often to reclaim disk space	One command puts it back
Standby (S0 Low Power Idle) is listed as available	You have Modern Standby. S3 was never part of this machine.	Nothing. Sleep works, differently. Explained below.

Take the reason literally. It is the single most reliable statement you will get about this problem, and it is more trustworthy than any general guide — including this one — because it is describing your machine rather than machines in general.

The most common answer on a recent PC is the first row, and it deserves a proper explanation rather than a workaround.

The Security Trade Nobody Mentions

Core isolation and its memory integrity setting are genuinely valuable protections. They run parts of Windows inside a virtualized container so that even malicious code with deep access cannot reach them. Windows Security recommends switching memory integrity on, and that recommendation is sound.

What it does not say is that virtualization and the traditional S3 sleep state cannot coexist on many machines. Once memory integrity is on, S3 becomes unavailable, and Windows removes the Sleep option rather than presenting a button that would fail.

So you have a real choice, and it is worth making it deliberately:

Keep memory integrity and lose S3 sleep. Reasonable on most machines, especially if Modern Standby is available or you are willing to use Hibernate instead. Hibernate uses no power at all and restores your open work, which is arguably better than sleep for anything left overnight.

Turn memory integrity off and regain sleep. Defensible on a desktop that sleeps constantly, and it does mean giving up a meaningful protection. If you decide that is the right trade for your machine:

1. Open Windows Security from the Start menu.
2. Choose Device security, then Core isolation details.
3. Turn Memory integrity off. Windows will warn you, and the warning is accurate rather than boilerplate.
4. Restart. The change does not take effect until you do.
5. Run powercfg /a again and confirm the state now appears in the available list. If it still does not, memory integrity was not the cause and you should turn it back on.

Step five matters more than it looks. If you disable a security feature and the problem persists, you have given something up for nothing — so check, and put it back if it made no difference.

Ethan's advice to Jake's customer, which is the honest version rather than the safe one: "Keep the security and use Hibernate. You're closing the lid on a laptop overnight — hibernate costs you four seconds when you open it and no battery at all. You'd be trading a genuine protection for four seconds, and that's a bad trade even when the four seconds annoy you."

The same logic applies to the hypervisor row. If powercfg blames a hypervisor and you actively use WSL2, Hyper-V or virtual machines, sleep is the smaller loss.

When Sleep Was Never There to Lose

If powercfg /a lists Standby (S0 Low Power Idle) as available and S3 as unsupported by firmware, your machine uses Modern Standby, and it never had traditional sleep.

The two work quite differently. S3 cut power to almost everything and the machine was properly unconscious. Modern Standby keeps it lightly awake — screen off, most things paused, but able to collect mail and messages, rather like a phone. Recent processors have dropped S3 entirely, so this is simply what sleep is now on newer hardware.

Two things follow that are worth knowing rather than fighting.

Your machine uses a little battery while asleep, and occasionally more than a little if something keeps waking it. A laptop that loses noticeable charge overnight in a bag is usually a Modern Standby machine being woken by network activity, which is a real complaint with real fixes rather than something to blame on the missing S3.

And some firmware lets you choose. A few machines offer S3 versus Modern Standby in the BIOS setup, often under a sleep-state or S3-support entry. If it is there, you can switch. Most newer machines do not offer it, and on those the state genuinely cannot be enabled by any means.

Getting Hibernate Back

Hibernate goes missing for a simpler reason than sleep: somebody turned it off. It takes two steps to restore, and doing only the first is why people conclude it did not work.

1. Enable the feature. Administrator Command Prompt: powercfg /hibernate on. No output means it worked. This recreates the hibernation file on your disk.
2. Make the menu entry appear. Open Control Panel, choose Power Options, then Choose what the power button does on the left.
3. Click "Change settings that are currently unavailable." This is the step everybody misses. It is a small link near the top and it does not look like a button, and until you click it every checkbox below is locked.
4. Under Shutdown settings, check Hibernate. Also check Turn on fast startup while you are there.
5. Click Save changes and open the Start menu's power button. Hibernate is back.

If Hibernate is absent from that Shutdown settings list rather than merely locked, step one did not take — run powercfg /a and check whether it reports hibernation as unavailable and why.

On Windows 11, Search Sends You to the Wrong Page

The steps above are identical on Windows 11. Same commands, same Control Panel page, same locked checkboxes. If you have already done them, you are finished — this section exists because of what happens when you try the obvious thing first.

The obvious thing is to click the search box on the taskbar and type hibernation. On Windows 11 that returns a result called Remote Desktop Hibernation Settings, and opening it drops you into a page about remote sessions that has nothing to do with your power menu. Nothing on the way in warns you, and nothing on the page tells you that you have arrived somewhere unrelated.

That is a search-result problem, not a mistake on your part. Windows 11 moved most of the Control Panel's power settings behind Settings, but not the Shutdown settings checkboxes, and the search index never learned that the thing people actually want still lives in the old place. So it offers the closest name it can find.

Ethan lost most of an evening in that page before he thought to check whether it was the right one at all, and he is not a careless person — he is someone who typed a word into a search box and trusted the answer, which is the whole point of a search box.

The reliable route on Windows 11 skips search entirely. Press Windows + R, type powercfg.cpl, press Enter, then click Choose what the power button does. That opens the correct page directly, on both Windows 11 and Windows 10, and it cannot be misdirected because you are naming the page rather than describing it.

Hibernate and Fast Startup Are the Same Feature

This one catches careful people, because it punishes a sensible decision.

Fast Startup is what makes modern Windows machines start in seconds. When you shut down, it saves part of the system state to disk and reloads it at power-on rather than starting everything from scratch.

It saves that state into the hibernation file. Fast Startup is, mechanically, a partial hibernation.

So powercfg /hibernate off — which people run to reclaim several gigabytes of disk space, and which plenty of guides recommend — also removes Fast Startup. The option vanishes from that Shutdown settings page entirely, and every boot from then on is slower. Nothing tells you that is what happened, and the disk space arrives immediately while the slower boots are only noticeable in hindsight.

If disk space is the real problem, shrink the file instead of removing it:

powercfg /hibernate /size 40

That reduces the hibernation file to around 40 percent of its default size. You keep Fast Startup, you keep hibernation working in most cases, and you recover most of the space. It is the answer the "disable hibernation" advice should have been.

Our guide on turning Fast Startup on or off covers the other side of this — including the cases where you genuinely want it off, such as dual-booting or troubleshooting, since a shutdown with Fast Startup on does not fully restart anything.

The Remaining Causes

Situation	Cause	Fix
powercfg says the state is available, menu still missing	Group Policy is removing the entry	Common on work machines and intended. Ask your IT team.
Vanished right after a Windows update	A generic display driver replaced the manufacturer's	Roll the driver back, or install the maker's version
Power plans look wrong generally	The power configuration is damaged	powercfg /restoredefaultschemes as administrator
Sleep is there but the machine wakes immediately	A device is permitted to wake it	powercfg /lastwake names the culprit
Power button itself missing from the sign-in screen	A shared-PC policy, not a power problem at all	Different lane — see the guide linked below

Row two is worth pairing with the wider pattern: a Windows update replacing a manufacturer driver with a generic one causes several apparently unrelated faults, and slow startup is another of them. Our post on slow boots after a driver update covers the same mechanism from the other direction.

Row five is a genuinely different problem that gets searched with the same words — if the whole power button is absent from the sign-in screen rather than one option missing from the menu, our guide to the missing power button on the login screen is the one you want.

What This Page Said Before, and What It Covers Now

The original version of this post went up in December 2016 and gave the Control Panel steps for putting Sleep back into the power menu. Those steps were right, and they are still here.

What it could not do was tell you whether they would work for you, because it never asked what had removed the option in the first place. A reader whose sleep state had been disabled by firmware or by a security feature would follow every step correctly and find the checkbox still absent, with nothing on the page to explain why.

That is the gap the powercfg /a section fills, and it is why the diagnosis now comes before the instructions rather than after them.

This page has also been widened deliberately. We had written about sleep going missing and hibernate going missing as separate topics over the years, on several different pages, which was never a helpful way to divide it — the two share a cause, share a fix, and are frequently missing together. So this page now covers both, along with the Fast Startup connection that ties them, and it is the one to bookmark for any option that has vanished from the power menu.

Your Questions, Answered Straight

Why has the Sleep option disappeared from my power menu?

Because Windows hides options the machine cannot currently perform. Something has made the sleep state unavailable, and one command names it: open Command Prompt as administrator and run powercfg /a. It lists which states are available and, for each one that is not, states the exact reason.

What does powercfg /a actually tell me?

It prints the sleep states your system supports, then a second list of those it does not, each with a reason. Common reasons are that the system firmware does not support the state, that the current Device Guard configuration has disabled it, or that a hypervisor is present. That sentence is your diagnosis.

Why did Sleep vanish after I turned on a security feature?

Because Core isolation and memory integrity rely on virtualization, and the traditional S3 sleep state cannot coexist with it on many machines. Windows disables S3 rather than offering something that would fail. It is a genuine trade-off between that protection and old-style sleep, and nothing in Settings tells you it is being made.

Does my laptop still sleep if S3 is unavailable?

Usually yes, through Modern Standby instead. Most laptops sold in recent years never had S3 at all — they use a low-power idle state where the machine stays lightly awake to sync mail and messages. Sleep works, it simply works differently, and on those machines the missing S3 is not a fault to fix.

How do I get Hibernate back in the power menu?

Open Command Prompt as administrator and run powercfg /hibernate on. Then open Control Panel, Power Options, Choose what the power button does, click Change settings that are currently unavailable, and check Hibernate under Shutdown settings. Both halves are needed — the command makes it possible, the checkbox makes it appear.

Why is the Hibernate checkbox unavailable in Control Panel?

Because you have not clicked Change settings that are currently unavailable at the top of that page. Those checkboxes are deliberately locked until you do, and the link is easy to miss because it does not look like a button. If Hibernate is absent entirely rather than locked, run powercfg /hibernate on first.

Are Hibernate and Fast Startup the same thing?

They are the same underlying feature. Fast Startup is a partial hibernation — it saves the system state to the same file and reloads it at power-on. Turn hibernation off and Fast Startup disappears too, because there is nothing left for it to use. That surprises people who disabled hibernation to reclaim disk space.

How much disk space does hibernation use?

The hibernation file is normally a substantial fraction of your installed memory, so a machine with plenty of RAM gives up several gigabytes. You can shrink it with powercfg /hibernate /size 40 rather than switching hibernation off entirely, which keeps Fast Startup working while reclaiming most of the space.

The command says my firmware does not support the state. Can I fix that?

Sometimes, in firmware settings rather than in Windows. Some machines offer a choice between Modern Standby and S3 in the BIOS setup, often under a sleep-state or S3-support entry. Many newer ones do not, because recent processors dropped S3 entirely. If the option is not there, the state genuinely cannot be enabled.

Why would a hypervisor stop sleep working?

Because Hyper-V and virtualization-based security run underneath Windows and hold hardware in a state the old sleep model cannot handle. If powercfg reports a hypervisor is present, look for Hyper-V, WSL2, virtual machine software or memory integrity being enabled. Turning the relevant one off restores the state, at the cost of whatever it provided.

Can Group Policy hide the Sleep option?

Yes, and it is common on work machines. A policy can remove Sleep, Hibernate or Shut down from the power menu regardless of what the hardware supports. If powercfg reports the state as available while the menu entry is still missing, policy is the likely explanation and your IT team is the right place to ask.

Sleep disappeared right after a Windows update. What changed?

Usually a display driver. The update replaced the manufacturer's driver with a generic one that does not declare support for the sleep state, so Windows withdraws the option. Roll the driver back, or install the version from your laptop maker's support page rather than the chipset vendor's generic package.

Is it worth using hibernate at all on a modern PC?

On a laptop you carry between places without charging, yes — it uses no power at all and restores your open work. On a desktop with an SSD, the practical difference between hibernating and shutting down is small enough that most people will not notice. Keep it enabled anyway, because Fast Startup depends on it.

Will enabling hibernation slow my computer down?

No, it speeds startup up, because Fast Startup uses it. The only cost is the disk space taken by the hibernation file. If that space matters more than the boot time, shrink the file rather than disabling the feature, so you keep the faster start.

Does this apply to Windows 11 as well as Windows 10?

Yes. The powercfg commands, the Control Panel page and the shutdown settings checkboxes are identical on both. Windows 11 is more likely to be running on hardware that uses Modern Standby rather than S3, which is why the missing-sleep question comes up more often on newer machines.

Nothing works and the option is still missing. What now?

Read the powercfg /a output once more and take the reason literally rather than looking for a workaround. If it says firmware or hypervisor, the answer is in firmware settings or in what you have enabled, not in Windows. If it reports the state as available and the menu still lacks it, that is policy or a damaged power configuration, and powercfg /restoredefaultschemes resets the latter.

Worth Reading Next

Revision note. Originally published December 2016 as a Control Panel walkthrough for restoring Sleep. Rewritten August 22, 2026 for Windows 11 and Windows 10, and widened to cover Hibernate as well — the two share a cause and a fix, and splitting them across separate pages never served anyone looking for either. What is new: the powercfg /a diagnosis that names the exact reason before you change anything, the Core isolation trade-off that removes sleep without telling you, Modern Standby on machines that never had S3, and the fact that hibernate and Fast Startup are the same feature so disabling one costs you the other. If your machine reports something the table above does not cover, please write in with the powercfg /a output — that text is almost always the whole answer. And if you have spent an evening looking for a checkbox: on most machines it was never a checkbox, and there was no way to know that from the screen you were looking at.