very interesting thread, but, forgive me, from the pdv of a newcomer relatively to the 'telemetry' issues, maybe some more separation of concerns especially in the 1st post(the 'repository' i assume) would be useful; i mean, separating, as far as possible, 'items' related to 'telemetry' strictly from other privacy-related things(of course with "items" and "things" i mean the usual stuff: services, tasks, componenets, reg settings etc), grouping items by topic or single component/feature name as strictly as possible. i.e. especially in the scheduled tasks list many names you can read in there don't seem to be related to exactly the same component/feature or same type of functionality and, maybe, when clear separation is not possible due to things being more related than it could seem, adding a brief explanation on why so. moreover, if this repo will not stay strict to "telemetry" but will be more privacy-wide, could this other summary htt?://forums.mydigitallife.net/threads/61570-Windows-10-KMS-Activation?p=1039635&viewfull=1#post1039635 be considered for being merged ? (significant part of the content is already included here)
back in the days when W7 was new, wasn't there a very similar concern by many people about removing a list of unwanted things ?
HINT: To block additional adresses via hosts file with the script, add them at the very end of the script (after existing list). I will release new version soon, if more additions pop up. EDIT: I will spare the akamai ones to avoid confusions.
This REPO is meant as a collection of all telemetry and privacy related stuff. Atm there is very less info but a lot of speculation going around. I will sort it when i get info about what is mandatory or more a voluntary thing.
Thanks, murphy. That is the kind of thing that i'm not sure but i decide to post it here anyways to see if someone with better knowledge can investigate it further or can comment on it as you did so we can clear things out.
It's good to mention. We need to be aware of all the ways that MS is sending data. I'm more of an advocate of trying to plug leaks with GPO settings and then shoring up remaining leaks with firewall settings, but if none of those work, then we'll need this kind of info.
@ ALL If you find anything worth mentioning, please post here. It will be checked, sorted and if nessessary added to OP and the script .
While searching through the forums i just decided it might be an idea to offer manual way to disable several stuff by passing a TXT list to the process. Especially for install_wim_tweak.exe un/hide and remove online and offline. need to test if offline way works to disable them from Win RE .
s1ave77: I found these 2 the other day, I posted them in a thread but they haven't been added yet: Code: vortex-bn2.metron.live.com.nsatc.net (Uploaded 6mb of data to Microsoft) vortex-cy2.metron.live.com.nsatc.net
Code: 0.0.0.0 msnbot-65-55-108-23.search.msn.com That isn't enough. msnbot seems to range from from 191.232.139.0 to 191.232.139.255. If you run an application such as TCPView then you'll see explorer.exe connecting to that address often.