Disable value banner in Windows Settings header

Bournesup

Member
Is there a way to disable the value banner that shows in the windows settings. Unfortunately it show its ugly head again.

Before I use Mach2 which you can download from the internet and the following command lines I have been using.

mach2.exe disable 18299130

mach2.exe disable 31950543
 

garlin

Moderator
Staff member
Feature controls are only switchable during Preview builds. After the feature is merged into production code, those codes are removed.
The answer would be no...

https://geekermag.com/how-to-enable-header-in-windows-10-settings-app/
Update – August 3, 2021 – After installing Windows 10 update Version 21H1 KB5004296 (Dated 2nd Aug 2021) & KB5004331 (Dated 3rd Aug 2021) lots of users reporting that they’re unable to disable header ads in Windows 10. So we have updated this post with latest post.
 

Bournesup

Member
Thank-you for the great info. I normally don't install preview builds. But I wasn't comfortable with the last update. My computer did crash I couple of times. So I roll back my realtek audio driver to the previous version. I kept everything else the same. Looks good so far.

So If I understand your explanation, the next update which would be a production update would not have the issue with the header ads.
 

garlin

Moderator
Staff member
MSFT will beta-test new features by using a "soft rollout", where a build (or update) hides working functions. If you are picked by Insider to test them, it will be enabled for you. This is the same for tech bloggers who get preview copies of Windows.

The control setting is only intended to reveal a feature early, not to disable it once in general release. After the feature is made permanent, the setting has no effect. There is no rollback, other than never updating Windows.

Hope that makes sense.
 

Clanger

Well-Known Member
I dont even bother with preview updates. Wait for RTM or public releases because you know exactly what you are dealing with then.
 

AeonX

Active Member
How not? Where did you read this? Since clearly you've never tested it.

I tested it and it works. At least until the December 2021 cumulative update it was working.

I even captured this to a .reg and integrated it with NTLite in my builds :cool:

Code:
Windows Registry Editor Version 5.00

; Not required on Enterprise edition

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\KernelVelocity]
"DisableFGBoostDecay"=dword:00000000

; ViveTool.exe addconfig 18299130 1
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\4\4095660171]
"EnabledState"=dword:00000001
"EnabledStateOptions"=dword:00000001
"Variant"=dword:00000000
"VariantPayload"=dword:00000000
"VariantPayloadKind"=dword:00000000

; ViveTool.exe addconfig 31950543 1
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\4\2674077835]
"EnabledState"=dword:00000001
"EnabledStateOptions"=dword:00000001
"Variant"=dword:00000000
"VariantPayload"=dword:00000000
"VariantPayloadKind"=dword:00000000
 

crypticus

Well-Known Member
How not? Where did you read this? Since clearly you've never tested it.

I tested it and it works. At least until the December 2021 cumulative update it was working.

I even captured this to a .reg and integrated it with NTLite in my builds :cool:

Code:
Windows Registry Editor Version 5.00

; Not required on Enterprise edition

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\KernelVelocity]
"DisableFGBoostDecay"=dword:00000000

; ViveTool.exe addconfig 18299130 1
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\4\4095660171]
"EnabledState"=dword:00000001
"EnabledStateOptions"=dword:00000001
"Variant"=dword:00000000
"VariantPayload"=dword:00000000
"VariantPayloadKind"=dword:00000000

; ViveTool.exe addconfig 31950543 1
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\4\2674077835]
"EnabledState"=dword:00000001
"EnabledStateOptions"=dword:00000001
"Variant"=dword:00000000
"VariantPayload"=dword:00000000
"VariantPayloadKind"=dword:00000000

Feature controls are only switchable during Preview builds. After the feature is merged into production code, those codes are removed.
The answer would be no...

https://geekermag.com/how-to-enable-header-in-windows-10-settings-app/

i don't talk without testing. i both tested mach2 and vive. they don't work for me as garlin states.
+your reg file did not work on virtualmachine with a stable windows 11 22000.527
also here on its own site: https://github.com/thebookisclosed/ViVe/issues/6
which build are you using? or maybe you enrolled to insider on stable build?
 

AeonX

Active Member
"Feature controls are only switchable during Preview builds."

Is this documented somewhere? Microsoft said this in some doc? Because I've never used preview builds and mach2 and vivetool work for me.

At least they worked. I decided to test again to make sure and without connecting to the internet it works, if you connect to the internet the banner comes back :mad:

I suspect it's Windows Update or Content Delivery Manager that does this. As I always remove both I didn't notice that the tweak had stopped working.

Tested on Win10 Pro build 19044.1415 (Dec 2021).

Well then the only solution without removing these components is to use Enterprise.
 

|====|

Active Member
"Feature controls are only switchable during Preview builds."

Is this documented somewhere? Microsoft said this in some doc? Because I've never used preview builds and mach2 and vivetool work for me.

At least they worked. I decided to test again to make sure and without connecting to the internet it works, if you connect to the internet the banner comes back :mad:

I suspect it's Windows Update or Content Delivery Manager that does this. As I always remove both I didn't notice that the tweak had stopped working.

Tested on Win10 Pro build 19044.1415 (Dec 2021).

Well then the only solution without removing these components is to use Enterprise.
Tested on online network connected VM 19041.1526 & its not coming back using your shared reg tweaks same as vivetool does.
even rebooted VM more then 5 times still i cant see settings header coming back :)
 

crypticus

Well-Known Member
"Windows Feature Store, where Features (and associated on/off state) live. This store lives in the undocumented Windows Notification Facility (WNF), which provides publish-subscribe messaging for kernel components, system services, and user-space applications.

Windows currently contains thousands of Feature switches that turn on and off new and unfinished functionality, mitigations, test hooks, and overrides." -mach2

there are no documents about it that i can find as a normal user right now. but those settings meant to stay hidden and the funtions they change doesn't exist in stable builds as garlin mentioned. maybe disabling/enabling entire things can be achievable since it is already present as reg tweaks.
 
Last edited:

crypticus

Well-Known Member
Tested on online network connected VM 19041.1526 & its not coming back using your shared reg tweaks same as vivetool does.
even rebooted VM more then 5 times still i cant see settings header coming back :)

really? 1526 doesnt exist in stable lineup. it cannot be 19041

it is 19044 or 19043-42 at best. they are insider lineup. ofc it works on you..... ;)
 

crypticus

Well-Known Member

shouldn't be idk yours look sketchy :D i think it might be working on old builds like yours 1809 2004 etc

here is idea: maybe you switched to insider to u got the 1526 build....
 
Last edited:

garlin

Moderator
Staff member
Mach2 and vivetool perform the exact same job, changing WNF keys. There's no difference.

Because WNF is undocumented, many Windows hackers have spent hours trying to discover them. The problem is not uncovering one, it's figuring out if they've "expired" after a given release/update.

Sometimes, hidden features are in normal updates. A recent example is the 20H2 Enablement Package:
Windows 10, versions 2004 and 20H2 share a common core operating system with an identical set of system files. Therefore, the new features in Windows 10, version 20H2 are included in the latest monthly quality update for Windows 10, version 2004 (released October 13, 2020), but are in an inactive and dormant state. These new features will remain dormant until they are turned on through the “enablement package,” a small, quick-to-install “master switch” that activates the Windows 10, version 20H2 features.

KB4562830 is 85 MB, which after you extract all the files is mostly the size of microsoftedgestandaloneinstaller.exe
Which means it's just flipping switches. Again, because it's undocumented -- MS planned this move months in advance.

19041.1526 is Feb 22 CU
 

|====|

Active Member

shouldn't be idk yours look sketchy :D i think it might be working on old builds like yours 1809 2004 etc

here is idea: maybe you switched to insider to u got the 1526 build....
I use Base xxxxx.1 iso always then apply updates to it whenever i think theres a need to update my os with clean install not upgrade.

Hahahaha seems like a joke | Good Joke :D
 
Last edited:

garlin

Moderator
Staff member
https://github.com/riverar/mach2#management
While the tool can manipulate Feature states, the Feature itself drives state compliance. That is, it can choose to ignore its configured state. Various factors, including what's referred to internally as a staging configuration, can dictate whether a Feature respects its configurable state or not. (Always Disabled staged Features, for example, are crippled/stripped during Windows build compilation and cannot be turned on with Feature Control.)
 
Top