Windows Update is becoming polite. About time.
A few weeks ago, I was hosting a meeting and feeding two presentation screens at the same event. Mid-sentence, the computer driving the slides decided it had waited long enough. Reboot. Black screens. The room went quiet while I scrambled.
That machine was running Windows.
If you’ve used Windows in the last decade, you have a version of this story. Mine just happened to involve a live audience.
What Microsoft is changing
Caschys Blog wrote up the new Windows Update behavior on April 25, and there’s a lot in there. The headlines:
- A 35-day pause, with a calendar picker so you can defer to a specific date instead of mashing the snooze button.
- The setup wizard now lets you skip updates during a fresh install.
- The shutdown menu finally separates plain Shut down from Update and shut down. You can turn the machine off without inheriting a fifteen-minute boot the next morning.
- Update entries describe what each driver actually does — graphics, audio, battery — instead of a Device Manager hash.
- Drivers, .NET, and firmware are bundled into a single monthly restart instead of three.
Rolling out through the Dev and the new Experimental channels for Windows Insiders.
Is this what we wanted?
Mostly, yes. A 35-day pause is meaningful. Bundling restarts is meaningful. The shutdown menu fix should have shipped in 2015.
But notice what’s missing. The underlying philosophy hasn’t changed. Windows still assumes that, given enough time, it knows better than you when to reboot. The pause is longer, but the clock is still ticking. You can defer the reboot, but you can’t decline it. That isn’t user control. That’s a polite warden.
The mid-work surprise restart — the one that hit me at the event — isn’t really what these changes target. That’s what Active Hours has always been for, and Active Hours has always been a band-aid.
The Apple comparison, since I have to
macOS asks. It waits. If I’m working, I dismiss the prompt and it goes away until I come back to it. There’s no “you have 24 hours, then we install regardless”. There’s no surprise reboot at 3 a.m. that loses my open documents. The OS treats my time as more important than its own release cadence.
It can be done. Microsoft is just choosing not to do it that way.
I’ve been complaining about this since 2010
I wrote a post in 2010 about disabling the repeated reboot prompt via gpedit.msc. Sixteen years later, the official answer is finally “we’ll let you pick a date”. Progress, of a kind.
These days I run Windows 11 ARM64 in a VMware Fusion VM on Apple Silicon, mostly to test things. I stopped using Windows daily when I switched to a Mac and realized I no longer needed any of the apps that had kept me on Doze. Update interruptions were a quiet part of that decision.
What to do tonight
Open Settings, go to Windows Update, and look at the pause options and the shutdown behavior. Set the longest pause you’re comfortable with. If you’re on an Insider channel, the new shutdown menu is worth flipping on the moment it appears. The defaults have never been on your side.
Take control while Microsoft is, briefly, willing to give you some.