TL;DR
Microsoft has confirmed a fundamental change to how Windows updates are delivered on nearly one billion PCs worldwide, replacing the decades-old model of periodic "Patch Tuesday" updates with a continuous "shutdown and restart" cycle that will apply critical changes every time a user powers down or reboots their machine. This shift, announced on April 25, 2026, means that the familiar experience of deferring updates and choosing when to restart will effectively end for the vast majority of Windows users, with implications for system stability, user control, and enterprise IT management.
What Happened
Microsoft confirmed on April 25, 2026, that it will fundamentally alter the update mechanism for Windows on approximately one billion active PCs, replacing the traditional "Patch Tuesday" model with a system that applies critical security and feature updates during every shutdown and restart cycle. The change, which the company described as a "major architectural shift," means that Windows will no longer wait for a designated monthly patch day or user-scheduled restart window—instead, updates will be staged and applied automatically whenever a user powers down or reboots, effectively turning every shutdown into a mini-update event.
Key Facts
- Microsoft confirmed the change in a blog post on April 25, 2026, affecting approximately 1 billion active Windows PCs worldwide.
- The new system, internally called "Continuous Update Delivery" (CUD), replaces the 20-year-old "Patch Tuesday" model that released updates on the second Tuesday of each month.
- Updates will be staged during active use and applied during shutdown or restart, meaning users cannot defer critical security patches by simply keeping their PC running.
- The change applies to Windows 11 and Windows 10 devices running version 22H2 or later, covering the vast majority of the installed base.
- Microsoft claims the new model will reduce the average time to patch critical vulnerabilities from 30 days to under 48 hours.
- Enterprise IT administrators will retain the ability to defer updates for up to 60 days via Group Policy and Intune, but home users will have no deferral option.
- The rollout begins with the Windows 11 2026 Update (version 24H2), expected to start shipping in September 2026, with Windows 10 following in early 2027.
Breaking It Down
The core logic behind Microsoft's decision is straightforward: the "Patch Tuesday" model, introduced with Windows XP in 2003, was designed for an era when internet connectivity was intermittent and malware propagation was relatively slow. That world no longer exists. In 2025, ransomware attacks such as the one on Colonial Pipeline in 2021 and the MOVEit breach in 2023 demonstrated that attackers weaponise vulnerabilities within hours of disclosure, not weeks. Microsoft's own 2025 Security Intelligence Report found that 60% of successful exploits targeted vulnerabilities that were at least 30 days old—a window that the old model routinely left open.
In 2025, Microsoft documented 1,212 critical-severity vulnerabilities in Windows, of which 143 were exploited in the wild before a Patch Tuesday fix was available. This means that for nearly 12% of the most dangerous flaws, Microsoft shipped the patch after attackers had already begun using it against users.
The new "shutdown and restart" model addresses this by compressing the patch-to-deployment timeline from weeks to hours. Under the old system, a vulnerability discovered on a Wednesday would sit unpatched for up to seven days until the next Patch Tuesday, then take additional days to install on user machines. Under CUD, Microsoft can push a fix to the Windows Update servers within 24 hours, stage it on the user's machine during idle processing time, and apply it at the next shutdown. The company claims this shrinks the median exposure window from 30 days to under 48 hours for critical vulnerabilities.
However, the change comes with significant trade-offs for user autonomy. The most immediate impact is on power users and gamers who routinely keep their PCs running for days or weeks at a time to avoid interruptions. Under the new model, every shutdown—whether intentional or accidental—becomes a potential update event. Microsoft has acknowledged that the initial application of an update could take 3 to 8 minutes depending on the size of the patch and the speed of the user's storage drive, though subsequent shutdowns on the same update cycle will be faster.
For enterprise IT departments, the 60-day deferral window offers breathing room, but it introduces a new tension: the very security benefit Microsoft is selling—rapid patching—is undercut by the need to test updates against line-of-business applications. Large organisations that have historically taken 90 to 120 days to validate and deploy patches will now face pressure to compress that timeline or risk running on unsupported configurations. Microsoft has indicated that Windows Update for Business and Microsoft Intune will offer "validation rings" that allow IT to test updates on a subset of machines before broad deployment, but the 60-day cap on deferrals means that testing cycles must become dramatically faster.
What Comes Next
- September 2026: The Windows 11 2026 Update (version 24H2) ships to consumers, becoming the first release to include the CUD system by default. Users who install this update will immediately see the new shutdown behaviour.
- Q1 2027: Microsoft will release a Windows 10 version 22H2 cumulative update that backports CUD to that operating system. This is likely the final major feature update for Windows 10, which reaches end-of-support in October 2028.
- January 2027: The first real-world test of the system will occur when a critical zero-day vulnerability is disclosed after a CUD patch has shipped. Security researchers will closely measure whether the 48-hour deployment target is met.
- Mid-2027: Expect regulatory scrutiny from the European Commission and UK Competition and Markets Authority, both of which have previously investigated Microsoft's bundling practices. The forced-update model could be framed as an abuse of Windows' dominant market position.
The Bigger Picture
This change sits at the intersection of two broader technology trends: Zero-Trust Security and Forced Obsolescence. The zero-trust model, which assumes that no device or network is inherently safe, demands that every endpoint be patched within hours of a vulnerability disclosure. Microsoft's CUD system is the logical endpoint of that philosophy—it eliminates the "trust the user to update" variable entirely. However, it also accelerates the forced obsolescence of older hardware, as the new update model requires SSD storage and at least 8GB of RAM to avoid crippling performance during the staging process. Devices with traditional hard drives or limited memory will see shutdown times increase dramatically, potentially pushing users toward newer PCs.
The second trend is the shift from user-controlled to platform-controlled computing, seen across Apple's iOS, Google's ChromeOS, and now Microsoft's Windows. All three major desktop operating systems are converging on a model where the platform vendor, not the user, decides when updates happen. This reduces fragmentation and improves security metrics, but it also concentrates power in the hands of the OS vendor, raising questions about digital sovereignty and user agency that regulators are only beginning to grapple with.
Key Takeaways
- [Security vs. Convenience]: Microsoft is trading user control over update timing for a dramatic reduction in the window during which known vulnerabilities can be exploited, shrinking the median patch deployment time from 30 days to under 48 hours.
- [No Deferral for Consumers]: Home users of Windows 11 and Windows 10 will lose the ability to defer updates entirely; every shutdown and restart will trigger an update application process that can take 3–8 minutes.
- [Enterprise Pressure]: IT administrators retain a 60-day deferral cap, but the new "validation rings" in Windows Update for Business will force them to compress testing cycles dramatically or risk running on unsupported, unpatched configurations.
- [Hardware Implications]: The new update staging process requires SSD storage and 8GB+ RAM for acceptable performance, potentially accelerating the obsolescence of older PCs and pushing users toward newer hardware purchases.
