Well...no... Once again HOW do you know what any component does? How, for example, would you know if the print services driver also records keyboard input and sends it to M$. YOU DON'T. We can't simply assume a new service is a bad one or that a process does solely what its name suggests it does. A lot of telemetry in W10 is hard coded so trying to block anything M$ via the HOSTS file is a waste of time. A router based intercept method would be the way to go but the address space used by M$ would likely be way too big for the average router. Here's a *dumb* idea - cable netowrk to an older pc and only allow internet access via that pc and have that pc configured to block all M$ addresses.