• Paul Thurrott: Windows as a Service isn’t working

    Some days I despair about Paul’s coverage of Microsoft’s foibles. Some days he hits the nail smack-dab on the head. Sunday was a banner nail-meet-head day.

    Thurrott posted a sweeping analysis (dare I say a rant?) about the current state of Windows updating. If you’re a Thurrott Premium subscriber ($64/year; highly recommended) you can see it on Thurrott.com.

    His conclusion:

    Microsoft’s goal with Windows as a Service was pure and well-intentioned. But it may never work. And after the tough past year or so, I’m not sure how Windows will absorb this hit. The only thing worse would be continuing down the current path and pretending that it’s working.

    … and that’s precisely correct.

    Windows 10’s patching model (and, increasingly, Win7 and 8.1’s patching model) is congenitally defective. I’ve been saying that in InfoWorld since Feb. 2015.

    Cumulative updates are a great concept, but poorly implemented. And how can they not be? Microsoft’s trying to keep a huge, rickety, old boat afloat in an increasingly inhospitable sea.

    Every month, as of late, we see patches blow up.

    In the real world, Windows customers (and corporate admins) need control over the patches being applied to their machines – and we need patches that work right the first time.

    Every experienced Windows user I know has had at least a handful of minor (and sometimes major) problems with bad patches.

    We Windows customers have bought and paid for reliable patches. We also need tools to better protect our machines. Fancy tiles, 3D drawing, new Universal apps, less leaky browser — they’re are all well and good. But they don’t hold a candle to keeping Windows stable.