Windows Recovery

Winsage
May 18, 2025
Windows 10 users are facing issues due to the mandatory KB5058379 update, which has caused some PCs to boot into Windows Recovery mode and prompted the need for a BitLocker key. Some users have also experienced a Blue Screen of Death (BSOD). The update primarily affects devices with Intel Trusted Execution Technology (TXT) using 10th generation or later Intel vPro processors, particularly on Windows 10 versions 22H2 and Windows 10 Enterprise LTSC 2021. Microsoft is working on a resolution and plans to release an Out-of-band update soon. Affected users are advised to disable Intel TXT in the BIOS to complete the update successfully and avoid further issues. Windows 11 is not impacted by this problem.
Winsage
May 16, 2025
The Windows 10 KB5058379 cumulative update, released on May 13, 2025, has caused unexpected BitLocker recovery prompts for some users after installation and reboot. Reports indicate that affected devices, including those from Lenovo, Dell, and HP, automatically boot into the Windows Recovery Environment and display the BitLocker recovery screen. Users have experienced various issues, such as needing BitLocker keys to start up or devices refusing to start. A workaround involves disabling Intel Trusted Execution Technology (TXT) in the BIOS. Microsoft has not publicly acknowledged the issue but support representatives are aware and working on a resolution. Microsoft has provided steps to resolve the issue, including disabling Secure Boot and virtualization technologies, checking Microsoft Defender System Guard Firmware Protection status, and disabling firmware protection via Group Policy or Registry Editor.
Winsage
April 24, 2025
Microsoft has resolved a known issue causing 0x80070643 installation failure errors during the deployment of the April 2025 Windows Recovery Environment (WinRE) updates. This issue affected the KB5057588 update for Windows Server 2022 and the KB5057589 update for Windows 10, versions 22H2 and 21H2. The error message was misleading, as it did not reflect the actual status of the update or the device's performance. The error typically occurred when a device attempted to install the WinRE update while another update was pending a reboot. Microsoft confirmed that users will no longer see the incorrect error message after installing the affected updates. Additionally, in August of the previous year, Microsoft retired the January 2024 Windows security updates that also triggered 0x80070643 errors during WinRE updates. During that time, fraudulent IT support websites promoted malicious PowerShell "fixes" for these errors, leading to malware infections among users.
Winsage
April 15, 2025
The April 2025 Windows Recovery Environment update, identified as KB5057589, has caused confusion among Windows 10 users due to an error message (0x80070643 – ERRORINSTALLFAILURE) encountered during installation. Microsoft clarified that this error is a nuisance and does not affect the update or device functionality. The update enhances recovery features for devices facing booting issues and is delivered through Windows Update. Users may see the error if the update is installed while another update is pending a reboot, but the update typically installs successfully after a restart. Microsoft is working on a resolution to address user concerns.
Winsage
April 15, 2025
Microsoft has acknowledged that some users may experience installation failures with error code 0x80070643 when deploying the April 2025 Windows Recovery Environment (WinRE) updates, specifically affecting the KB5057589 update for Windows 10 versions 22H2 and 21H2, and the KB5057588 update for Windows Server 2022. The company stated that this error is misleading and does not affect device functionality, as the WinRE update is typically applied successfully after a device restart. Users may see a failure indication in Windows Update, but this will be resolved after the next daily scan and restart. Microsoft is working on a resolution for this issue, which follows a similar situation from August 2024. Additionally, fraudulent IT support websites have been identified promoting malicious PowerShell "fixes" for these errors.
Search