A hot laptop with a screaming fan, or a desktop that idles all night at near-full power, usually traces back to one setting: maximum processor state. Here's where it lives in Windows 11 and 10, the powercfg PROCTHROTTLEMAX command that sets it instantly, how it also disables turbo boost, and why the cap you set today can quietly disappear the next time you switch power plans.
Quick answer: Control Panel → Power Options → Change plan settings → Change advanced power settings → Processor power management → set "Maximum processor state" below 100% — try 70%. Prefer a command line? powercfg /setacvalueindex scheme_current sub_processor PROCTHROTTLEMAX 70 then powercfg /setactive scheme_current to apply it. Read on for the turbo boost connection, why the cap doesn't survive a plan switch, and how to make it stick.
Unlike the sleep timeout, this setting has never made it into the simple Settings app on either Windows version — it only lives in the classic Control Panel dialog:
As with sleep settings, laptops show separate On battery and Plugged in values; desktops only show plugged-in. A common setup is 100% plugged in for full performance, and 60–70% on battery to stretch runtime — but plenty of people cap both, all the time, just to keep things quiet.
powercfg writes the same value the advanced settings dialog does, and it's faster if you're doing this more than once. The number is a percentage (5–100); a value like 70 means "never sustain above 70% of rated clock speed." One step everyone skips: the value doesn't take effect just by writing it — you have to reactivate the plan.
| What you're changing | Plugged in | On battery |
|---|---|---|
| Max processor state | powercfg /setacvalueindex scheme_current sub_processor PROCTHROTTLEMAX 70 | setdcvalueindex scheme_current sub_processor PROCTHROTTLEMAX 60 |
| Min processor state | powercfg /setacvalueindex scheme_current sub_processor PROCTHROTTLEMIN 5 | setdcvalueindex scheme_current sub_processor PROCTHROTTLEMIN 5 |
| Apply the changes | powercfg /setactive scheme_current | |
That last command is easy to forget and it's why people report "I set it but nothing changed" — setacvalueindex and setdcvalueindex only write the number into the plan's storage. Reactivating the currently-active plan with setactive is what actually pushes it to the running system. Confirm it stuck with powercfg /query scheme_current sub_processor PROCTHROTTLEMAX.
Turbo boost (Intel Turbo Boost, AMD Precision Boost) is the chip briefly running above its base clock when there's thermal and power headroom. It only ever operates below the ceiling Windows enforces — so a 100% maximum processor state leaves turbo free to fire, and anything under 100% caps it out automatically, no separate toggle required. That's also where the disproportionate heat and fan noise live: the last slice of clock speed a modern CPU can reach draws far more power per unit of performance than the base clock does, so trimming even 20–30 percentage points off the ceiling removes most of the spike.
| You want to change… | Setting name | What it does |
|---|---|---|
| How fast the CPU is allowed to run, sustained | Maximum processor state | A hard ceiling; turbo can't exceed it |
| Whether turbo activates at all | Same setting, indirectly | Any value under 100% blocks it |
| Different caps for different situations | PowerDoze power modes | Windows resets the cap on plan switches; a mode reapplies it |
PROCTHROTTLEMAX is stored inside a specific power plan, not as a global Windows setting. That means it only survives as long as that plan stays active. Two things quietly undo it:
A game launcher's "performance mode," a GPU driver installer resetting plans, or you manually switching back to Balanced — any of these swaps which plan is active, and your cap only lived in the one you edited. If Balanced never had a cap, you're back to 100%.
Best for understanding: Why the same PC "used to be capped" and now isn't, with no error and no notification. Note: The reboot itself doesn't erase the value — it's the plan change that does.
scheme_current targets whatever plan is active right now — if you switch plans afterward, the new one never got the value. And as covered above, skipping powercfg /setactive scheme_current means the number was saved but never pushed to the running system.
Best for understanding: The "I definitely typed the command" case. Fix: Re-run against the plan you're actually using, and always follow with setactive.
Want the fan-noise angle in more depth — cooling policy, GPU limits, and the full "why is my PC loud" breakdown? See the three settings that quiet a PC.
Windows saves PROCTHROTTLEMAX, boost mode, and cooling policy per plan, with nothing to reapply them if the active plan changes or a driver install resets things. PowerDoze folds the CPU max/min, turbo boost switch, and cooling policy into a power mode you build once — set it to apply on startup, or attach it to a schedule, and it writes the same values back every time instead of you rediscovering the advanced settings dialog. A quiet mode capped at 70% for daily use, an uncapped mode for when you actually need the performance, switched with one click or automatically. Free for up to 2 custom power modes, no account required.
Honest note: Windows can do all of this on its own — the advanced power settings dialog has every one of these controls, they're just several menus deep and easy to lose track of after a plan reset. PowerDoze doesn't add new CPU control Windows doesn't have; it makes the setting you already have one click and persistent instead of something you rediscover every few weeks. Limit: Free tier caps at 2 modes; Pro removes it and adds automatic switching by app, Wi-Fi, and schedule.
Control Panel → Power Options → Change plan settings → Change advanced power settings → Processor power management → Maximum processor state, and set it below 100% (try 60–80%). Or from a command line: powercfg /setacvalueindex scheme_current sub_processor PROCTHROTTLEMAX 70 followed by powercfg /setactive scheme_current to make it take effect.
Set Maximum processor state to anything under 100% — turbo only ever activates below the ceiling you set, so a 100% cap with turbo left "on" still lets it run. For finer control, Processor power management → System cooling policy exposes a Boost Mode option (Disabled/Enabled/Aggressive) on some systems, though many Windows installs hide it from the advanced settings UI entirely.
powercfg /setacvalueindex scheme_current sub_processor PROCTHROTTLEMAX 70 sets the plugged-in cap to 70%; swap setacvalueindex for setdcvalueindex to set the on-battery value. Run powercfg /setactive scheme_current afterward — writing the value alone doesn't apply it until the plan is reactivated.
Yes, and disproportionately. A CPU's last slice of clock speed — the turbo range — draws far more power per unit of performance than the base clock does. Cutting the ceiling to 70–80% removes most of that spike while leaving everyday tasks like browsing, video, and office work feeling unchanged.
PROCTHROTTLEMAX is stored per power plan, not globally, so switching plans — or Windows Update quietly resetting a plan — reverts it. A reboot alone won't erase a value saved to the active plan, but anything that changes the active scheme (a game launcher's performance mode, a driver installer, a manual switch back to Balanced) will. Nothing reapplies the cap automatically unless you set that up yourself.
No — CPU max/min state and turbo boost are part of power modes, which are free for up to 2 custom modes with no account required. Pro removes that limit and adds automatic switching by app, Wi-Fi network, and schedule.
Want a quiet CPU cap that reapplies itself instead of resetting every time you switch power plans? Power modes are free, up to 2 modes, no account required.
Download free for Windows 10/11See also: Cap GPU power draw on Windows · The three settings that quiet a PC · Change when Windows sleeps · All features