4 ms·
That was backported to 7 though. You can disable it in 7 by memorizing the KB #'s of the updates that install them and refusing them, but it's just as much wor
by SippinLean 9y ago
That was backported to 7 though.
You can disable it in 7 by memorizing the KB #'s of the updates that install them and refusing them, but it's just as much work as installing Spybot Anti-beacon on 10.
- Silhouette 9y agoYou can disable it on Windows 7, though. That's the most important point. If you adopted the policy of only installing security updates, which plenty of people did after GWX if not before, you didn't get that other junk anyway. The way Microsoft have actively made it more difficult to install only security updates on older versions of Windows recently is yet another reason not to trust them with updates you can't control at all on newer versions. They brought this mistrust upon themselves by abusing their position deliberately and repeatedly, so I don't think anyone can blame the sceptics. The really sad thing is the number of people, even here on HN where you'd expect to find relatively well-informed discussion, who completely miss the distinction between security updates and updates more generally when debating this issue. I mean, we are literally talking about an organisation that pushed out an entire new operating system via the update process, and they deliberately did so in such a way that many people now have that new OS and didn't necessarily want it or actively did not want it.
- SippinLean 9y agoRight, and you can disable it in 10 as well. >it's just as much work as installing Spybot Anti-beacon on 10 Most apps automate the process. In 7 you have to memorize the 8-digit code associated with the updates you don't want.