[lax4ever]

If you are getting your OS from some third party torrent packager you are doing it wrong. There are far easier ways to get around this without trusting that some mysterious third party hasn't embedded some malware in their custom Windows deployment.

[qu4z-2]

You're already putting your trust in some mysterious first party to not embed malware...

[lax4ever]

You're doing that pretty much regardless of what OS you use. Yes, I agree MS has issues, but legitimate malware has not yet been a line they have crossed.

[john01dav]

If I created a program that took screenshots and keylogged everything that you did, and then put it in your computer, you'd rightly call it malware. But, when Microsoft does this, it isn't? They aren't exactly trustworthy (as you said, it has issues).

[barbs]

Malware, maybe not. But adware...?

[mindslight]

Companies keep generating this proliferation of xyz-ware names to distract from the fact that anything that works against the user's interest is fundamentally malware.

[lucb1e]

With Microsoft allegedly trying to close down all those ways, it sure sounds like OS modification (or not using Windows) is the reasonable endgame here? I'm not sure how this comment, saying to not use modified OSes but use the "far easier ways", fits with the submitted article. Not everyone has the skills to modify the compiled code files that make Windows require a Microsoft account

If it's so easy, which are these ways, then? Do you think they'll remain available indefinitely?

Not that I don't underwrite the risks involved in getting your OS from untrusted or unreputable sources

[lax4ever]

The simplest remaining way that I am aware of is actually an autounattend file. This is a Microsoft supplied method that has been around for a long time and something that I truly believe will stick around untouched because it is pretty much a requirement of any enterprise Windows deployment.

Not only does it allow you to create a local admin account, but you can also skip all the other setup screens that you want by pre-supplying values. Throw this file into your Windows boot media, do a fresh install (which you should be doing when you get a new machine regardless), and away you go. I use this both personally and my work environment. Not only are you then not relying on modifying OS ISO's or compilations, but an XML file is relatively easy to verify that only the settings you have set are the ones being input into the system if you utilize a third party tool like the one available at schneegeas.de

[mindslight]

I know there are more direct sources. But for the amount of mental energy I want to invest into Windows, discovery through torrents is far easier. My workflow consists of creating a VM, installing / updating everything, taking a snapshot, then removing network access before it gets access to Samba shares with any private information.

I suppose I might still be worried about targeted offline-acting malware if I were using Windows to control some enrichment centrifuges or something. But apart from that, I'm fine with whatever inhabitants it may have frolicking in their isolated jungle.