- Windows 10 recently got a patch tinker with the recovery environment
- Some users see an error message that says patchet not installed
- In fact, the update is installed just fine and the error message is the error
Some Windows 10 users encounter an error message after applying a fresh patch to the operating system and informing them that the update failed – when it didn’t actually do.
Neowin discovered that update (known as KB5057589), released last week (separately from the main cumulative update for April) and Tinkers with Windows Recovery Environment (Winre) on some Windows 10 PCs (versions 21H2 and 22H2).
Far from all Windows 10 users get this, but those who do can be confronted with an error message after it has installed (which is visible on the Windows Update settings page).
It reads: “0x80070643 – error_install_failure.”
Of course, it looks alarming and when you see this you will take the fair assumption that the update has failed. As mentioned, however, the error is not with the update, but the error message itself.
Microsoft explains: “This error message is not accurate and does not affect the update or device’s functionality. Although the error message suggests that the update has not completed, the Winre update is typically used successfully after the device restarts.”
Microsoft also notes that the update may continue to appear as ‘failed’ (when it has not done so) before the next check for updates, after which the error message must be cleared from your system.
Analysis: Bugs in the errors
There is nothing wrong here, in short, except the mistake itself, but it will confuse people, and maybe send them some unnecessary – and potentially long – rabbit holes to find further information or a solution to a problem that does not exist.
The problem is what aggravates this is that the whole Winre debate has been a long-lasting affair. A patch for this was previously released in January 2025 recently, and there were others before that, with some people who witnessed repeated installations of this winre -fix, which is confusing in itself.
Therefore, the rabbit holes that you may be lost may end up appearing so deeply if you are unable to catch Microsoft’s clarification on this case.
Microsoft says it is working to solve this wrong mistake and will tell us when it happens. At least you are now armed with the knowledge that the update should be fine despite what the error – in block capitals that are plastered across your screen – tells you (and it should be cleared from your PC in a short time).
