Let me first say that I'm here out of concern and that I'm not bashing this tool.
I just don't see this tool doing anything to my Win7x64 box other than adding a few entries to the HOSTS file.
Below is the log from the tool:
Code:
[i] TWindows10WindowsHandWritingDataSharingImmunization is not supported on your OS.
[i] TWindows10WindowsSensorsImmunization is not supported on your OS.
[i] TWindows10WindowsUpdateLocalP2PRegistryImmunization is not supported on your OS.
[i] TWindows10AdvertisingIDRegistryImmunization is not supported on your OS.
[i] TWindows10WiFiSenseRegistryImmunization is not supported on your OS.
[i] TWindows10StepsRecorderRegistryImmunization is not supported on your OS.
[i] TWindows10AITRegistryImmunization is not supported on your OS.
[i] TWindows10TelemetryServicesImmunization is not supported on your OS.
[i] TWindows10TelemetryIPImmunization is not supported on your OS.
[i] TWindows10OneDriveRegistryImmunization is not supported on your OS.
[i] TWindows10OneDriveServicesImmunization is not supported on your OS.
[i] TWindows10CortanaRegistryImmunization is not supported on your OS.
[i] TWindows10WebSearchRegistryImmunization is not supported on your OS.
[i] Telemetry Hosts: 38304 entries found in hosts file (C:\Windows\System32\drivers\etc\hosts.).
[.] (TWindows10TelemetryHostsImmunization)
[i] Telemetry Hosts (extensive list): 38304 entries found in hosts file (C:\Windows\System32\drivers\etc\hosts.).
[.] (TWindows10TelemetryHostsOptionalImmunization)
I've read in a few articles that some of the DNS used for MS telemetry is hard-coded and adding entries like these to the HOSTS file is useless.
I've also read that there are several KB's, a service or two and multiple scheduled tasks that need to be removed in order to "disable" telemetry.
So I will ask again... How effective is this tool?