@ geneticplasma Entries such as the following don't work because Windows doesn't support wildcards. Code: 127.0.0.1 *.data.microsoft.com 127.0.0.1 *.telemetry.microsoft.com 127.0.0.1 *.update.microsoft.com.akadns.net 127.0.0.1 *.support.microsoft.com
1. Is it enough, only to delete the 127.0.0.1-Entries? 2. Why did the Spying-Tool use 127-Entries and no Zeros?
@Boops If you've removed them packages then reboot your PC and then open up TCPView or look at the network tab within resource monitor. Do you see any connections being made to Microsoft? Maybe explorer.exe connecting to msnbot?
Since OP got longer, i added an interactive menu for more comfort navigation down and vice versa in the thread .
BGD PRODUCTION PRESENTS: Win 10 S-M-R-T Enable Disable v0.06.666 Changelog v0.06.666 --added manual option via TXT to all processes --tool now notes when there is nothing to add to hosts in given lists --no redundant entries possible if TXT apply to rules --tool is shipped with the default entries as TXTs and points to them in Input mask --check the TXT in files folder to see syntax
BGD PRODUCTION PRESENTS: Win 10 S-M-R-T Enable Disable v0.06.667 Changelog v0.06.667 --added manual option via TXT for Service Delete that is missing in predecessor
what is the chance that M$ will bring in a "cumulative update" to counter all these de-telemetry measures?
Once I'm finished my personal tweak script I'm going to use Group Policy to set is a startup script so every time my Windows 10 machine turns on the script will apply its tweaks.
The older scripts are what gave the starting point on what the Windows RTM would look like from a telemetry perspective. Not mentioning them makes it seem like the brand new more efficient ones are a completely new idea. My heartburn is that this notion to disable the telemetry excludes all prior work done by people like me.