It wasn't homebrew, it was the clean OEM of that Chinese company that partnered with Microsoft to make Government edition. Seriously, go google about it instead of refusing the facts!
Still refuse to believe it's telemetry free, even the thread wasn't able to prove this. The ISO is another thing.
I'm Windows 10 Home User. Currently using Peerblock, O&O Shutup, W10Privacy but also remap routing table via static routes: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\PersistentRoutes\ Powershell command: route -p add 23.218.212.69 MASK 255.255.255.255 0.0.0.0 route -p add 65.55.108.23 MASK 255.255.255.255 0.0.0.0 route -p add 65.39.117.230 MASK 255.255.255.255 0.0.0.0 route -p add 134.170.30.202 MASK 255.255.255.255 0.0.0.0 route -p add 137.116.81.24 MASK 255.255.255.255 0.0.0.0 route -p add 204.79.197.200 MASK 255.255.255.255 0.0.0.0 route -p add 23.218.212.69 MASK 255.255.255.255 0.0.0.0 route -p add 8.254.209.254 MASK 255.255.255.255 0.0.0.0 route -p add 68.232.34.200 MASK 255.255.255.255 0.0.0.0 route -p add 66.119.144.190 MASK 255.255.255.255 0.0.0.0 route -p add 65.55.39.10 MASK 255.255.255.255 0.0.0.0 route -p add 65.55.252.93 MASK 255.255.255.255 0.0.0.0 route -p add 65.55.252.92 MASK 255.255.255.255 0.0.0.0 route -p add 65.55.252.71 MASK 255.255.255.255 0.0.0.0 route -p add 65.55.252.63 MASK 255.255.255.255 0.0.0.0 route -p add 65.55.252.43 MASK 255.255.255.255 0.0.0.0 route -p add 65.55.108.23 MASK 255.255.255.255 0.0.0.0 route -p add 65.52.108.29 MASK 255.255.255.255 0.0.0.0 route -p add 65.52.100.94 MASK 255.255.255.255 0.0.0.0 route -p add 65.52.100.93 MASK 255.255.255.255 0.0.0.0 route -p add 65.52.100.92 MASK 255.255.255.255 0.0.0.0 route -p add 65.52.100.91 MASK 255.255.255.255 0.0.0.0 route -p add 65.52.100.9 MASK 255.255.255.255 0.0.0.0 route -p add 65.52.100.7 MASK 255.255.255.255 0.0.0.0 route -p add 65.52.100.11 MASK 255.255.255.255 0.0.0.0 route -p add 64.4.6.100 MASK 255.255.255.255 0.0.0.0 route -p add 64.4.54.32 MASK 255.255.255.255 0.0.0.0 route -p add 64.4.54.22 MASK 255.255.255.255 0.0.0.0 route -p add 23.99.10.11 MASK 255.255.255.255 0.0.0.0 route -p add 23.218.212.69 MASK 255.255.255.255 0.0.0.0 route -p add 23.102.21.4 MASK 255.255.255.255 0.0.0.0 route -p add 216.58.209.166 MASK 255.255.255.255 0.0.0.0 route -p add 207.68.166.254 MASK 255.255.255.255 0.0.0.0 route -p add 207.46.223.94 MASK 255.255.255.255 0.0.0.0 route -p add 207.46.194.25 MASK 255.255.255.255 0.0.0.0 route -p add 207.46.101.29 MASK 255.255.255.255 0.0.0.0 route -p add 207.123.56.252 MASK 255.255.255.255 0.0.0.0 route -p add 204.79.197.200 MASK 255.255.255.255 0.0.0.0 route -p add 198.78.208.254 MASK 255.255.255.255 0.0.0.0 route -p add 194.44.4.208 MASK 255.255.255.255 0.0.0.0 route -p add 194.44.4.200 MASK 255.255.255.255 0.0.0.0 route -p add 185.13.160.61 MASK 255.255.255.255 0.0.0.0 route -p add 173.194.113.220 MASK 255.255.255.255 0.0.0.0 route -p add 173.194.113.219 MASK 255.255.255.255 0.0.0.0 route -p add 168.63.108.233 MASK 255.255.255.255 0.0.0.0 route -p add 157.56.91.82 MASK 255.255.255.255 0.0.0.0 route -p add 157.56.91.77 MASK 255.255.255.255 0.0.0.0 route -p add 157.56.77.139 MASK 255.255.255.255 0.0.0.0 route -p add 157.56.74.250 MASK 255.255.255.255 0.0.0.0 route -p add 157.56.23.91 MASK 255.255.255.255 0.0.0.0 route -p add 157.56.121.89 MASK 255.255.255.255 0.0.0.0 route -p add 157.55.129.21 MASK 255.255.255.255 0.0.0.0 route -p add 134.170.58.189 MASK 255.255.255.255 0.0.0.0 route -p add 134.170.58.123 MASK 255.255.255.255 0.0.0.0 route -p add 134.170.58.121 MASK 255.255.255.255 0.0.0.0 route -p add 134.170.58.118 MASK 255.255.255.255 0.0.0.0 route -p add 134.170.53.30 MASK 255.255.255.255 0.0.0.0 route -p add 134.170.53.29 MASK 255.255.255.255 0.0.0.0 route -p add 134.170.51.190 MASK 255.255.255.255 0.0.0.0 route -p add 134.170.185.70 MASK 255.255.255.255 0.0.0.0 route -p add 134.170.115.60 MASK 255.255.255.255 0.0.0.0 route -p add 131.107.113.238 MASK 255.255.255.255 0.0.0.0 route -p add 111.221.29.177 MASK 255.255.255.255 0.0.0.0 route -p add 104.82.22.249 MASK 255.255.255.255 0.0.0.0 route -p add 104.82.14.146 MASK 255.255.255.255 0.0.0.0 Results in traffic destined for those listed (telemetry) ip's to be redirected to an unreachable destination. I'm not expert on this but posted the info if anyone wants to test.
From all spying controversy that surrounds W10, I am more concerned about the possibility of have text input recorded and send over to an MS server for whatever reason (really, no matter the reason...) Does that text input collected whilst typing anywhere or somewhere in particular. For example will it get recorded whilst typing in the search area and/or in Notepad, Firefox or other apps? What about passwords? Like when you use a password manager - does text input recorded whilst using such an app? If W10 is indeed an OS with an integrated key logger, how to prevent such text input from being send over the web? Never mind some usage statistics, but this is something else entirely. In group policy editor, under Data Collection, you get the following options (2016 LTSB): Toggle user control over Insider builds >> Disabled Allow telemetry >> Disabled Configure the commercial ID >> Disabled Disable pre-release features or settings >> Enabled Configure Connected User Experiences and Telemetry >> Disabled Do not show feedback notifications >> Enabled Does this key logging ability fall under 'Allow Telemetry'? Because I read that, for LTSB in particular, setting this to Disabled, really means just that (whilst it gets ignored on other W10 editions)
Is there a way to remove all telemetry without breaking the Xbox app and keeping the store running with updates included?
TelemetryPermission-AllowDisable in the kernel settings could disable the telemery but it always go back to default settings