Security Update for Windows 10, 2024-11, KB5048239 getting error 0x80070643 when installing

For KB5048239, see:

https://support.microsoft.com/en-au/topic/kb5048239-windows-recovery-environment-update-for-windows-10-version-21h2-and-22h2-november-12-2024-c466de00-2d33-46bf-842f-11a7c189583e

For KB5042320, see:

https://support.microsoft.com/en-us/topic/kb5042320-windows-recovery-environment-update-for-windows-10-version-21h2-and-22h2-january-9-2024-f5784a62-2b82-4522-b5b2-c31b67049526

which states: This update replaces the previously released update KB5034441

which is the earlier (January 2024) update to "WinRE".

For both updates, the only "security implications" seem to be when something is installed on your computer that exploits a vulnerability in WinRE. If you don't allow that malware to be installed, then the vulnerability won't be exploited. So, without running that malware, your computer is secure.

As I earlier wrote, after applying the other "November 2024" updates, and restarting my computer, then Windows Update successfully installed the update to WinRE. Done.

Perhaps, there were some side-effect of those other updates that caused the "failure to install" issue, until Windows was restarted ???

>>> I think the problem is that there is no one at MS who understands how the original code works, and there is no one to train new employees.

I disagree. Somebody is still at Microsoft who authorized another employee to investigate the issue, code the solution (for Windows 10 & 11), test it, write supporting documentation, pass the code to employees in the QA (Quality Assurance) Department, and to pass the code to other employees who have queued it into the Monthly Update stream. Also, the code will be passed to another employee who would review the code, to see if it is applicable to Windows 12 (or whatever the next version will be called by developers).

I really doubt that Microsoft is so short-sighted to not train new hires. That is shooting oneself in the foot. Sell your shares of Microsoft, if you think that the Evil Empire is about to implode. :-)

I am glad that this worked for you, however some of us are not having any luck using the instructions given earlier and retrying the install several times - both with and without re-starting and/or powering down the computer. This continues to be exactly the same problem seen earlier this year with the WINRE environment. I don't know why MSoft can't get this update right, but they've proven that they can't at least twice. The suggestion below about ditching MS stock is a little over the top, but it seems like a real possibility if this keeps up and Windows users can't rely on clean updates. Inconsistency when updating any OS leaves a very troubling question in your mind if you continue to see that they can't get it right...

What worked for me was to puirchase a brand-new, larger, faster, in-warranty, disk-drive, and use the Macrium Reflect (commercial) software to "clone" from my antique disk-drive onto the new disk-drive.

The software can be used to "shrink" or "expand" each partition, during the copying, namely to enlarge the WinRE partition.

Then, physically detach the old disk-drive, boot from the new disk-drive, and let Windows Update successfully apply the update.

Label and keep the old disk-drive for "disaster recovery".

Done, although I wish that this path was not necessary.

cela doesn't work i can't insert a screen capture why??