Live data from Hacker News

“Reclaim Windows 10” Powershell Script

gist.github.com

141–150 of 273 posts

Re: “Reclaim Windows 10” Powershell Script

#141

Earlier quoted context omitted.

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.

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. Di…

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.

Re: “Reclaim Windows 10” Powershell Script

#142
Warning: i tried turning Cortana off by following some powershell scripts (not this one though). ended up she's still on, but now my search functionality is broken. Nothing I did could fix it. Guess I need to reinstall windows if I ever want to get that back.

Re: “Reclaim Windows 10” Powershell Script

#143
post #57

I seriously doubt that Windows 10 is doing anything so grave as to require you to run some arbitrary PowerShell script you found on the Internet with elevated privileges. If you do not understand every single command in this thing, you should avoid it, and if you understand every single command in this, you don't need it.

There's another category. Those of us who manually did this already, are annoyed we didn't write down all the steps, but are glad to find this posted here.

There's another category. Those of us who were so aggravated by it we ended up starting an entire open source project and now have 12k users.

https://www.reddit.com/r/TronScript

Re: “Reclaim Windows 10” Powershell Script

#144

Being heavily involved in setting up standard developer workstations, I consider this to be the only practical approach. It's way beyond any specific config item (including telemetry). This is a sure way to get to a stable and consistent configuration. A few comments: - It is better to split such a mega-script into a set of named scripts, so admins can mix-and-match their own configuration set. - The configuration se…

I believe the word you're looking for in your very first list item is "idempotent", not "re-entrant".

Right. One should ensure that simply re-invoking the script will not break anything by itself. The end result between invocations may be different if scripts are modified between invocations, as getting configuration right is a tricky business.

Re: “Reclaim Windows 10” Powershell Script

#145
post #57

I seriously doubt that Windows 10 is doing anything so grave as to require you to run some arbitrary PowerShell script you found on the Internet with elevated privileges. If you do not understand every single command in this thing, you should avoid it, and if you understand every single command in this, you don't need it.

> you understand every single command in this, you don't need it.

Just because I understand/know how to verify them doesn't mean I can write them down myself in the same time, so no, I don't "need" it, but it is useful to have and to compare to what I'm usually doing.

Re: “Reclaim Windows 10” Powershell Script

#146
post #84
post #57

I seriously doubt that Windows 10 is doing anything so grave as to require you to run some arbitrary PowerShell script you found on the Internet with elevated privileges. If you do not understand every single command in this thing, you should avoid it, and if you understand every single command in this, you don't need it.

Up voted for this: "If you do not understand every single command in this thing, you should avoid it, and if you understand every single command in this, you don't need it." It's so universally applicable!

Not true - automation is great! I understand the script and would use it.

Re: “Reclaim Windows 10” Powershell Script

#147

Rather than continuing to struggle against these features which will continue to be added, why not use an operating system that respects your freedom?

As someone who uses the big three desktops daily, freedom is just one facet. I also want an operating system that respects my time. None of the free operating systems out there do that. Considering the state of Ubuntu, probably the "easiest" to use desktop out there at the moment, my freedom is second to my ability to get a working desktop.

>I also want an operating system that respects my time.

Reminds me of this video (Free as in free time; the freedom less mentioned by free software evangelists.) by Louis Rossmann: https://www.youtube.com/watch?v=KOjCJXHJhPg

Re: “Reclaim Windows 10” Powershell Script

#148
post #57

I seriously doubt that Windows 10 is doing anything so grave as to require you to run some arbitrary PowerShell script you found on the Internet with elevated privileges. If you do not understand every single command in this thing, you should avoid it, and if you understand every single command in this, you don't need it.

I tend to agree. Things like this will most likely break in the future.

They will be undone, they can cause deeper issues in the OS, and they can in some cases cause vulnerabilities.

I see this a lot with chrome. People will load it up with extensions, then blame the browser when something doesn't work.

I'm not saying don't ever use it, but remember this if you start having weird issues, or one day the changes are undone.

It doesn't mean MS is out to get you, they just don't support those who are changing undocumented internals and don't need to announce hen they change some undocumented internal registry entry.

Re: “Reclaim Windows 10” Powershell Script

#149

We shouldn't have to fight the OS, this is ridiculous. Before moving definitively to Linux I'm considering installing a proxy on my router, bloc all ports except one and just redirect Firefox and a few apps that need connectivity to this port. I'm not a network guy though, might be complicated.

You'll either fight it because it doesn't manage power property on your new laptop or you'll fight it because it shows bing on your start menu or sends telemetry about what apps you run.

I'm not going to argue which is "worse" but I sure prefer to switch a few reg keys to stay ahead of Microsoft, to scouring forums trying to figure out what well hidden lever I need to pull to just get the hardware working.

You'll be fighting the OS either way - I'm picking this (easy) fight.

Post reply on HN