Code: System32\Tasks\Microsoft\Windows\Feedback\Siuf\DmClient => C:\Windows\system32\dmclient.exe [2015-07-10] (Microsoft Corporation) Update SIUF strings This also better disable.
I have applied just about every tweak, remove,disable and block that I am aware of and yet there is one little oddity remaining; Search, whether from taskbar or just within the Start menu. The moment you start to type, if you watch your internet connection sent/received within Windows, you will see some data sent and received still. I am assuming this is the same thing Ars noticed as a ping to bing.com; how do we kill it dead? EDIT: had not realised that Murphy78 just mentioned this same thing right above. Whether by Peerblock or some other trick, I for one want to see this firmly stopped, regardless of if it means losing access to bing (oh noes, however would we cope? ) entirely.
You could try firewall blocking different explorer.exe files and see if that works. I'm not sure which one it actually uses.
Hey s1ave77, after running your program and executing all of the options except for the last 3 ([P], , [F]), I did a reboot. After that, I noticed my mouse cursor was gone so I rebooted again. On the second reboot, my mouse cursor came back, but initially it did make me nervous. *Edit* Damn, sloppy writing. Fixed!
That was one of the first things I tried, blocking SearchUI.exe with a custom rule. However, it never did any good. TCPView always observed an established connection between SearchUI.exe and a remote address. The only thing that seems to gag SearchUI.exe was disabling the predefined "Search" rule. Code: Powershell Set-NetFirewallRule -DisplayName search -Action Block Now I'm not saying don't make a custom rule. By all means do it if you want to. Personally, I would rather have firewall rules that might be redundant than have my data carted to Microsoft.
Quick question about blocking IPs rather than the blocking the full range say 23.96.0.0 - 23.103.255.255, I should be able just to enter the CIDR at 23.96.0.0/13 correct? I entered a custom rule in my firewall with the CIDR and when I opened it back up it read as 23.96.0.0/255.248.0.0, so I'm assuming it has the same affect as entering the range?
Thanks for the reply! If you wouldn't mind, what is your take on blocking the ips via router vs firewall? Also, do you recommend blocking outbound connections only as this appears to be a phoning home protocol or also blocking inbound as well?
Also, upon go through the Host files list, I've noticed that: telecommand.telemetry.microsoft.com telecommand.telemetry.microsoft.com.nsatc.net oca.telemetry.microsoft.com oca.telemetry.microsoft.com.nsatc.net sqm.telemetry.microsoft.com sqm.telemetry.microsoft.com.nsatc.net All fall under the same range of [FONT=Verdana, Arial, Helvetica, sans-serif]65.52.0.0[/FONT] - [FONT=Verdana, Arial, Helvetica, sans-serif]65.55.255.255[/FONT] with a CIDR of [FONT=Verdana, Arial, Helvetica, sans-serif]65.52.0.0[/FONT]/14. If I make one rule with the CIDR, this would ultimate include each individual site?
Microsoft and US government does everything they possibly can to protect us from terrorists and all other evil people and you guys are complaining. IF YOU HAVE NOTHING TO HIDE YU HAVE NOTHING TO BE AFFARAID OF AND JUST LET MICROSOFT DO WHATEVER THEY HAVE TO DO.
oh, US government is the Terrorist who starts wars all over the world with no reason except making money out of it, period
unfortunately this is not the place to discuss things down to the bone, even if I wished if I could but things must be said. back to topic
Some more blather with nothing to back it up there just for a change. Wasting more time for nothing. Yawn. Yes, let the people who understand facts get on with the actual work and useful contributions. Run along.
Which is why I for one don't have one. Next? ./topic Let's keep the unfounded drivel out of this thread. Here be useful things.