Repository navigation
Description
Version
1.7.4
Windows Version
Windows 11
Reproduction Steps
I’m testing ThreadPilot’s Core Parking feature on Windows 11 and found what appears to be a mismatch between the ThreadPilot UI and the actual Windows power-plan settings.
System:
- Windows 11 build 26200
- Intel Core i7-10510U (4 cores / 8 threads)
On my Power Saver plan, I checked these settings with powercfg:
- CPMINCORES: AC/DC 0/0
- CPMAXCORES: AC/DC 100/100
- CPINCREASEPOL: AC/DC 0/0
- CPINCREASETIME: AC/DC 7/7
- CPOVERUTIL: AC/DC 60/60
- CPPERF: AC/DC 0/0
I then toggled ThreadPilot’s Core Parking switch and immediately checked all six settings again.
None of the six Windows settings changed, but ThreadPilot’s displayed Core Parking status changed.
In an earlier test, I also observed ThreadPilot changing CPMINCORES on AC while DC remained at 0, so the behavior appears inconsistent between tests.
Could you clarify:
- Which Windows setting/API does ThreadPilot use to determine the Core Parking status?
- What exactly does the Core Parking toggle modify?
- Why can ThreadPilot show different states when the Windows CPMINCORES/CPMAXCORES values are identical?
I can provide the exact before/after powercfg output if needed.
Expected Behavior
I’m testing ThreadPilot’s Core Parking feature on Windows 11 and found what appears to be a mismatch between the ThreadPilot UI and the actual Windows power-plan settings.
System:
- Windows 11 build 26200
- Intel Core i7-10510U (4 cores / 8 threads)
On my Power Saver plan, I checked these settings with powercfg:
- CPMINCORES: AC/DC 0/0
- CPMAXCORES: AC/DC 100/100
- CPINCREASEPOL: AC/DC 0/0
- CPINCREASETIME: AC/DC 7/7
- CPOVERUTIL: AC/DC 60/60
- CPPERF: AC/DC 0/0
I then toggled ThreadPilot’s Core Parking switch and immediately checked all six settings again.
None of the six Windows settings changed, but ThreadPilot’s displayed Core Parking status changed.
In an earlier test, I also observed ThreadPilot changing CPMINCORES on AC while DC remained at 0, so the behavior appears inconsistent between tests.
Could you clarify:
- Which Windows setting/API does ThreadPilot use to determine the Core Parking status?
- What exactly does the Core Parking toggle modify?
- Why can ThreadPilot show different states when the Windows CPMINCORES/CPMAXCORES values are identical?
I can provide the exact before/after powercfg output if needed.
Actual Behavior
I’m testing ThreadPilot’s Core Parking feature on Windows 11 and found what appears to be a mismatch between the ThreadPilot UI and the actual Windows power-plan settings.
System:
- Windows 11 build 26200
- Intel Core i7-10510U (4 cores / 8 threads)
On my Power Saver plan, I checked these settings with powercfg:
- CPMINCORES: AC/DC 0/0
- CPMAXCORES: AC/DC 100/100
- CPINCREASEPOL: AC/DC 0/0
- CPINCREASETIME: AC/DC 7/7
- CPOVERUTIL: AC/DC 60/60
- CPPERF: AC/DC 0/0
I then toggled ThreadPilot’s Core Parking switch and immediately checked all six settings again.
None of the six Windows settings changed, but ThreadPilot’s displayed Core Parking status changed.
In an earlier test, I also observed ThreadPilot changing CPMINCORES on AC while DC remained at 0, so the behavior appears inconsistent between tests.
Could you clarify:
- Which Windows setting/API does ThreadPilot use to determine the Core Parking status?
- What exactly does the Core Parking toggle modify?
- Why can ThreadPilot show different states when the Windows CPMINCORES/CPMAXCORES values are identical?
I can provide the exact before/after powercfg output if needed.
Logs and Diagnostics
I’m testing ThreadPilot’s Core Parking feature on Windows 11 and found what appears to be a mismatch between the ThreadPilot UI and the actual Windows power-plan settings.
System:
- Windows 11 build 26200
- Intel Core i7-10510U (4 cores / 8 threads)
On my Power Saver plan, I checked these settings with powercfg:
- CPMINCORES: AC/DC 0/0
- CPMAXCORES: AC/DC 100/100
- CPINCREASEPOL: AC/DC 0/0
- CPINCREASETIME: AC/DC 7/7
- CPOVERUTIL: AC/DC 60/60
- CPPERF: AC/DC 0/0
I then toggled ThreadPilot’s Core Parking switch and immediately checked all six settings again.
None of the six Windows settings changed, but ThreadPilot’s displayed Core Parking status changed.
In an earlier test, I also observed ThreadPilot changing CPMINCORES on AC while DC remained at 0, so the behavior appears inconsistent between tests.
Could you clarify:
- Which Windows setting/API does ThreadPilot use to determine the Core Parking status?
- What exactly does the Core Parking toggle modify?
- Why can ThreadPilot show different states when the Windows CPMINCORES/CPMAXCORES values are identical?
I can provide the exact before/after powercfg output if needed.
Activity
PrimeBuild-pc commentedon Sep 21, 2026
Hi, thanks for the detailed report. You have identified both a confusing UI convention and behavior that we need to investigate.
In ThreadPilot 1.7.4, the Core Parking control gets the active power scheme through
PowerGetActiveSchemeand reads the AC value ofCPMINCORESthroughPowerReadACValueIndex.The toggle currently changes only
CPMINCORESfor AC power on the active scheme:It does not modify the DC value,
CPMAXCORES,CPINCREASEPOL,CPINCREASETIME,CPOVERUTIL, orCPPERF. This means the current Core Parking label is ambiguous and should be improved.An AC change with DC remaining unchanged is expected. However, if
CPMINCORESfor the same active scheme remained unchanged while ThreadPilot's displayed state changed, that is not expected.Could you please post the exact before and after output of:
Please also mention whether the laptop was plugged in. We will keep this issue open while we investigate.
PrimeBuild-pc commentedon Sep 22, 2026
Thanks, Navin. Your email follow-up confirms that ThreadPilot changed the active plan's AC CPMINCORES value from 0 to 100 while DC remained at 0, as intended.
We found a UI synchronization gap: after a system tweak write fails or is not confirmed, the one-way-bound switch could keep the visual state produced by the click even though the model still held the previous state. PR #61 refreshes the displayed state after every attempt. It also renames the control to "Prevent Core Parking" and explains that it affects the active power plan while plugged in.
A non-release test build is available here:
https://github.com/PrimeBuild-pc/ThreadPilot/releases/tag/issue-60-test.1
For the read-only confirmation you offered:
powercfg /getactivescheme.powercfg /query SCHEME_CURRENT SUB_PROCESSOR CPMINCORES.Expected result: the switch is on only when the AC index is 100 (
0x64), and off for lower values. You do not need to toggle the switch or change any setting.This is an unsigned test build, so Windows may show a SmartScreen warning. Its SHA-256 is
D76C6E14E3699C2DAD04253A89E82616F464ED51162A32F8399F78CEFE859295.We will keep the issue and PR open until you confirm the result.
ende-es commentedon Sep 23, 2026
Hi Lorenzo,
I tested the issue #60 test build using the requested read-only procedure.
CPMINCORES:0x00000000(0%)CPMINCORESsetting of 100% (0x64).The switch correctly reflects the current AC
CPMINCORESvalue in both cases.I also noticed that the switch is now labeled “Prevent Core Parking” rather than simply “Core Parking.” I think this makes the function much clearer, since ON means preventing Windows from parking cores.
I did not toggle the switch or change any power settings during the test.
Thanks for preparing the test build.
PrimeBuild-pc commentedon Sep 23, 2026
Thanks again, Navin. Your read-only confirmation matched the acceptance criteria and helped us validate the fix on real hardware. The change from PR #61 has now been merged and released in ThreadPilot v1.7.5: https://github.com/PrimeBuild-pc/ThreadPilot/releases/tag/v1.7.5
The Prevent Core Parking switch now resynchronizes with the active power plan's AC CPMINCORES value after every write attempt, and the clearer label is included in the release.
fix: keep system tweak switches in sync (PrimeBuild-pc#61)