# 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.

**Tested on**

- Build: 26300.9457 / 26100.33650
- Edition: Pro (26H2) / Server
- Architecture: x64
- Evidence: E1
- Verified: 2026-10-29

## 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

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

```powershell
# list plans (GUID + name)
powercfg /list
# show every setting in the active plan, with current AC/DC values
powercfg /query SCHEME_CURRENT
# processor-specific subgroup
powercfg /query SCHEME_CURRENT SUB_PROCESSOR
```

Settings 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

| 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

- **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.

```powershell
# create and configure a plan (example: always-on desktop)
powercfg /duplicatescheme SCHEME_MIN
powercfg /change standby-timeout-ac 0
powercfg /change disk-timeout-ac 0
powercfg /setacvalueindex SCHEME_CURRENT SUB_PROCESSOR PROCTHROTTLEMIN 5
powercfg /setactive SCHEME_CURRENT
```

> **Caution: Do not disable idle states on a laptop**
>
> Setting minimum processor state to 100% on a laptop is the fastest way to make it hot, loud and short-lived on battery. If you need sustained performance, raise the power mode, not the idle floor.

## 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

- [Throttling: thermal or power](https://winbook.fyi/en/hardware/laptop/throttling/)
- [Modern Standby](https://winbook.fyi/en/hardware/laptop/modern-standby/)
- [Cores or clock](https://winbook.fyi/en/hardware/cpu/cores-vs-clock/)

## 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.

## Sources

- [Microsoft Learn — Powercfg command-line options](https://learn.microsoft.com/en-us/windows-hardware/design/device-experiences/powercfg-command-line-options)
- [Microsoft Learn — System power states](https://learn.microsoft.com/en-us/windows/win32/power/system-power-states)

---

Source: https://winbook.fyi/en/hardware/laptop/power-plans/