I'm doing so to provide accurate information for readers who only read this post and not my previous ones. You were the one who mentioned "privacy" tools, so sorry if I just provide the results you requested. Is there a problem with "Slimdown10" that I'm unaware of? While I couldn't care less about mentioning "Slimdown10"; I can - for what it's worth - only thank the author for his excellent work.
If what you say is correct, and I certainly have no reason to doubt it, so there must be something else in ViveTool job, since I've done the test with great accuracy.
Please note that I hate to point this out, but my experience here is very different. What I've observed here, where the Slimdown10 batch file has disabled, deleted, and prevented the installation of a huge amount of data compared to a regular clean install, is that the following ViveTool command changes only 1 entry in the Windows Registry. "ViVeTool /disable /id:48796508" From this one Code: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\HostActivityManager\CommitHistory\Microsoft.Windows.Search_cw5n1h2txyewy!ShellFeedsUI] "Mixed"=hex(b):49,16,d0,02,00,00,00,00 to this one Code: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\HostActivityManager\CommitHistory\Microsoft.Windows.Search_cw5n1h2txyewy!ShellFeedsUI] "Mixed"=hex(b):0b,a8,36,03,00,00,00,00 and I can confirm that it works without restarting Windows, even by simply manually adding it to the registry by double-clicking the attached ".reg" file without run ViveTool at all.
In other words, please note that the following entries seem unrelated to ViveTool's job, at least here. Code: reg add "HKLM\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\8\3108581004" /v "EnabledState" /t REG_DWORD /d "1" /f reg add "HKLM\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\8\3108581004" /v "EnabledStateOptions" /t REG_DWORD /d "0" /f https://forums.mydigitallife.net/posts/1894118 Edit to add: I can confirm one more time that the above entries, at least here, do not work.
For the sake of accuracy and if someone was interested, it seems that at least here the above happens in the current session only. While I can confirm that ViveTool modifies that registry entry (which seems dynamic and changing with each reboot), then backing up that entry to use it in a different session doesn't work. To reach the goal it seems that one must necessarily run ViveTool and not a backup .reg file. I've no idea why, at the moment I can only guess that ViveTool perhaps patches a file related to "MoUsoCoreWorker.exe," but that's only a guessing. Just for the record, ViveTool also creates the file "C:\Windows\bootstat.dat". However, for what it's worth, my current preference, as already mentioned, goes in a different direction.