Who modifies the value of SettingsPageVisibility when removing a component?

Z

zyr3344

Member
Messages
40
Reaction score
2
When removing a component, is the value of SettingsPageVisibility automatically modified by the system (dism) or NTLite (set by nuhi)? I noticed that after removing certain components, some settings pages were completely non-functional, but not hidden, so I'm wondering where this error is coming from.
 
After NTLite removes a major feature like Defender or Windows Update, it will update the SettingsPageVisibility reg key to hide the removed pages from the Settings App. Otherwise, users will complain they see "leftovers" when they open Settings.

Right now, the problem is NTLite cannot currently keep your custom SettingsPageVisibility value at the same time it does an edit.

(Suggestion) Option to Hide Pages from Settings App in Windows
 
garlin said:
After NTLite removes a major feature like Defender or Windows Update, it will update the SettingsPageVisibility reg key to hide the removed pages from the Settings App. Otherwise, users will complain they see "leftovers" when they open Settings.

Right now, the problem is NTLite cannot currently keep your custom SettingsPageVisibility value at the same time it does an edit.

(Suggestion) Option to Hide Pages from Settings App in Windows
Click to expand...
So the values set in SettingsPageVisibility are all set by NTLite developers? If this is the case it would explain why some pages are not hidden, simply because the developer didn't notice them.
 
nuhi is the only NTLite dev, and he sometimes misses some of the final details on a new change.

If you have a list of removals which didn't get properly hidden, feel free to report them by DM to him or share them in a forum report.
 
For nuhi,
When TTS is removed, the page ms-settings:speech should be hidden, but now it is only hidden when the Speech Api is removed, and when Speech Recognition is removed, the page ms-settings:privacy-speech should be hidden, but it is not hidden even when the Speech Api is removed, when Voice Access is removed, ms-settings:easeofaccess-speechrecognition will lose its function. Although it is related to Speech Recognition, this page only has settings related to Voice Access.
All of the above are based on 24H2.
 
Last edited:
Curious if the issues zyr3344 mentioned above were rectified? Mostly want to know if I should make some reg keys before finalizing my ISOs.
After applying changes in NTLite but not creating the ISO, would the registry hive contain the aforementioned settings tweaks after removal of components?
 
When NTLite removes selected components, it will hide the matching pages. The problem is some sections are not cleanly divided, they will cause other parent or child pages to disappear at the same time. For example, hiding Energy Recommendations removes the entire Power section.

If you don't agree with NTLite's choices, then you can always apply a new reg file or command during Post-Setup.
 
  • Like
Reactions: Jim
You must log in or register to reply here.
Back
Top