boot failures

Winsage
March 6, 2026
Microsoft addressed an issue in the Windows Recovery Environment (WinRE) that arose after the final update for Windows 10 on October 14, 2025, which disrupted WinRE functionality on some devices. The same update also caused accessibility issues for USB devices in Windows 11's recovery environment. Microsoft released an out-of-band patch, but some Windows 10 users continued to experience WinRE problems. The fix, KB5068164, targets Windows 10 versions 21H2 and 22H2 and aims to resolve the issue preventing WinRE from starting after the October 14 update. Concerns about Microsoft's quality control have been raised due to the timing of the failure and the delay in providing a solution. Users of Windows 10 can rely on Microsoft's Extended Security Updates program, although the situation has caused doubts about the reliability of Microsoft's updates.
Winsage
February 26, 2026
Windows Update KB5077241, released in February 2026, is a 4.5GB feature update for the 24H2 and 25H2 versions. It poses significant performance risks for older hardware, particularly laptops and desktops without a Neural Processing Unit (NPU). Users with outdated Nvidia graphics cards, specifically the 900 Series (Maxwell) and 1000 Series (Pascal), report issues such as game stuttering, screen flickering, and system boot failures. The update also contains a flaw that inaccurately displays CPU usage in Task Manager, showing 0% utilization even under load. Many users face installation issues, encountering Error 0x800F0983, requiring them to delete update cache files and run repair tools. The update introduces features like a Taskbar Speed Test, Sysmon Security, improved Sleep/Wake functionality, and WebP wallpaper support, but many remain locked. Users can enable these features using ViVeTool with specific commands. Overall, the update is advised against for those with older Nvidia GPUs due to potential conflicts and performance issues.
Winsage
February 17, 2026
Microsoft's Patch Tuesday update, KB5077181, released on February 10, 2026, has caused significant boot failures for users of Windows 11 versions 24H2 (OS build 26200.7840) and 25H2 (OS build 26100.7840), resulting in endless restart loops. Users are reporting over 15 reboot cycles, preventing access to their desktops. Issues include System Event Notification Service (SENS) errors and DHCP problems affecting internet connectivity. Installation errors with codes 0x800f0983 and 0x800f0991 indicate potential hardware, driver, or servicing stack incompatibilities. The update was intended to address 58 vulnerabilities, including six zero-days, but the boot loop issue has overshadowed these enhancements. CVE IDs and their CVSS scores related to the vulnerabilities addressed include: - CVE-2026-21510: 7.5 - CVE-2026-21519: 7.8 - CVE-2026-21533: 8.8 - CVE-2026-20841: 7.1 As of February 15, 2026, there is no "known issues" entry in Microsoft's release notes despite user reports. Users can uninstall the update through the Control Panel if their systems are accessible, or use the Windows Recovery Environment to execute commands for uninstallation if their systems are unbootable.
Winsage
February 16, 2026
Microsoft resolved a critical bug affecting some commercial systems running Windows 11 that caused boot failures due to an "UNMOUNTABLEBOOTVOLUME" error. This issue was linked to problematic updates from December 2025 and primarily impacted devices on Windows 11 versions 25H2 and 24H2. The resolution was included in the February 2026 Patch Tuesday update, specifically the Windows 11 KB5077181 security update released on February 10, 2026. An initial fix was provided in the optional update KB5074105 on January 29, 2026. Affected devices experienced failures after installing the January 13, 2026, security update KB5074109. Microsoft recommends that enterprise customers with still unbootable systems contact Microsoft Support for Business for assistance.
Winsage
February 1, 2026
Windows 11 is facing significant issues following the January Patch Tuesday, particularly with boot failures on commercial devices. These problems are linked to both the January update and a flawed December update, leading to a "UNMOUNTABLEBOOTVOLUME" Blue Screen of Death (BSOD) error. Microsoft has indicated that devices that did not successfully install the December security update are left in an improper state, which can prevent booting when subsequent updates are attempted. While Microsoft is working on a partial solution to prevent further installations that could cause boot failures, this fix will not resolve issues for devices already affected. The company is investigating the causes of these update failures and their consequences.
Search