KB 5057589 update
brucine Posted messages 24397 Registration date Status Membre Last intervention -
Hello,
This update does not install. Is it important? I have used repair tools. All other updates install correctly, just not this one.
Have a good evening
3 réponses
Good evening,
Restart your PC to see.
Do you have the error message "0x80070643" appearing in Windows Update?
Known issue
Symptom
After installing this update, the following error message may appear on the Windows Update settings page: 0x80070643 – ERROR_INSTALL_FAILURE. This error message is not accurate and does not impact the update or the device's features. Although the error message suggests that the update did not complete, the WinRE update is usually applied correctly after the device is restarted.
Windows Update may continue to show the update as failed until the next daily scan, at which point the update is no longer offered and the failure message is automatically cleared.
See this chapter also on the hyperlink.
Hello,
For KB5057589
https://support.microsoft.com/en-us/topic/kb5057589-windows-recovery-environment-update-for-windows-10-version-21h2-and-22h2-april-8-2025-74bc2baa-4ac6-40d0-8dde-4a8462b8f7e7
You may need to manually resize your WinRE partition.
(The recovery partition on the right)
So reduce C: first and increase the space of the last partition on the right to 1GB or so.
This can be done quite simply with a program like Macrorit Partition Expert Free Portable.
https://macrorit.com/partition-magic-manager/partition-expert-download.html
Hello and thank you for your quick response
My recovery partition is 16 GB. But while browsing the internet, I came across this article from Microsoft and I will therefore ignore all these errors as long as the other updates install normally
Have a good day
Hello,
By the way, the Windows recovery partition cannot be 16 GB; this is a confusion with the manufacturer recovery partition that exists on certain brands of PCs.
It typically ranges from about 600-800 MB, and an insufficient size was questioned in a previous update, but in this case, it is indeed not relevant as it's a Microsoft bug to be dealt with by ignoring it after restarting.