Repository navigation
Flag a lowered minimum processor state limit - #13
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Some tweaking tools set ValueMax of "Minimum processor state" below the Windows default of 100, which locks the setting, keeps the power plan editor from raising it and can make the CPU throttling tweak fail. The check restores ValueMax to 100 with a registry backup, so it can be undone.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a Tweak check for
ValueMaxof "Minimum processor state" (54533251-…\893dee8e-…) below the Windows default of 100.Found on a real PC:
ValueMax = 0, so the setting was stuck at 0%, the power plan editor could not raise it and the CPU throttling tweak would fail. The repair writesValueMax = 100with a registry backup (undo available) and asks for a restart.Build with 0 warnings, 179/179 tests (the Evaluate test now covers both the flagged and the default case).