While that's true, I'm not sure that I consider it a "problem" in the first place. I used to, but not any longer.

In my experience, there's never a good time to update/reboot. I always have multiple applications and tabs open, and always several tasks in flight.

For many years, I had Windows set to not automatically update. Now, given the rapid speed with which vulnerabilities can be exploited, I'm personally glad that it does.

In a corporate environment, though, as the blog author is in, it's really going to be the IT policies that dictate this. They typically have the ability to update not just Windows, but any other software on the system. And often do.

That's one of the reasons that IT departments do prefer (and sometimes dictate) Windows -- It does make it easier for them to secure the multitude of systems for which they are responsible.

I don't think the problem is when to reboot when necessary. The problem is many reboots shouldn't be necessary. If you update a service, restart it. If you update a kernel, reboot. While Microsoft has gotten better at not rebooting every time, most third party installed programs haven't. At least not when I last used a Windows desktop.

That's a completely fair point, and unfortunately Windows does require a restart on pretty much every Windows update. You're right -- Linux only requires a reboot on a kernel update, which is far less frequent.

That said, I don't know of many third-party apps that require a reboot.

You can even update GPU driver without restarting. Those are some crappy 3rd party programs.