Microsoft has commenced the rollout of enhancements to its Windows Update system, aiming to provide users with increased control over update installations and to minimise disruptions caused by unanticipated restarts. This initiative responds to critical user feedback highlighting the frequent disruption of workflows and a perceived lack of control regarding update timings.
Aria Hanson from Microsoft noted that the company has reviewed extensive user responses, revealing persistent concerns regarding untimely updates. The forthcoming changes focus on affording users greater autonomy while maintaining device security.
A significant update introduces a feature allowing users to bypass updates during the out-of-box experience (OOBE), thereby enabling quicker access to the desktop and permitting update installations at a more suitable time. However, this option is not applicable to managed commercial devices or systems necessitating updates for operation.
Additionally, Microsoft is amending the update pause function, enabling users to select a specific date to pause updates for a maximum of 35 days via a simple calendar interface. Users can extend this pause indefinitely, responding to demand for more flexible update management.
Another key adjustment addresses complaints about unexpected updates during power-downs. The Power menu will now differentiate between standard shutdown and restart options and those that initiate updates, thus preventing unexpected disruptions.
Further improvements include clearer listings for updates, specifically drivers, now labelled by device type such as display or audio. This clarity aims to assist users in identifying necessary installations easily.
Lastly, Microsoft is consolidating various update types into a single monthly restart, which is expected to significantly reduce required reboots. Updates will download in the background and will wait for a coordinated installation and restart that aligns with user-approved timings. The enhancements are currently accessible to Windows Insiders in the Dev and Experimental channels, with a full rollout planned for all users thereafter.
Test Your Understanding
How much do you know?
