So since Microsoft has released Windows 10 into the wild, there have been a bunch of articles flying around about how Microsoft wants your personal data. To get this, there are a whole bunch of privacy settings which are turned “on” by default which allow Microsoft to, among many things, collect and store your personal data and use your computer to distribute updates to the faceless masses on the internet.
I have had a copy of Windows 10 running in a virtual machine for a while as part of the Insider program. Now that I have an RTM version, I decided to run a little test.
First up was to take the Windows 10 install and perform all the privacy precautions I had read about. Turning off location services, using a local account, turning off using my system as a P2P distribution server, etc. Then I shut it down.
Thusly using the Windows 10 control panel and settings pages to turn off everything privacy related that I could, I performed the following actions:
1. Power it up.
2. Log on.
3. Wait for it to stop loading.
4. Power it off.
While doing so, I was capturing all the traffic going into and out of the virtual network interface. Some interesting things showed.
During the first run, I simply picked out the DNS queries which were being requested during this process.
Here’s what showed up:
I dutifully added all these entries to the hosts file in the vm which is found under c:\windows\system32\drivers\etc\hosts. I redirected them all to 0.0.0.0.
Then, I ran (as administrator)
Then turned off the vm and started again. On the second reboot, these additional entries showed up:
I added those to the hosts file as well, ran flushdns again, and rebooted.
The system seems to boot a bit quicker (no, I did not time this), but zero DNS queries are made while booting until you actually start doing something which requires it, such as, oh I don’t know, opening your browser.