Windows 11 Update Fixes Boot Failures After Failed Installs
▼ Summary
– Microsoft has resolved a Windows 11 boot failure bug with a fix delivered in the February 2026 Patch Tuesday update (KB5077181).
– The issue, which caused an “UNMOUNTABLE_BOOT_VOLUME” error and a black screen, affected a limited number of commercial devices running Windows 11 versions 25H2 and 24H2.
– The boot failures occurred after installing the January 13, 2026, security update (KB5074109) on systems left in an improper state by a failed December 2025 update.
– Microsoft had released an initial preventative fix in an optional January 29, 2026, update, but devices that became unbootable before the February fix may still require manual recovery.
– The advisory was shared privately with enterprises, and Microsoft has not publicly explained why this issue was not communicated more broadly.
Microsoft has successfully addressed a significant Windows 11 bug that was causing certain commercial systems to become unbootable. The resolution arrived with the February 2026 Patch Tuesday security update, specifically KB5077181, which fully resolves the problem. This issue, which manifested as a black screen with an “UNMOUNTABLEBOOTVOLUME” error, prevented affected devices from starting up normally and required manual recovery efforts to restore functionality.
The problem was traced back to a failed installation of a security update from December 2025. When that update did not install correctly and rolled back, it left devices in what Microsoft termed an “improper state.” Attempting to install subsequent updates, such as the January 13, 2026, update KB5074109, on a system in this state could trigger the boot failure. The error message displayed read: “Your device ran into a problem and needs a restart. You can restart,” though restarting did not solve the issue.
According to information from a private enterprise advisory, this bug impacted a limited subset of devices. It specifically affected physical machines running Windows 11 versions 25H2 and 24H2 in commercial environments. Microsoft stated it did not receive reports of the issue affecting home users or virtual machines, confining the disruption to certain business systems.
Prior to the final fix, Microsoft released an initial mitigation in an optional non-security preview update, KB5074105, on January 29, 2026. This update was designed to help prevent additional systems from falling victim to the boot problem. However, the company now confirms that the issue is completely resolved in the February security update and all later updates.
For enterprise IT administrators, it’s important to note that devices which became unbootable before the fix was applied may still need direct intervention. Microsoft advises commercial customers with persistently affected devices to contact Microsoft Support for Business to receive assistance in restoring system stability. The company did not publicly share this advisory, opting instead to communicate directly with enterprise clients through private channels.
(Source: Bleeping Computer)
