memstechtips
[BUG] CPU Core Parking Minimum Cores stuck at 12% on battery option
Please confirm these before moving forward
- [x] I have searched for my issue and have not found a similiar in the Open or Closed issues.
- [x] I have tested that this issue has not been fixed in the latest (beta or stable) release.
- [x] I have checked the Discussions section for solutions.
- [x] This issue is about a bug (if it is not, please use the correct template).
Winhance Version
v25.11.12
Windows version, edition, and architecture
Windows 11 Home 25H2 (with latest updates)
Describe your issue
After I selected this option and changed it from 12% to 100%, it resets to 12% after each restart.
Steps to reproduce the issue
- Type 100% in CPU Core Parking Minimum Cores at "on battery"
- Restart PC
- Changes reverted back to 12%
Expected behavior
.
Actual behavior
.
Screenshots or Logs (if applicable)
No response
Additional context
Perhaps this is not a problem with the program itself, but rather a setting specified by the laptop manufacturer?
Hey there, thanks for raising this issue.
It actually is not a Winhance issue, it actually isn't an "issue" - it is related to hardware, here is what I found:
When running Powercfg /query it shows the following:
It reports that the settings max value is 0, can't be higher than that. This also means that Winhance's initial report of 100% was incorrect for this setting.
Even if you try and change the setting in Windows via the Control panel, it doesn't work and you will notice the up and down arrow controls are "greyed-out" indicating it can't be changed:
From what I found this is related to newer processors handling the MinCores setting via hardware/firmware and overrides Windows Settings.
Root Cause: Hardware-Controlled Core Parking On modern CPUs (Intel Skylake and newer, recent AMD processors), core parking control has been moved
from Windows to the hardware itself. The CPU now handles core parking internally, making the Windows
power setting effectively obsolete. When Windows reports:
- Minimum Possible Setting: 0x00000000
- Maximum Possible Setting: 0x00000000 This indicates that the setting is unavailable for user control because it's now hardware-managed.
How it will work in Winhance going forward (after v25.11.18):
- During app startup, FilterSettingsByExistenceAsync validates power settings
- For settings with CheckForHardwareControl = true, it queries powercfg capabilities
- If min=0 and max=0 (hardware-controlled), the setting is filtered out completely
- Only compatible settings appear in the UI
Basically, the user won't see the setting if they can't change it: