startup failures

Winsage
August 20, 2026
Following the KB5121003 Patch Tuesday update, users on ARM64 devices like Surface Laptop 7 and Surface Pro 11 are facing startup failures with Microsoft Teams and New Outlook, while traditional Win32 applications remain unaffected. Reverting to the previous update restores functionality, but recovery options have not resolved the issue. The root cause appears to be broken AppModel Runtime package states, leading to dependency issues and 0x80073CFC errors. This problem is similar to one caused by update KB5094126 earlier this year. Creating new Windows profiles offers only temporary relief, and administrators are advised to pause the deployment of KB5121003 on ARM devices until the issue is addressed.
Winsage
June 17, 2025
Microsoft released an emergency update (KB5063159) to address startup failures in certain Surface Hub v1 devices running Windows 10, specifically those encountering Secure Boot Violation errors after installing the June 2025 Windows security update (KB5060533). The issue was limited to Surface Hub v1 systems on Windows 10, version 22H2, and did not affect Surface Hub 2S and 3 devices. Microsoft paused the rollout of the KB5060533 update on June 11, 2025, to prevent further complications. Additionally, the June 2025 Patch Tuesday updates included security patches for 66 vulnerabilities, including critical ones that allowed remote code execution and privilege escalation.
Winsage
June 13, 2025
Microsoft is addressing an issue with Surface Hub v1 devices running Windows 10, version 22H2, where users encounter Secure Boot errors after installing the KB5060533 security update released in June 2025. The error message states: 'Secure Boot Violation. Invalid signature detected. Check Secure Boot Policy in Setup.' This issue is specific to Surface Hub v1 and does not affect Surface Hub 2S and Surface Hub 3 models. Microsoft implemented a mitigation strategy on July 11, 2025, to prevent further startup failures on additional Surface Hub v1 devices. The KB5060533 update aimed to fix issues with Hyper-V virtual machines and was part of a larger rollout addressing 66 vulnerabilities, including critical ones related to WebDAV and Windows SMB. Additionally, an emergency update for Windows 11 (KB5063060) was released to fix an incompatibility with Easy Anti-Cheat causing BSOD errors.
Winsage
May 29, 2025
Microsoft has acknowledged that some Windows 11 systems may experience startup failures after installing the KB5058405 cumulative update, resulting in a 0xc0000098 recovery error related to ACPI.sys. This issue affects Windows 11 versions 22H2 and 23H2, particularly in enterprise settings like Azure Virtual Machines and on-premises virtual machines. Home users are less likely to encounter these problems. Microsoft is investigating the issue and will provide updates.
Search