Microsoft Responds to User Frustration Over Update Timing
Microsoft is deploying a series of meaningful changes to Windows Update designed to give users more say over when updates are installed and to cut down on the disruptive, often poorly timed restarts that have long frustrated Windows users. The improvements are currently being rolled out to Windows Insiders, with broader availability planned for all users afterward.
According to Microsoft's Aria Hanson, the changes stem directly from analyzing user feedback at scale.
"We are continually reading the feedback submitted about the Windows update experience. Personally, I've had the opportunity to read over 7,621 direct verbatims over the last few months,"Hanson explained. She identified two recurring themes across that feedback: disruption caused by untimely updates, and insufficient control over when those updates happen.
Skipping Updates During Initial Setup
One feature Microsoft has already introduced allows Windows users to skip updates during the out-of-box experience (OOBE), enabling faster access to the desktop so that updates can be installed at a more convenient time. This option is not available on managed commercial devices or systems that require updates to function properly before use.
Flexible Pause Controls with a Calendar Interface
A significant new control addresses how update pauses work. Windows users will now be able to select a specific date to pause updates for up to 35 days using a flyout calendar interface. Crucially, this pause can be extended repeatedly without a fixed limit, giving users far more flexibility than previous pause mechanisms allowed.
Separating Power Options from Update Actions
One of the most common complaints addressed in this update cycle is the unexpected triggering of updates during a routine shutdown or restart. Microsoft is restructuring the Power menu to separate standard power actions from update-related ones.
Going forward, users will see distinct options:
- Restart and Shut down — standard actions that do not trigger updates
- Update and restart and Update and shut down — explicitly labeled options that appear only when updates are ready to be installed
This change is intended to eliminate the frustrating scenario where a user shuts down their PC expecting a quick power-off, only to find it spending several minutes installing updates.
Clearer Driver Update Labeling
Microsoft is also tackling a transparency issue with driver updates, which have historically been listed under a manufacturer's name with no indication of which specific hardware component is being updated. Windows Update will now display the device type — such as display, audio, or battery — directly within the update title, making it easier for users to understand exactly what is being installed before they approve it.
Consolidated Monthly Restarts
Perhaps the most technically impactful change is the consolidation of different update types into a single monthly restart. Driver updates, .NET updates, and firmware updates will now be bundled and installed alongside the regular monthly cumulative updates, reducing the total number of required reboots.
Hanson described the mechanics of this approach:
"Updates will download in the background, then will wait for a coordinated installation and restart. This installation and restart will align with the next Windows quality update or other update that you manually approve."
Users who prefer not to wait for the coordinated installation window retain the ability to manually initiate download, install, and restart for any available update at any time.
Rollout Timeline
All of these features are currently being made available to Windows Insiders enrolled in the Dev and Experimental channels. Microsoft has indicated that a broader rollout to all Windows users will follow once the features have been sufficiently tested through the Insider program. The initiative reflects a broader effort by Microsoft to balance keeping devices secure by design and by default while reducing the friction that updates introduce into everyday computing workflows.
Source: BleepingComputer