Features lost on reboot

[driftywinds]

Hey guys I did as instructed and even got the successfully configured message but as soon as I restart, the start menu is the same as before. How do I fix this?

[boe323]

Having the same issue, the added configs are still there but disabled, have to keep enabling. Build 19042

[boe323]

Its happening in desktop now, seems like you need a block to stop microsofts server setting the disable flag. The tool is useless after 19041.

[boe323]

Hey guys I did as instructed and even got the successfully configured message but as soon as I restart, the start menu is the same as before. How do I fix this?

If youve used mach2 before the this tool, you will need to revert them in mach2, i found this out yesterday but microsoft disable the configs after around 5 mins of login anyway so, create a bat file to run every 5 mins untill theres an offical fix.

[thebookisclosed]

Windows periodically contacts Microsoft servers to configure features on your machine based on data their servers offer at the moment
You can stop this from happening by following the steps I mentioned in this tweet:
https://twitter.com/thebookisclosed/status/1248675136565362693
Please be warned that just like feature editing, feature task disabling is a scenario unsupported by Microsoft

[brc-dd]

Windows periodically contacts Microsoft servers to configure features on your machine based on data their servers offer at the moment
You can stop this from happening by following the steps I mentioned in this tweet:
https://twitter.com/thebookisclosed/status/1248675136565362693
Please be warned that just like feature editing, feature task disabling is a scenario unsupported by Microsoft

It still doesn't work. I have removed Microsoft\Windows\Flighting\ FeatureConfig\ReconcileFeatures. Still on restart my start menu is same as previous one. I am on Windows 10 build 20175.1000.

[thebookisclosed]

Would you mind exporting the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides key found in registry both before reboot when the new UI works and after reboot when it's gone? Additionally, a screenshot of you enabling the feature would be welcome. Thank you.

Does rebooting always result in the feature overrides getting wiped for you or does that happen over time?
This seems to be a very rare issue so any extra detail is welcome.

[brc-dd]

Does rebooting always result in the feature overrides getting wiped for you or does that happen over time?

Actually this is what I am trying to figure out. It was happening with me in morning when I was restarting my device. It never happened with me when I used the "shutdown" option. A probable explanation for this is the windows' "fast startup" feature. I am not sure though.

After I had commented on this thread I tried figuring out the possible reasons myself. I obtained the list of the recently executed tasks by

Get-ScheduledTask | Where State -ne "Disabled" | Get-ScheduledTaskInfo | Select TaskName,TaskPath,LastRunTime,LastTaskResult,NextRunTime | Sort-Object -Property LastRunTime -Descending

This took me to the task \Microsoft\Windows\Flighting\OneSettings\RefreshCache. I tried disabling it, re-enabling feature, restarting explorer. It brought me the new start menu again, but it was again temporary. As soon as I restarted the system, the feature config got lost.

Then I went to HKLM:SYSTEM\CurrentControlSet\Control\FeatureManagement\. I cleared all the registries inside it and then re-enabled the feature using ViVeTool. (I had queried the state of featureId : 23615618 before clearing the registry back then. It was giving me enabled. I also tried restarting the explorer, but nothing was changing then. Sorry I didn't maintained logs.)

But after re-enabling the features, the tool is working as expected. I tried restarting several times, but no feature was lost. I am not able to reproduce any of the errors. If in future, I experience such things, I would surely let you know with proper logs and registry entries. Thanks for the support! :)

PS : I had also tried running sfc -scannow. But it didn't gave me any integrity violation. I have mentioned all these things here as they might be helpful for other users. :)

Well, is it possible some feature is conflicting with another? Because at the time when I removed the registry there were many subkeys in Overrides. But now there is just one subkey (4\81669771).

[thebookisclosed]

Thanks a lot for the detailed reply.

Me and a few friends tried to reproduce what you were experiencing but so far were unsuccessful.
One of my guesses is that the permissions on the FeatureManagement key or one of its descendants were set to something unusual. What you see in registry is effectively what's responsible for configuring features upon a clean boot and I wouldn't be surprised if the early loading (done by winload) resorted to resetting if things went south. If you'd like to manipulate the live config, you have to use NTDLL APIs like ViVeTool does.

I don't think multiple Overrides should be conflicting. I've been doing some research around what ViVe currently calls the "Group" (and defaults to 4 if not specified otherwise) and as I suspected, it is basically a priority system. Value 10 acts a bit special as the system considers those not only overrides but also enterprise policies. However, I've never seen an override with priority 10 installed on any machine, only 0 and 4.
Currently I'm working on reducing the amount of mystery number representations of various feature fields (like EnabledStateOptions) and letting users pick values based on more straightforward word based ones. Hope that makes both using the tool and reporting potential issues a bit easier.

[klepp0906]

I've been using this to disable the settings header successfully for quite some time. I only toggle the ReconcileFeatures task back on when microsoft pushes an update such as the news & interests ticker I wasn't getting enabled with that disabled.

However as of this mornings windows update (the one to fix the printer vulnerability I believe) disabling the settings header works until I restart, then it is lost again.

[thebookisclosed]

Unfortunately we are unable to repro, using the latest 19043.1083 CU the Settings ValueBanner stays disabled

[klepp0906]

i figured that may be the case. the only other thing that "changed" on my end was upon logging in i clicked "forgot my pin" by accident which opened a page at the login screen to login to my microsoft account. Presume that somehow reset or un"synced" something between the flag, task, and registry.

still trying to troubleshoot it with a second pc for comparison at the moment. the prior post from brc-dd has at least given me some registry keys to compare between the two.

[ghost]

As of today's update (KB5005033), removing the ad from settings doesn't work at all any more, regardless of rebooting or not. RIP

[mgieseki]

Same issue here. After KB5005033 (Win 21H1) the feature settings get lost on reboot. The unchanged registry entries are still there, though, but vivetool queryconfig all no longer shows the entries of group 4. The above mentioned task ReconcileFeatures is disabled on my machine.

Before reboot:

[0x011738FA / 18299130]
Group: 4
EnabledState: Disabled (1)
EnabledStateOptions: 1
Variant: 0
VariantPayloadKind: 0
VariantPayload: 0

[0x016B553E / 23811390]
Group: 0
EnabledState: Enabled (2)
EnabledStateOptions: 0
Variant: 0
VariantPayloadKind: 0
VariantPayload: 0

[0x01A4258C / 27534732]
Group: 0
EnabledState: Disabled (1)
EnabledStateOptions: 0
Variant: 0
VariantPayloadKind: 0
VariantPayload: 0

[0x01C4D492 / 29676690]
Group: 0
EnabledState: Enabled (2)
EnabledStateOptions: 0
Variant: 0
VariantPayloadKind: 0
VariantPayload: 0

[0x01E786CF / 31950543]
Group: 4
EnabledState: Disabled (1)
EnabledStateOptions: 1
Variant: 0
VariantPayloadKind: 0
VariantPayload: 0

After reboot:

[0x016B553E / 23811390]
Group: 0
EnabledState: Enabled (2)
EnabledStateOptions: 0
Variant: 0
VariantPayloadKind: 0
VariantPayload: 0

[0x01A4258C / 27534732]
Group: 0
EnabledState: Disabled (1)
EnabledStateOptions: 0
Variant: 0
VariantPayloadKind: 0
VariantPayload: 0

[0x01C4D492 / 29676690]
Group: 0
EnabledState: Enabled (2)
EnabledStateOptions: 0
Variant: 0
VariantPayloadKind: 0
VariantPayload: 0

[ghost]

Same issue here. After KB5005033 (Win 21H1) the feature settings get lost on reboot.

Not quite the same then; maybe they are lost on reboot also, but my issue is that they don't even take effect prior to the reboot.

[mgieseki]

Ok, right, that could be. The registry entries are present, though. Maybe the Windows update changed the way how features are treated now? At least on my 20H2 laptop it is sufficient to add the registry entries to affect the feature settings.
Either way, I always had to reboot the machine to get the features to work -- at least to disable the annoying banner in the settings window.

[ghost]

Maybe the Windows update changed the way how features are treated now?

I think you may be right mate, I hadn't noticed this:

vivetool queryconfig all no longer shows the entries of group 4.

And I think you're onto something there. Nice catch! I gather that the groups act as some kind of priority level so perhaps changing the group to a high level may still function? I'm making wild guesses here....

[thebookisclosed]

Correct, the "group" is actually a priority. I wasn't entire surely what this particular value meant when reversing the mechanism in its early days but now I'm a little wiser. An update to ViVeTool is coming which lets you utilize priorities properly.

[alwaysaheadofMS]

I am finding with many of my clients computers, The "Settings" reverts back to the ads after a few days! Thanks for an update to the tool in advance. On my own machines I just turn off Windows Update for the removal the ads!

[ghost]

I originally found my way here in an attempt to remove the advertising from the OS settings app. Every now and then it annoys me enough to check and see if anything changed, and, today it has. Courtesy of https://winaero.com/disable-settings-header-banner-in-windows-10-2004-and-20h2/ I tried the two commands and both are retained through reboots. Windows version is build 19043.1348 Windows Feature Experience Pack 120.2212.3920.0

Hope that helps, and thanks so much for getting this abomination out of my face.

[GitExploraa]

Windows 11 Pro Latest Dev Build here 22533.1001 , i enabled the new Alt-Tab non full screen menu, and each time i reboot the setting reset, hence the need to reenable it back manually each time

[thebookisclosed]

Windows 11 Pro Latest Dev Build here 22533.1001 , i enabled the new Alt-Tab non full screen menu, and each time i reboot the setting reset, hence the need to reenable it back manually each time

Had no luck reproducing this in a brand new 22533.1001 VM, I have two questions:

• Are you configuring features as admin?
• Mind taking a screenshot of HKLM\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\4?

[GitExploraa]

latest dev build to date 22538.1000 still randomly occuring

[thebookisclosed]

The frequent feature resets will be addressed in the next ViVe update

[GitExploraa]

The frequent feature resets will be addressed in the next ViVe update

Great, looking forward to that

[alwaysaheadofMS]

The code doesn't work anymore after the latest Win 10 update on 2-15-22, KB5010415 Win ver 19044.1566. I removed and blocked KB5010415 and the ads are gone again. It's back to ver 19044.1288.

[hedhehd]

Please fix this, I'm doing an update to 22567.1 and I do have the new Bluetooth Quick Settings enabled, and today later after I came home this happened. Though I enabled them again.

[GitExploraa]

Please fix this, I'm doing an update to 22567.1 and I do have the new Bluetooth Quick Settings enabled, and today later after I came home this happened. Though I enabled them again.

he said on twitter that an update is on the way, be patient

[crim2som]

Looking forward to ViVe update so that this annoyance can be removed. Thank you.

[hedhehd]

Looking forward to ViVe update so that this annoyance can be removed. Thank you.

Same I'm excited for this

[hedhehd]

Hmmm, looks like it's gonna take a loooong time..

[thebookisclosed]

Hmmm, looks like it's gonna take a loooong time..

This is the last thing that motivates me to work on the update, you know

[thebookisclosed]

This issue should be addressed by the newly released v0.3.0.
If similar problems arise, this thread can be reopened.