Acaba de encontrar esto: http://localghost.org/posts/a-traffic-analysis-of-windows-10
Citar
While the inital reflex may be to block all of the above servers via HOSTS, it turns out this won't work: Microsoft has taken the care to hardcode certain IPs, meaning that there is no DNS lookup and no HOSTS consultation. However, if the above servers are blocked via HOSTS, Windows will pretend to be crippled by continuously throwing errors, while still maintaining data collection in the background. Other than an increase in errors, HOSTS blocking did not affect the volume, frequency, or rate of data being transmitted.
Resumiendo en español: Microsoft se ha "tomado la molestia" de codificar (hardcode) ciertas ips donde se envia la información recolectada en Windows 10, por lo tanto, aunque se bloqueen las ips (dominios) usando el archivo hosts windows seguirá siendo capaz de enviar toda esta información en segundo plano (al parecer windows ya no consulta el archivo hosts cuando se trata de enviar nuestros datos).
Fuente: http://www.overclock.net/t/1569236/localghost-a-traffic-analysis-of-windows-10
Citar
Por: orlfman (usuario de overclock.net)
whats going on with the article is that microsoft baked, hard coded actually IP addresses into windows 10. so even if you block a domain, it will bypass the domain and use a hard coded IP address to get around the host block.
simply blocking all known microsoft domains in the host file will not stop the tracking.
even if errors are given, such as cannot find host, it still sending data by using one of the IP addresses in the background when the domain address doesn't resolve.
microsoft really doesn't want you to prevent them from tacking and seeing all your installed software and such.
whats going on with the article is that microsoft baked, hard coded actually IP addresses into windows 10. so even if you block a domain, it will bypass the domain and use a hard coded IP address to get around the host block.
simply blocking all known microsoft domains in the host file will not stop the tracking.
even if errors are given, such as cannot find host, it still sending data by using one of the IP addresses in the background when the domain address doesn't resolve.
microsoft really doesn't want you to prevent them from tacking and seeing all your installed software and such.
Aquí un usuario de overclock.net explica mejor que esta ocurriendo en windows 10, supongo que no es difícil de entender (creo que la mayoría tenemos un nivel decente de ingles hehehe).
Al final el "por si acaso" ya no nos da más esperanzas xD
P.D.: ¿soy el único que se ha dado cuenta que el formato de hosts no es IP-IP? Si no me equivoco debería ser IP-FQDN. Esas lineas (Ip-Ip) del script de Mad Antrax no estarían bloqueando nada, ¿no? hahaha