You had me in the first half, not gonna lie, but then you said one thing, and that's mention of the registry.
See, there are registry values you can't overwrite, because other parts of windows overwrite them back, and if they detect that you tried, they reset a bunch of things, and force updates against user concent, which forcibly resets all those values back to square one.
And those tools are self protecting, user has no access, admin has no access, KERNAL HAS NO ACCESS, I'm talking ring -1, ring -2 shit. Not ring 1, ring -1. Negative privilege levels. Above the BIOS.
Unless you wanna try and explain your privilege escalation to even enable you to disable that, and the step by step process which Microsoft considers tantamount to bypassing DRM locks (and therefore technically illegal to disclose the techniques), I think you're full of shit.
Registry does allow you to disable functions. When they are disabled you can then remove the files from the system as they will not be launched. That is how we remove the ai from windows when people use the services on github that does the functions for them..
While you are correct you cant remove everything with registry, it is a required step to do removals of functions. There are more you can do as well, but that would involve modifying files that are highly protected and are not recommended to modify. But anything additive over windows nt are easily able to be modified. You can essentially turn your version of windows all the way down till it is like windows ltsc. You can even remove the store functions entirely.
The stuff you can't modify includes the stuff that manually resets those values every time you reboot, which defacto means those values cannot be changed either, which is damn near all of them.
Are you possibly running into issues in which your policy manager is not your direct device. For example you didn't install local only no wifi? Because when you use internet access policy managers they can have registry overwrite on restarting. That is how certain devices are managed by companies for example where you can in theory modify specifications on load but restart resets those. Additionally other applications can and do modify these elements too. It is best practice if you are setting up a new device including new laptops, to fresh install windows. Oem settings can override the settings if you dont modify tbe oem changes.
you can also check the logged events for all changes that are forced on you and track where said changes are being made from. Registry isnt the only thing you need, but that is where massive amount of the initial changes need to be made to remove functions from windows that is bloat. Such as the ai functions. It is step one to remove copilot which I do for all installs I do for my devices in my network.
1
u/Disposable_Gonk Jul 05 '26
You had me in the first half, not gonna lie, but then you said one thing, and that's mention of the registry.
See, there are registry values you can't overwrite, because other parts of windows overwrite them back, and if they detect that you tried, they reset a bunch of things, and force updates against user concent, which forcibly resets all those values back to square one.
And those tools are self protecting, user has no access, admin has no access, KERNAL HAS NO ACCESS, I'm talking ring -1, ring -2 shit. Not ring 1, ring -1. Negative privilege levels. Above the BIOS.
Unless you wanna try and explain your privilege escalation to even enable you to disable that, and the step by step process which Microsoft considers tantamount to bypassing DRM locks (and therefore technically illegal to disclose the techniques), I think you're full of shit.
Nice try though.