News for hackers. Stuff that matters.
Re:“Reclaim Windows 10” Powershell Script by MrVitaliy on Saturday January 07, 2017 @02:15PM (#13345962)
That's not true. Install and run wireshark then dial all you want, there will always be traffic every other minute or so to one of Redmond's servers from just idling.
Re:“Reclaim Windows 10” Powershell Script by UnoriginalGuy on Saturday January 07, 2017 @02:32PM (#13346074)
I did just that, cannot reproduce.

Did you actually try this or is this based on one of those articles about the open beta of Windows 10 that had a lot more telemetry you couldn't disable?

Re:“Reclaim Windows 10” Powershell Script by Aldo_MX on Saturday January 07, 2017 @02:43PM (#13346153)
I'll be the devil's advocate this time.

As you can see in gpedit, Cortana and Web Search is disabled. Why does explorer.exe need to access akamai or search.msn?

http://imgur.com/a/yiIxn

Re:“Reclaim Windows 10” Powershell Script by UnoriginalGuy on Saturday January 07, 2017 @02:56PM (#13346236)
Some of those GPO policies no longer work, they're legacy.

Instead: Click Search, Hamburger Menu, Settings, Uncheck "Search Online and Include Web Results."

If you have OneDrive installed Explorer keeps a constant connection to Microsoft's servers to populate your OneDrive folders into the navigation pane.

Re:“Reclaim Windows 10” Powershell Script by Aldo_MX on Saturday January 07, 2017 @03:08PM (#13346329)
OneDrive is also disabled, and your claim about GPO policies is blatantly nonsense, since that's what you use for Enterprise deployments.

Also, if you had actually researched before publishing, you'd known that Microsoft removed the disable option from the Hamburger menu during the Anniversary Update.

This is not a conspiracy theory but Microsoft blatantly crossing the line, I personally don't care since I'm not interested in joining the arms race against Telemetry, but not being able to easily disable an annoying persistent connection certainly leaves you a bad taste in your mouth.

Re:“Reclaim Windows 10” Powershell Script by UnoriginalGuy on Saturday January 07, 2017 @03:26PM (#13346425)
> your claim about GPO policies is blatantly nonsense, since that's what you use for Enterprise deployments.

It says right in the GPO policies which operating systems they apply to. For example in your screenshot you set "Do not allow web search" to quote the policy itself that only applies to:

> Microsoft Windows XP, or Windows Server 2003 with Windows Search version 3.01 or later

Doesn't do anything on Windows 10. So it isn't "blatantly nonsense." You are just playing with pro functionality you don't understand.

> Also, if you had actually researched before publishing, you'd known that Microsoft removed the disable option from the Hamburger menu during the Anniversary Update.

Nope. http://i.imgur.com/nzHBVex.png

As you can see I am on 10.0.14393 which is the Anniversary Retail Release and have the option.

Re:“Reclaim Windows 10” Powershell Script by vic-traill on Saturday January 07, 2017 @09:05PM (#13347825)
Your point about various GPO settings being version specific is absolutely correct.

I will say that I definitely do not want to manage options via clicky-click. Local policy editing (and domain group policies in the enterprise) have been a replicable, scalable way to manage settings in a Windows environment since at least XP/Server 2003 (the earliest Windows client + server environments I've admin'd IIRC).

Configuration outside of LP/GP doesn't scale particularly well beyond personal use, I'd say and as such I get what the other poster was driving at.

Re:“Reclaim Windows 10” Powershell Script by MrVitaliy on Saturday January 07, 2017 @02:34PM (#13346083)
The only thing I didn't do is to block MS servers in System32\Drivers\etc\hosts file. This is useless in my opinion, MS can always change them or add new ones.
Re:“Reclaim Windows 10” Powershell Script by EasyTiger_ on Saturday January 07, 2017 @02:46PM (#13346176)
Didn't they 'hack' it so it ignores MS servers listed in hosts file?
Re:“Reclaim Windows 10” Powershell Script by dhimes on Saturday January 07, 2017 @03:14PM (#13346360)
Curious about this too as I heard the same thing.
Re:“Reclaim Windows 10” Powershell Script by rasz_pl on Saturday January 07, 2017 @10:41PM (#13348102)
not hacked, just hardcoded IPs as a fallback path when resolving telemetry domains fails.
Re:“Reclaim Windows 10” Powershell Script by nerflad on Sunday January 08, 2017 @04:53AM (#13349084)
Good lord.
Re:“Reclaim Windows 10” Powershell Script by UnoriginalGuy on Saturday January 07, 2017 @02:45PM (#13346163)
That didn't answer my question at all.

You said above:

> That's not true. Install and run wireshark then dial all you want, there will always be traffic every other minute or so to one of Redmond's servers from just idling.

I literally did exactly what you said. Shutdown all third party applications on a Windows 10 Pro machine, loaded Wireshark 2.2.3, filtered out all LAN traffic/broadcast traffic/etc and watched. Didn't see any traffic at all going to Microsoft nor anyone else, it is still running now and not a peep.

Now I have no doubt that if I waited long enough I would, since I have Windows Update enabled, use Microsoft for time synchronisation, and a handful of other things. But it definitely isn't "every other minute." I cannot reproduce that.

Re:“Reclaim Windows 10” Powershell Script by rasz_pl on Saturday January 07, 2017 @10:42PM (#13348109)
This is interesting, because I just did the same thing and there is plenty of garbage flying around to various akamai hosts every 20-60 minutes.

Is your system volume license or retail?

Re:“Reclaim Windows 10” Powershell Script by UnoriginalGuy on Saturday January 07, 2017 @11:36PM (#13348292)
Retail. 10 Pro specifically.
Re:“Reclaim Windows 10” Powershell Script by rasz_pl on Sunday January 08, 2017 @01:40AM (#13348638)
Mine was activated as Win 7 upgrade to 10 during the Insider Program. Tested clean install in VM right now.

Maybe Microsoft tracks this and forces my in theory Retail copy to still act like some sort of guinea pig :/

Re:“Reclaim Windows 10” Powershell Script by MrVitaliy on Saturday January 07, 2017 @03:56PM (#13346585)
Fair enough. From what I recall, the traffic was going to telemetry servers not time sync. Next time I play with Windows I'll holdon to the capture logs for proof.

I think the other side effect from all those regedit hacks was issues with Windows updates. In the end, my machine got stuck at installing October patches, rebooting then failing at 99% applying the patch, rebooting again, rolling back the patch, rebooting, trying to install the patch again. The non-stop CPU usage and reboots made me quit Windows for awhile.