| Actually I made this error twice, which is far from "countless times". The one Allow Telemetry setting would not have made a difference because I had also configured it manually and the Teredo setting doesn't actually disable Teredo anyway. This does not make the entire experiment a failure. But to show how easy of a mistake this is to make, here is what Microsoft's documentation from https://docs.microsoft.com/en-us/windows/configuration/manag... says: Enable the Group Policy: Computer Configuration > Administrative Templates > Network > TCPIP Settings > IPv6 Transition Technologies > Set Teredo State and set it to Disabled State. Reading that, it seems as though you should disable the policy but in fact you should first Enable the policy, then go into the policy settings and Disable the setting there. And even with that mistake, I had it manually disabled in both HKCU and HKLM so if disabled means it uses the local host settings then it should use that. Nevertheless, there are some serious concerns here: 1. Why is it even connecting to facebook, msn ad services, google analytics, etc when nothing is running? 2 Why is it doing this by default on an Enterprise operating system? 4. Why is this the default setting that requires dozens of group policy settings (and knowledge of group policy) to disable? 5. And why is there no option to opt out completely? |