Please confirm these before moving forward
Describe your suggestion
The "Recommended" preset for the UAC level setting (Id = "security-uac-level") currently
selects the option that fully disables UAC. I'd suggest making the Windows default - "Notify when apps try to make changes" — the recommended option instead.
Current behavior
In src/Winhance.Core/Features/Optimize/Models/PrivacyOptimizations.cs, under
Id = "security-uac-level", the ComboBox option that disables UAC entirely is the one
flagged as recommended:
new ComboBoxOption
{
DisplayName = "Never notify",
ValueMappings = {
["ConsentPromptBehaviorAdmin"] = 0,
["PromptOnSecureDesktop"] = 0,
},
IsRecommended = true,
},
The Windows default ("Notify when apps try to make changes", ConsentPromptBehaviorAdmin = 5,
PromptOnSecureDesktop = 1) is only marked IsDefault = true.
As a result, applying the Recommended settings sets ConsentPromptBehaviorAdmin = 0 and
PromptOnSecureDesktop = 0. I confirmed this on my own machine with a before/after registry
diff: both values changed (5 -> 0 and 1 -> 0) after applying Recommended.
With UAC at "Never notify", any process can elevate to administrator silently, with no prompt.
Proposed behavior
Move IsRecommended = true to the "Notify when apps try to make changes" option (which already
carries IsDefault = true), and leave "Never notify" available as an explicit opt-in for users
who specifically want it.
Benefit
The "Recommended" button is a one-click action, and most users (myself included) trust it
without reading each of the 65 individual toggles. Silently removing the main barrier against
unwanted privilege escalation is a significant change in security posture for a preset labeled
"Recommended".
Users who want UAC off can still choose "Never notify" deliberately - they just wouldn't get
it by default.
Additional context
I noticed the setting is also marked IsSubjectivePreference = true, which seems to acknowledge
this is a matter of personal taste. That makes flagging the most permissive option as the
recommended one feel inconsistent with the rest of the definition.
To be clear: I like Winhance and use it — this is meant as constructive feedback on one
specific default, not a complaint about the project. Thanks for your work on it!
Please confirm these before moving forward
Describe your suggestion
The "Recommended" preset for the UAC level setting (Id = "security-uac-level") currently
selects the option that fully disables UAC. I'd suggest making the Windows default - "Notify when apps try to make changes" — the recommended option instead.
Current behavior
In src/Winhance.Core/Features/Optimize/Models/PrivacyOptimizations.cs, under
Id = "security-uac-level", the ComboBox option that disables UAC entirely is the one
flagged as recommended:
The Windows default ("Notify when apps try to make changes", ConsentPromptBehaviorAdmin = 5,
PromptOnSecureDesktop = 1) is only marked IsDefault = true.
As a result, applying the Recommended settings sets ConsentPromptBehaviorAdmin = 0 and
PromptOnSecureDesktop = 0. I confirmed this on my own machine with a before/after registry
diff: both values changed (5 -> 0 and 1 -> 0) after applying Recommended.
With UAC at "Never notify", any process can elevate to administrator silently, with no prompt.
Proposed behavior
Move IsRecommended = true to the "Notify when apps try to make changes" option (which already
carries IsDefault = true), and leave "Never notify" available as an explicit opt-in for users
who specifically want it.
Benefit
The "Recommended" button is a one-click action, and most users (myself included) trust it
without reading each of the 65 individual toggles. Silently removing the main barrier against
unwanted privilege escalation is a significant change in security posture for a preset labeled
"Recommended".
Users who want UAC off can still choose "Never notify" deliberately - they just wouldn't get
it by default.
Additional context
I noticed the setting is also marked IsSubjectivePreference = true, which seems to acknowledge
this is a matter of personal taste. That makes flagging the most permissive option as the
recommended one feel inconsistent with the rest of the definition.
To be clear: I like Winhance and use it — this is meant as constructive feedback on one
specific default, not a complaint about the project. Thanks for your work on it!