Article Details

Microsoft slows Windows 11 24H2 Patch Tuesday due to a 'compatibility issue'. On your marks, get set... bork!. Microsoft has set a new record with June's security update for the time between release and an admission of borkage. The patch Tuesday update arrived yesterday and contained a number of critical fixes. However, after trumpeting its arrival for Windows 11 24H2, Microsoft hastily followed up with a warning that: "We've identified a compatibility issue affecting a limited set of these devices" and, as such, the update was being throttled. "If your device is affected, you'll receive a revised update with all the June 2025 security improvements in the near term." On the Windows release health dashboard, Microsoft defined "near term" as being "by the end of the day." It did not, however, say if the day in question was the one on its Redmond campus or the universally accepted UTC. Remember the days when signs were signs and operating systems didn't need constant patching? The Register asked Microsoft for more information on this mysterious "compatibility issue", but it has yet to respond. The leading theory on social media is that the problem might be something to do with different CPU architectures. Some users have also reported errors during installation. The throttling and rapid replacement of the patch is unusual, considering this is an update containing critical fixes. It also speaks of the quality woes affecting the team at Redmond. The rapid fixing of the problem is laudable, but the question must be asked: how did the problem get released in the first place? A simple case of someone checking the wrong option on the builder and inadvertently causing a compatibility issue, or a bug that somehow eluded all the quality gates and release previews? According to Microsoft, "This update addresses security issues for your Windows operating system." Unless, of course, it doesn't because of a mysterious compatibility issue. Instead, affected users might have to wait for a fix for the fix.