Microsoft May Security Patch Fails

Microsoft's May Security Update is failing for some Windows 11 users due to a boot partition size issue, leaving systems unprotected.

Some Windows 11 users are experiencing installation failures with Microsoft's May Security Update. The process typically fails during the reboot phase, at around 35-36% completion, showing a generic error message that reads, “Something didn’t go as planned. Undoing changes.” Microsoft has confirmed the cause is insufficient free space on the EFI System Partition (ESP). The issue primarily affects devices that have 10MB or less of available space on this critical partition. The installation begins but cannot complete, forcing the system to roll back the changes and leave the device unpatched.

The main impact of this failure is that affected systems do not receive the dozens of security fixes included in the May update, leaving them vulnerable to potential exploits. This is a critical concern for IT and security teams tasked with maintaining organizational security and compliance. While the problem doesn't affect all users, administrators managing multiple Windows devices need to be aware of this potential installation blocker. Identifying machines with low ESP space is key to understanding the scope of the issue within an organization and ensuring that all systems can be successfully updated and secured against known threats.

The failure of a critical security update leaves systems exposed to vulnerabilities, requiring manual intervention from IT teams to diagnose and eventually resolve the issue, increasing security risk and operational overhead.

Unpatched systems pose a significant security risk to businesses, potentially leading to data breaches or system compromise. The time IT teams spend troubleshooting this issue translates to lost productivity and increased operational costs.