Reserved bandwidth??
Some sort of hidden, concealed, clandestine internal QoS implementation in Windows. Reserving a portion of network bandwidth for high priority traffic sounds like a good concept, but I don’t like the fact that this is so hidden (I’ve been working with computers for many years and I’ve never heard of it until now), and that the mechanism to determine the priority of a packet is unknown.
I mean, you don’t HAVE to do any of that stuff in Windows, it’s just helps a bit.
I’m sure there are plenty of windows horror stories. But almost every Windows computer I’ve had in the last decade, both custom and OEM, has worked pretty well out of the box. And almost every Ubuntu computer I’ve had over the last decade has had problems that weren’t trivial to fix.
I like Linux, but when people compare these problems like they’re the same just are missing the point.
I mean that only matters for people like us.
99.99% of the Windows user base doesn’t give the tiniest semblance of a shit about any of that. Hell I run Windows on my gaming pc still and have never had cause to do any of that.
what if you wanted to show a presentation but windows said 
I’m going to be honest with you, as often as this has been memed and for as long as I have been using Windows on my work computer, I have never once been forced to restart on the spot by an automatic update.
I’m sure those who have will be quick to reply but at this point I’m 90% confident it’s a loud minority.
I’ve seen an entire factory shut down for hours because two critical Win10 computers tried and failed to update. It’s never an issue until it becomes one.
Plus a failed update is the whole reason I nuked my C: drive and switched to Manjaro (now running Arch, put down the pitchforks).
