News for hackers. Stuff that matters.

A comment on “Reclaim Windows 10” Powershell Script. Parent comment

Re:“Reclaim Windows 10” Powershell Script by Mithaldu on Sunday January 08, 2017 @06:26AM (#13349268)
Incorrect. You could also use the default windows administration process of editing the Group Policy locally, or setting it via your domain controller. It only uses the registry here because that's the simplest way to do it with a script on any kind of machine setup.

If you'd rather do it manually, these steps do the same thing: http://i.imgur.com/HnFpmE6.png

Start > [group policy] > [enter] > Computer Configuration > Administrative Templates > All Settings > Allow Telemetry

[ Parent | on HN ]
Re:“Reclaim Windows 10” Powershell Script by CaptSpify on Sunday January 08, 2017 @01:58PM (#13351282)
Which, AFAIR, is only available on certain versions of Windows?

Additionally, has anyone checked to see if these same keys are changed by using lgpe?

[ Parent | on HN ]
Re:“Reclaim Windows 10” Powershell Script by Mithaldu on Sunday January 08, 2017 @02:13PM (#13351353)
That's why i said "any machine setup". The Home version does not have the Group Policy Editor, because it is not intended for people who should be messing with such things. And for people who have the knowledge, or the drive to mess with such things, keys for both Home and Pro go for ~16€ on amazon.de

> has anyone checked to see if these same keys are changed by using lgpe?

It does not touch the Wow6432Node entry, but given that as far as i know that exists for compatibility for 32 bit programs, i'm not sure it is necessary. Or it might be mirrored in by some kind of maintenance process.

[ Parent | on HN ]