Before applying a Windows sleep or hibernation fix, check what the computer actually supports. The read-only powercfg /availablesleepstates command reports available sleep states and attempts to explain unavailable ones. Its short alias is powercfg /a. This answers a capability question, not whether yesterday’s sleep session worked correctly.
A missing Hibernate menu item, a computer that never sleeps, and a computer that immediately wakes are different symptoms. Collecting the right evidence first prevents unnecessary registry edits, power-plan resets and firmware experiments.
Run the capability check without changing settings
Open Command Prompt or a PowerShell tab in Windows Terminal. Run the following command and read the entire response, including explanations below unavailable states:
powercfg /aRecord the exact wording rather than summarising everything as sleep unsupported. Note the PC model, Windows version, whether it is a physical computer or a virtual machine, and the symptom you are investigating. The host used for remote administration may not be the device with the problem, so make sure the command runs on the affected Windows installation.
If access is denied, follow your organisation’s process for an elevated diagnostic session. Do not disable protections to run it. The command is an inspection, not a repair; a successful response does not alter the power plan or switch hibernation on.
Separate available states from unavailable reasons
Look first at the states listed as available. Then pair each unavailable state with its accompanying reason. A reason that points to firmware support calls for a different enquiry from one that says hibernation has not been enabled. Keep these lines together when sending a support ticket.
Do not assume every PC should present the same list. Device design and its current configuration matter. If your output mentions S0 low-power idle while another machine lists S3, copying the other machine’s settings is not evidence of a compatible repair. Ask the manufacturer or your IT team which sleep design is supported for your exact model and firmware.
Microsoft states that the command attempts to report reasons. That wording matters: an incomplete explanation is not permission to guess which component failed. Preserve the output and obtain device-specific guidance before considering firmware changes.
Check hibernation separately from Fast Startup
The powercfg reference distinguishes enabling hibernation from selecting the hibernation-file type. It specifically states that a reduced hibernation file supports only hiberboot. Therefore, a discussion of Fast Startup does not by itself establish that full hibernation is available for the user’s session.
If the output says hibernation is unavailable, ask support to review the exact reason alongside the intended configuration. Do not blindly copy commands that disable hibernation, resize its file or change its type. Those are write operations with consequences beyond this diagnostic check, and a managed computer may intentionally use a particular configuration.
For example, imagine a fictional support ticket saying, ‘Fast Startup appears enabled, but Hibernate is not offered.’ The useful follow-up is the complete capability output and the intended device policy, not a claim that the storage drive must be faulty. The command reference supports a distinction between features; it does not diagnose this imagined machine.
Choose the next check from the actual symptom
A supported state exists, but the computer will not automatically sleep: investigate application or driver power requests. Microsoft documents powercfg /requests for enumerating requests that can prevent low-power sleep or display-off behaviour. The related tutorial on finding what keeps Windows awake explains how to collect that separate evidence without immediately overriding it.
The computer sleeps and then wakes: capability output is not a wake history. Microsoft’s powercfg /lastwake reports information about the last sleep transition’s wake event, while powercfg /waketimers enumerates active wake timers. Our wake-timers versus last-wake walkthrough helps distinguish these questions.
Battery use seems high during standby: record the supported sleep design and the observed time period. The reference documents SleepStudy as a Modern Standby quality report, not a universal substitute for every sleep diagnosis. Confirm that the report fits the device before asking for one.
Support checklist and short FAQ
- Keep the full available-state list and each unavailable-state reason.
- Describe one reproducible symptom rather than combining unrelated power complaints.
- Include device model, Windows version and recent approved changes.
- Ask whether the intended configuration matches manufacturer and organisational guidance.
- Leave power-plan, registry and firmware changes outside this read-only check.
Do I need to enable every state? No. An unavailable state is not automatically a fault, and supported configurations differ.
What is the rollback? None is required for the inspection command because it changes no power settings. If later repairs are approved, record their original values and rollback procedure separately.
Source: Microsoft Learn powercfg command-line options, particularly available sleep states, hibernation-file types, requests and wake reporting.
Safety: This tutorial is for educational purposes. Test carefully before using steps in production. The site owner is not responsible for misuse, damage, data loss or production issues. Follow workplace device policies and obtain approval before configuration changes.
