I run Windows at $WORK too, and it runs fine (there were minor issues which would probably have been worse on Linux). Also much of my work is with the MS stack, which is pretty fine too.
It's just I have little use for it at home, so I run and upgrade it rarely. It turns out upgrading from the nearly oldest Windows 10 build to the latest (at the time) crashed the upgrade process on my setup. This is hardly a regular process - I am sure 99% of people upgrade more regularly, and do not skip as many builds.
It's a cycle too, I guess. The less I use Windows the more upgrades the system accurres which makes me dread turning it on more....
It is odd. I run Windows at work and the machine rarely gets rebooted. No problems what-so-ever. I run a Windows at home and in my Office (I do a lot of SQL SERVER and .NET dev), I rarely have crashes (once or twice a year). I work in a very large office with many other developers and the machines run fine for years on end.
Yet when someone is complaining about Windows on the internet and they like Linux it always has thousands of updates and they need to reinstall the whole OS to play one game. Odd how that comes about. I don't know quite how people manage it. Yet I use the same windows installation for half a decade with almost no problems. It almost sounds like it is operator error.