heatlesssun
Extremely [H]
- Joined
- Nov 5, 2005
- Messages
- 44,154
The thing is, in a perfect world, updates would always be a pure beneficial thing that you just add and be done with. The reality is MOST of the time it's that way, other times, you get real problems. For example, I use a custom shell on my system and after doing a giant update pack on a system on 7, I noticed that the Z-order on my windows got completely screwed. I couldn't see the links that were supposed to appear always on top of other windows. It made my GUI practically unusable. So I reverted and went down the updates one by one, until I found the problem. Turns out TWO updates introduced the problem (KB3145739 and KB3153199 for those that want to know). If I had to rely on forced auto-update, my system would be effectively broken for my use, meanwhile most people would be happily singing "works for me!" because they're not doing the same things with their system that I am. Knowing that Microsoft can and will potentially break my system with an update means I need to have the capacity to skip ones that end up being problematic. But whatever. According to some here, I'm part of the 0.00000001% of people who has ever have a problem from a bug Microsoft introduced.
Of course anytime you change software you run the risk of adding bugs. Indeed you always do. But over time as functional and other changes are made to that software, not updating will introduce bugs as well. How many times have we seen security flaws that have been patched be exploited? Or even other bugs corrected in software that cause issues with other software because the updates weren't there?
It's never going to be perfect and I'm not saying 10 can't handle it better in non-Enterprise versions but simply refusing updates doesn't solve everything and can introduce problems of its own when the OS is getting constant functional and non-functional changes.