Windows 11 does contain a hidden Processor performance boost mode setting, identified by the PERFBOOSTMODE alias and the GUID be337238-0d82-4146-a960-4f3749d470c7, but the new claim that its seven choices offer a straightforward performance ladder does not survive a close read of Microsoft’s own documentation. MakeUseOf tested the setting on an 11th-generation Core i7-1165G7 ultrabook and reported up to 6–8% faster compile times in Aggressive mode, alongside higher fan noise, heat, and battery use. Those results are plausible for that laptop, but they are not enough to make “Aggressive” a general Windows performance recommendation. Microsoft’s documentation confirms that the control is intentionally hidden in the legacy Power Options interface. It also makes clear that the setting governs how Windows requests performance above a processor’s nominal level when boost headroom exists; it does not change maximum multipliers, voltage limits, PL1/PL2 power limits, or the CPU’s thermal protections. In other words, it is a policy control for boost behavior, not an overclocking switch.
The practical finding is less exciting but more useful: on a thin laptop, this setting is mainly a way to choose where to spend a limited thermal budget. Aggressive modes can front-load performance for short, CPU-heavy work. They cannot create sustained throughput once the processor, firmware, and cooling system have reached their long-term power limit.

Split-screen laptop showcases contrasting red and blue thermal cooling systems with diagnostic software and controls.The Registry tweak exposes an existing Windows policy​

MakeUseOf’s registry path is legitimate. The Processor performance boost mode entry belongs to Windows’ Processor Power Management subgroup, whose GUID is 54533251-82be-4824-96c1-47b60b740d00. Changing its Attributes value to 2 makes the hidden setting appear in the old Control Panel path: Edit Power Plan, Change advanced power settings, Processor power management.
There is a cleaner approach for administrators and power users who do not want to edit the registry manually. An elevated Command Prompt or PowerShell can expose the setting with:
powercfg -attributes SUB_PROCESSOR PERFBOOSTMODE -ATTRIB_HIDE
The current effective value can then be inspected with:
powercfg /q SCHEME_CURRENT SUB_PROCESSOR PERFBOOSTMODE
Windows stores separate AC and DC values, so a laptop can use one boost policy while plugged in and another while on battery. After changing a value through powercfg, the active scheme should be reapplied with powercfg -setactive scheme_current; Microsoft documents that step for power-policy changes.
The important limitation is that revealing a hidden menu does not mean a PC vendor intended every listed option to be useful on that machine. Laptop makers increasingly layer their own controls on top of Windows: firmware power limits, Intel Dynamic Tuning, AMD platform profiles, fan curves, battery-preservation modes, and OEM utilities such as Lenovo Vantage, Dell Power Manager, HP Omen Gaming Hub, or ASUS Armoury Crate. Those controls can override, narrow, or simply make irrelevant what the old Control Panel dropdown requests.

Microsoft’s documentation does not support treating all seven modes as distinct​

MakeUseOf lists seven selections: Disabled, Enabled, Aggressive, Efficient Enabled, Efficient Aggressive, Aggressive at Guaranteed, and Efficient Aggressive at Guaranteed. Windows can indeed show those labels, and powercfg enumerations on many systems include indexes 0 through 6.
But Microsoft’s current PERFBOOSTMODE documentation is substantially more cautious. It documents the setting as hardware-dependent and provides behavior tables for traditional ACPI P-state systems, CPPC/PEP systems, and autonomous CPPC/PEP systems. In those tables, some numerical choices collapse to the same behavior depending on the processor control model. The official page explicitly shows values 3 and 4 behaving identically to Enabled and Aggressive, respectively, on several implementations.
Microsoft’s separate power-tuning guidance is even blunter: its detailed explanation of Processor performance boost mode says the parameter applies to non-HWP systems. HWP, or Hardware-Controlled P-states, is Intel’s hardware-directed performance-management model, used by Windows on Intel systems going back to Broadwell-era support. Intel lists Speed Shift Technology—the client-facing branding associated with hardware-directed performance selection—on the Core i7-1165G7 used in MakeUseOf’s test laptop.
That leaves a material unanswered question in the MakeUseOf testing: which of the seven visible labels caused a distinct policy change on that particular Tiger Lake system, and which were aliases or near-aliases once Windows handed control to Intel’s hardware logic and the laptop’s firmware? Microsoft has not published a clear, contemporary client-Windows mapping for all seven labels across HWP, CPPC, autonomous CPPC, and vendor-managed platforms.
The “At Guaranteed” labels are especially poorly explained in public Microsoft documentation. Community guides commonly describe them as requests for a higher target above the processor’s guaranteed or nominal performance level. That may be a useful shorthand, but it should not be mistaken for a fully documented Windows contract. The labels exist; a universal explanation of their real-world differences does not.

The reported compile gain fits a short-burst thermal model​

MakeUseOf reports that a multi-core build on its 15-watt Core i7-1165G7 laptop finished roughly 6–8% faster in Aggressive mode than with boost Disabled, saving about 40 to 55 seconds from a 10-to-12-minute job. That is exactly the workload where a boost policy can matter: compilers hit all cores hard, then benefit from any additional clock and package-power headroom available before the chassis reaches its sustained limits.
The reported gaming result tells the other half of the story. The outlet saw roughly 3–7% higher average frame rates in lighter CPU-sensitive games, with a smaller 1–4% difference in GPU-bound titles. It also observed that the advantage faded after about 10 to 15 minutes as the ultrabook reached its thermal ceiling.
That behavior should be expected, rather than read as a failed setting. A CPU boost policy influences how eagerly the operating system requests performance. It does not make a 15-watt chassis dissipate 28 watts indefinitely. Once the laptop firmware settles the processor at a sustained package-power limit, the policy has far less room to act. At that point, cooling capacity, GPU load, memory bandwidth, and the OEM’s thermal profile decide performance.
The flaw is not in MakeUseOf’s observation; it is in the temptation to generalize from it. The article does not publish repeat-run data, ambient temperature, charger rating, BIOS version, Windows build, actual package-power telemetry, clock residency, or the exact build workload. It also does not establish whether Windows’ power slider, Intel Dynamic Tuning, or the laptop maker’s own thermal software changed state during testing. Without those controls, its percentages are useful as a personal case study, not a benchmark result that can be carried from one Tiger Lake ultrabook to every Windows 11 PC.

Disabled is a thermal and battery setting, not a free efficiency win​

The one option with a consistently clear meaning is Disabled. Microsoft says it prevents boost behavior above nominal performance. On a laptop that runs too hot, cycles fans irritatingly during calls, or drains rapidly during battery-bound work, that can be a legitimate configuration choice.
It comes with an obvious cost. Disabling boost can sharply reduce performance in code compilation, decompression, photo exports, software updates, virtual-machine workloads, and other jobs that benefit from short periods above base performance. It may also make ordinary tasks feel slower on low-base-clock mobile processors, even when average CPU utilization looks modest.
This is why using Disabled as a universal “cool laptop” tweak can be counterproductive. A workload that finishes much later can consume as much—or more—total energy despite the lower instantaneous wattage. It can also keep fans active for longer. The sensible use case is a machine whose cooling behavior is unacceptable under ordinary bursts, not a desktop workstation or a laptop that needs maximum performance while connected to AC power.
For most users, Microsoft’s ordinary Windows 11 power mode control remains the safer front-end. The Settings app’s Best power efficiency, Balanced, and Best performance choices were designed to coordinate with modern hardware-directed controls. PERFBOOSTMODE is a deeper per-plan policy knob for people who understand their system’s behavior and can measure its trade-offs.

What IT pros should change—and what they should leave alone​

For a managed fleet, the hidden setting is potentially more valuable as a targeted thermal-control measure than as a performance tweak. A help desk dealing with noisy, hot thin-and-light laptops can test a battery-only policy that limits boost on the affected model. Developers with lengthy local builds can test a more assertive plugged-in policy, provided they measure compile time, package power, temperature, fan behavior, and battery health rather than relying on clock-speed screenshots.
A sensible test plan is small:
  • Clone the existing Balanced plan before changing any processor policy so the vendor default remains recoverable.
  • Record the current AC and DC values with powercfg /q before exposing or editing the setting.
  • Test one repeatable workload at least three times under each policy, with the same charger, BIOS profile, room temperature, and background activity.
  • Watch sustained package power and temperature, because a brief boost peak says little about performance after the first few minutes.
  • Check OEM thermal-management software after every change, because it may reset or override the Windows policy.
The headline-worthy part of this setting is not that Microsoft hid a magical speed boost. It is that Windows still exposes an old, hardware-dependent boost-request policy whose names are more precise than its public documentation. On MakeUseOf’s Core i7-1165G7, Aggressive mode appears to buy a short-lived advantage in CPU-bound compiling at a clear acoustic and thermal cost. For everyone else, the only responsible conclusion is to measure the specific machine—or leave the default alone.

References​

  1. Primary source: MakeUseOf
    Published: 2026-08-05T16:30:12+00:00
  2. Related coverage: learn.microsoft.com
  3. Related coverage: learn.microsoft.com
  4. Related coverage: h30434.www3.hp.com
  5. Related coverage: intel.com
  6. Related coverage: support.microsoft.com
  7. Related coverage: pcsupporthub.com
  8. Related coverage: intel.com
  9. Related coverage: pcgameshardware.de
  10. Related coverage: support.microsoft.com
  11. Related coverage: cordero.me
  12. Related coverage: cdrdv2-public.intel.com
  13. Related coverage: tenforums.com
  14. Related coverage: thewindowsclub.com
  15. Related coverage: windowsforum.com
  16. Related coverage: windowsforum.com
  17. Related coverage: elevenforum.com
  18. Related coverage: winhance.net
  19. Related coverage: tenforums.com
  20. Related coverage: elevenforum.com
  21. Related coverage: cdrdv2-public.intel.com
  22. Related coverage: builders.intel.com