Windows power plans: what balanced, performance and efficiency change
How power schemes map to processor and device settings, what the Windows power slider does, and when a custom plan is worth it.
- Build
- 26300.9457 / 26100.33650
- Edition
- Pro (26H2) / Server
- Architecture
- x64
- Support
- Documentation (E1)
- Evidence
- E1Official documentation
- Verified
- 2026-10-29
- Page type
- Concept
The short answer
Section titled “The short answer”A power plan is a bundle of settings, not a performance switch. It contains:
- processor minimum/maximum state and boost behaviour,
- PCIe link state power management,
- USB selective suspend,
- disk/idle timers,
- wireless adapter power saving,
- display and sleep timeouts.
“High performance” mostly means do not let the CPU idle down and do not suspend devices. That is why it raises idle power and heat, and why it rarely raises peak performance on a modern laptop.
What the slider does on Windows 11
Section titled “What the slider does on Windows 11”The Settings → System → Power & battery → Power mode slider (Best power efficiency / Balanced / Best performance) is not the same as the classic plan list. On modern devices it adjusts processor performance boost mode and energy preference on top of the active plan.
- Best power efficiency — lower boost, aggressive idle.
- Balanced — default.
- Best performance — higher sustained boost, more heat.
On a laptop, this slider and the plan interact; changing one does not show up in the other’s UI.
Inspect the real settings
Section titled “Inspect the real settings”# list plans (GUID + name)powercfg /list# show every setting in the active plan, with current AC/DC valuespowercfg /query SCHEME_CURRENT# processor-specific subgrouppowercfg /query SCHEME_CURRENT SUB_PROCESSORSettings are identified by GUIDs; powercfg /query prints the friendly names alongside them. Look for:
| Setting | Effect |
|---|---|
| Processor performance boost mode | how aggressively clocks exceed base |
| Minimum processor state | prevents downclocking when >0% |
| Processor power efficiency policy | core parking / frequency preference |
| PCI Express link state power management | L0s/L1 latency vs power |
| USB selective suspend | device sleep |
Common misconceptions
Section titled “Common misconceptions”| Claim | Reality |
|---|---|
| “High performance = more FPS” | Usually no change; GPU-bound games ignore CPU clocks |
| “Balanced throttles the CPU” | It idles down when there is no work — that is the point |
| “Ultimate Performance is best” | It disables idle states; on laptops it means heat and battery drain |
| “Power plans don’t matter on desktops” | For idle power/noise, they do; for peak performance, rarely |
When a custom plan is justified
Section titled “When a custom plan is justified”- Always-on desktop: minimum processor state 5%, max 100%, sleep never, disk never — predictable.
- Server: high performance is the sensible default (no idle-state latency surprises), and Windows Server exposes a power plan with that intent.
- Laptop on battery: balanced with a lower max state extends runtime noticeably; a custom plan saves you from hunting settings.
- Audio/latency work: disabling USB selective suspend and PCIe ASPM reduces glitches.
# create and configure a plan (example: always-on desktop)powercfg /duplicatescheme SCHEME_MINpowercfg /change standby-timeout-ac 0powercfg /change disk-timeout-ac 0powercfg /setacvalueindex SCHEME_CURRENT SUB_PROCESSOR PROCTHROTTLEMIN 5powercfg /setactive SCHEME_CURRENTServers are different
Section titled “Servers are different”Windows Server ships a High performance plan by default in most installs, because idle-state transitions add latency to networking and storage. Do not “optimise” it to balanced to save power on a machine that exists to serve requests.
Related
Section titled “Related”Lab boundary
Section titled “Lab boundary”E1. Plan settings are documented by Microsoft and exposed through powercfg. The lab’s virtual machines expose a reduced power configuration, so no runtime or temperature comparison was made.