This Windows 10 bug looks serious - but apparently it's lying

Image Credit - Clint Patterson on Unsplash.com
A new sneaky bug has made its way on Windows 10 machines, seemingly affecting an important update. But Microsoft is saying you shouldn't worry about it, literally.
Windows updates are always somewhat of a hassle. It's quite often that unexpected things occur after an update, and Windows users are used to a seemingly innocuous update knocking things over in passing.
Now, one of the latest updates (KB5057589), which is the Windows 10 21H2 and 22H2 April update, brings an interesting bug that may stress you out when you see it. The update started rolling out recently, on April 8 and is focused on the Windows Recovery Environment (WinRE), aimed at applying Safe OS Dynamic update to advance Windows recovery features.
Despite Microsoft's best intentions though, some unfortunate users have been encountering an annoying 0x80070643 error when installing an update, with an "ERROR_INSTALL_FAILURE" message accompanying it.
Microsoft just wants you to ignore the bug. Yes, you read that right: forget about it.
In the official support document for the update, the company is highlighting the error with WinRE alongside a few other priority issues. Some of the other issues listed have since been resolved (USB printers giving random text or a bug impacting dual Windows-Linux boot setups).
The company says it's working on a fix but in the meantime, it suggests you just revert back to the IT classic: getting off the car and getting back in. So basically, turning the machine off and on again, and checking back later if the problem persists.
You may be thinking that Microsoft has just given up on fixing it as Windows 10 is nearing its October 14, 2025 end-of-support date anyway. But it seems in this case, the solution really is to ignore the bug.
Microsoft notes that the 0x80070643 - ERROR_INSTALL_FAILURE message is basically not true. The company says it's inaccurate and it won't impact the functionality of Windows Repair. This error is seen normally when there is another update in the pending reboot state, and the update should typically show as complete after a successful restart.
If the restart doesn't resolve the issue, Microsoft again says not to fret. The support documentation blatantly states to give it time, as you know, time heals all wounds. Apparently, including this Windows 10 one.
Microsoft notes that Windows Update may continue showing the update as failed but after the next daily scan, the message should be cleared automatically.
Windows 10 is nearing its end-of-support date though. Recently Microsoft published a checklist for people still running Windows 10, somewhat gently urging them to upgrade their PC with a message written between the lines.
After the October 14, 2025 date comes, Microsoft will stop supporting Windows 10 machines. This means you won't receive security patches, features, or technical support (unless you have opted in for Microsoft's Extended Security Updates program, which covers one more year of support for $30).
Meanwhile, Windows 11 is getting richer and richer as we speak, with many features being introduced, including powerful generative AI ones. One of the newest additions will let Copilot, Microsoft's AI assistant, read your screen and even somewhat interact with your apps if you allow it. Windows 11 is also actively supported by getting important bug fixes, security patches, and new features on a regular basis.
Also, Windows 11 now has a new change to its Start menu which will now be bigger and more streamlined with an update Microsoft is cooking. You will also soon be able to sign password-less-ly, while the infamous Blue Screen of Death is also getting a new look.
A new sneaky bug has made its way on Windows 10 machines, seemingly affecting an important update. But Microsoft is saying you shouldn't worry about it, literally.
Windows updates are always somewhat of a hassle. It's quite often that unexpected things occur after an update, and Windows users are used to a seemingly innocuous update knocking things over in passing.
Despite Microsoft's best intentions though, some unfortunate users have been encountering an annoying 0x80070643 error when installing an update, with an "ERROR_INSTALL_FAILURE" message accompanying it.
Yep, this potentially means one of Windows 10's most important tools for protecting your data is failing to install. And if this has you worried you will find an unbootable system not too long after, well, you should relax, at least according to Microsoft.
In the official support document for the update, the company is highlighting the error with WinRE alongside a few other priority issues. Some of the other issues listed have since been resolved (USB printers giving random text or a bug impacting dual Windows-Linux boot setups).
The company says it's working on a fix but in the meantime, it suggests you just revert back to the IT classic: getting off the car and getting back in. So basically, turning the machine off and on again, and checking back later if the problem persists.
You may be thinking that Microsoft has just given up on fixing it as Windows 10 is nearing its October 14, 2025 end-of-support date anyway. But it seems in this case, the solution really is to ignore the bug.
Microsoft notes that Windows Update may continue showing the update as failed but after the next daily scan, the message should be cleared automatically.
Windows 10 is nearing its end-of-support date though. Recently Microsoft published a checklist for people still running Windows 10, somewhat gently urging them to upgrade their PC with a message written between the lines.
After the October 14, 2025 date comes, Microsoft will stop supporting Windows 10 machines. This means you won't receive security patches, features, or technical support (unless you have opted in for Microsoft's Extended Security Updates program, which covers one more year of support for $30).
Also, Windows 11 now has a new change to its Start menu which will now be bigger and more streamlined with an update Microsoft is cooking. You will also soon be able to sign password-less-ly, while the infamous Blue Screen of Death is also getting a new look.
Things that are NOT allowed: