You're halfway through a video call. The room goes quiet, and right then your laptop fan spins up loudly — like a tiny hairdryer everyone on the call can hear. You wince and think: is this thing dying?
Relax. It's not broken. The real explanation is more subtle than "broken" — there's a setting buried in Windows, one nobody ever explains, quietly making this call for you: when things get hot, does the fan get loud first, or does the chip slow down first? And almost everyone assumes the opposite of what it actually does.
This post shows you what that setting actually controls, where it really matters, and the thing people worry about most — whether it'll trample the BIOS fan curve you spent hours tuning.
Heat has two exits
When a chip heats up, the system has exactly two moves: move the heat away faster (spin fans up), or make less heat (run the chip slower). The cooling policy is the priority order between them:
- Active: fans first. Windows ramps cooling to hold clock speeds — performance is protected, your ears pay.
- Passive: slowdown first. Windows reduces CPU speed to make less heat, and the fans stay as the last resort — silence is protected, peak speed pays.
So the real translation is: Active = "loud before slow", Passive = "slow before loud". For a night-time download box or a machine you're on a call next to, passive is the right default; for a render rig mid-job, active is.
Where to set it
GUI: Control Panel → Power Options → Change plan settings → Advanced → Processor power management → System cooling policy (separate values for plugged-in and on-battery). Command line: it's the SYSCOOLPOL setting under powercfg's processor subgroup. Or let a power mode carry it — more on that below.
The fine print: where this setting actually works
This is the part most guides skip. The cooling policy only matters where Windows itself manages the fans — which in practice means laptops and OEM prebuilts whose firmware exposes thermal control to the OS through ACPI. On a typical self-built desktop, your fans answer to the motherboard's BIOS fan curve. Windows never touches them, so the policy's "active" branch has nothing to steer; what remains effective is the throttling side, and you control that more directly with a CPU maximum cap. If you're tuning a self-built desktop for quiet, the cooling policy is a supporting actor — the CPU cap and GPU power limit are the leads.
"Will it fight my BIOS curve or Afterburner?"
A reader testing PowerDoze asked exactly this — he'd spent hours tuning a BIOS fan curve and an MSI Afterburner profile and didn't want either overwritten. The answer is reassuring and worth spelling out:
- BIOS fan curves are never touched. Windows' cooling policy (and PowerDoze) works on the heat-production side: CPU clocks, caps, boost. Your fans keep following the BIOS curve — and because less heat reaches the sensors, the same curve simply spins slower. The two compose; they don't compete.
- Afterburner coexists, with one shared knob. Fan curves, core/memory offsets and voltage tuning in Afterburner are never touched by PowerDoze. The only overlap is the GPU power limit: both tools can set it, and the last writer wins. The clean setup: if Afterburner manages your GPU, leave the GPU power field empty in your PowerDoze modes — empty means "don't touch the GPU at all".
The part worth automating
The cooling policy is a trade-off, which means the right value changes with context: passive at midnight, active when you're rendering, passive during meetings, active in games. That's exactly the kind of switch nobody flips by hand five times a day. In PowerDoze, cooling policy is one of the knobs bundled into a power mode — a "Quiet" mode carries passive cooling plus a CPU cap, a "Full Power" mode carries active with everything open — and the automation (schedule, fullscreen detection, per-app rules) picks the mode, so the policy follows your day without you remembering it exists.
The short version
Active = loud before slow. Passive = slow before loud. Fans spin in both. It bites hardest on laptops and OEM machines; on self-built desktops it's the CPU cap that does the real work. And no — it won't eat your BIOS curve or your Afterburner profile.