Problem is, there are no good debloat scripts. It’s all written by amateurs who don’t know what they’re doing, messing up the system in subtle ways that then take ages to figure out.
I thought so as well for a time, but that tool in particular is what finally made me lose faith that there might be any good debloat tool out there.
Basically, someone mentioned that it does a weird thing, so I’ve decided to take a look closer, and stumbled about a whole lot of dumb choices. To exemplify, I’ll just repost that part of my comment from back then:
Oh yeah, I’ve just skimmed what else the “Disable Telemetry” script does to the registry, and I honestly can’t classify it as anything other than batshit insane.
And this is only one script out of a few dozen this “tool” has. Not to mention this is listed under “Essential Tweaks” that are, according to the documentation “Essential Tweaks are modifications and optimizations that are generally safe for most users to implement.”
Remote assistance is not rdp, it’s Microsoft’s support hook over the Internet, which requires telemetry to function. It is distinctly separate from, and not a prerequisite for RDP.
The rest of that I’ll have to look into, but disabling remote assistance seems sane in that context.
I wonder if other parts of the shutdown dialog or hover context menu have phone home functions that can only be disabled in roundabout ways; it wouldn’t be the first time. It would not surprise me to learn that the “which apps are preventing shutdown” dialog would be something that triggers a call to phone that data home.
Good catch. Never used Remote Assistance, so I don’t know how different it is, and if it actually requires telemetry.
Although the broader issue isn’t the why, it’s that it does those things at all without clearly communicating them to the user. Even their documentation has severe lack of any kind of explanation.
Problem is, there are no good debloat scripts. It’s all written by amateurs who don’t know what they’re doing, messing up the system in subtle ways that then take ages to figure out.
And if you are an amateur yourself, you have no means to validate that the scripts aren’t harmful.
Privacy.sexy works great…
Might be down right now ( https://privacy.sexy/ )
Up: https://github.com/undergroundwires/privacy.sexy
I’d say that the ctt winutil does a pretty good job. I’ve been running installs cleaned by it for a good year now without major issues
I thought so as well for a time, but that tool in particular is what finally made me lose faith that there might be any good debloat tool out there.
Basically, someone mentioned that it does a weird thing, so I’ve decided to take a look closer, and stumbled about a whole lot of dumb choices. To exemplify, I’ll just repost that part of my comment from back then:
Remote assistance is not rdp, it’s Microsoft’s support hook over the Internet, which requires telemetry to function. It is distinctly separate from, and not a prerequisite for RDP.
The rest of that I’ll have to look into, but disabling remote assistance seems sane in that context.
I wonder if other parts of the shutdown dialog or hover context menu have phone home functions that can only be disabled in roundabout ways; it wouldn’t be the first time. It would not surprise me to learn that the “which apps are preventing shutdown” dialog would be something that triggers a call to phone that data home.
Good catch. Never used Remote Assistance, so I don’t know how different it is, and if it actually requires telemetry.
Although the broader issue isn’t the why, it’s that it does those things at all without clearly communicating them to the user. Even their documentation has severe lack of any kind of explanation.