Updated July 21: This article, originally published July 20, has been updated to include yet another example of Microsoft update failure, this time involving Windows Server Update Services, in addition to the out-of-band fix that has been rolled out to address problems some Dell users faced after the latest Patch Tuesday security update.
An emergency, out-of-band security update for Windows 11 version 25H2 and Windows 11 version 24H2 has been released by Microsoft. This follows a highly unusual turn of events that led Microsoft to block the July Patch Tuesday KB5101650 update for some Dell users after it was determined to cause performance issues and, in some cases, system shutdowns.
The issue, it would appear, was related to the latest Windows USB-C Connection Manager interface conflicting with the Intel Innovation Platform Framework Processor Participant driver. Although I do not have a list of all impacted Dell devices, I am aware that the following were among those that Microsoft blocked: Dell Pro Max 14 Premium MA14250, Dell Pro Max 16 Premium MA16250, Dell XPS 17 9720 and Dell XPS 17 9730.
Microsoft has stated that the new out-of-band update, officially labeled as KB5121767 for Windows 11 builds 26200.8894 and 26100.8894, is only recommended to be installed by users of Dell devices that have been impacted by the performance-related issues. “If your device is not affected,” Microsoft said in an update announcement, then “no action is required.”
Imperfect Microsoft Security Updates Remain A Problem
Microsoft security updates remain essential to protect your device and the data from an ever-expanding threat surface, yet as we have seen time and time again, they can oftentimes have unexpected and concerning consequences. Whether it’s breaking VPN connections or preventing critical third-party data backup services from working properly, the real damage comes from diluting trust in the very users whose security is partly reliant on applying these patches in good time. Any increase in uncertainty regarding negative security update issues is never going to be a good thing.
A great example can be found as recently as April 2026, when Microsoft rolled out an optional security update for Windows users that included a replacement Secure Boot certificate. In short order, users started complaining about multiple system reboots rather than the one expected with a security update. Perhaps unsurprisingly, many of these users called foul on the update itself, which in turn led to unofficial support forums and social media accounts advising users not to install it. Yet, as I reported at the time, the reboot behavior was intentional and nothing to worry about. Microsoft itself said that some users “might experience one additional restart during installation,” as the restarts occur “after a Secure Boot certificate update is applied as part of the Secure Boot update process.”
Microsoft has now confirmed yet another update problem for some Windows users, specifically involving Windows Server Update Services that can lead to the failure of Windows Update scans. The latest announcement comes by way of a manual fix, deep joy, for the sync delay issues that have impacted users of both client and server platforms.
The official Microsoft notification said: “This issue is related to a buildup of publishing metadata which is present on existing WSUS server installations as well as from the service side.” The impacted platforms are:
On the client side: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
On there server side: Windows Server 2025; Windows Server 2022; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Microsoft has advised that as well as a service-side mitigation which returns synchronization times and sync operations back to normal for new WSUS installations and rebuilds that was deployed on July 18, organizations with existing WSUS server installations are recommended to clean up unneeded metadata. Detailed guidance has been provided here.
So, while Microsoft has fixed the latest Patch Tuesday update issue for some Dell users, the bigger problem remains. If AI is so good at finding vulnerabilities, and record-breaking security update rollouts provide the evidence for that, maybe Microsoft should find a way to use it to better test such criticial updates before they get released and deployed by users?
