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

Simon,

from your second image, I see that you have "Windows 10 22H2".

However, Microsoft Support for this "2022" version of Windows ended in October 2024. I recommend that you download the "24H2" version (writing either to dual-layer DVD-recordable media or to an (at least) 8GB USB memory-stick). Then, run the "setup.exe" in the root-folder of the image, and choose to "update" to the current level. It is possible that applying this update will also update the "WinRE" partition, which is your goal. .

From your first image, I see:

where the highlighted row seems to confirm that you have sufficient space for the update to run.

The image also shows 232 (!) Gigabytes of unallocated disk-space following the "C:" partition.

Do you have a planned usage for that space, or do you want to use Disk Management to "extend" the "C:" partition?

Simon wrote: I think that 400gb of free space can be enough for 2 updates of a few mb.

The update probably is done in a two steps:

1. add the update's files into the partition, consuming over 202 MB, if there is free-space on the disk-drive;
2. delete the superseded 200 MB of files.

So, at the end, the percentage-used has increased by 2 MB, if step #1 completed without running out of disk-space.

Compare to opening the boot of your vehicle, and adding the "winter sports" gear BEFORE removing all the "summer vacation" gear. Sometimes, you cannot do these two steps in this order, because the space inside the boot in insufficient to temporarily hold both seasons of equipment.

.

No! It doesn't work! I disabled BitLocker, repartitioned the system and recreated the recovery partition with 4 gb, updates install but return with each request or reboot of the system.

Windows has "trouble-shooter" apps.

Run the trouble-shooter app for "Windows Update" issues, and then restart your computer, and try again.

Replied to most recent, not most relevant. My bad. Regardless...

Honestly, just wait until Windows fixes it themselves, upgrade to Windows 11 like they want you to, hack the security update to fix it yourself, or learn to accept that you won't be able to update everything while using an OS that is losing support.

This happens every time Microsoft drops support for an older OS, they make "security" updates that are only available to their newer OS that aren't backwards compatible, yet release it to their older OS to get concerned users fretting and worrying until they buy into the upgrade. They've done it with every new OS drop for decades now, with Vista, XP, 7, 8, 8.1, and likely others that I'm forgetting, and now they're doing it with Windows 10.

In the past, they've even intentionally added or left in bugs for the final few "updates" that won't get noticed or addressed until they drop the OS, at which point they can legally say "we don't support that version anymore" and leave it at that, to force more users into changing to their newest OS. When Microsoft officially drops support for Windows 10 in favour of the ad-heavy windows 11 that makes them more money, they'll say that the update was not backwards compatible and "apologise" for their internal error. It's happened before, and is happening again.

As a consumer, you've done more then your part. You and a hundred others have made the company aware of the issue, you've tried every "solution" with no resolution, you've shared tons of information and jumped through all the hoops they asked you to. But as a company that technically still supports Windows 10 (for now), they're saying it's on your end despite it very clearly being on their end to avoid liability. The fact it's identical to another issue earlier this year is just unfortunate for them, and they hope users will forget that.

At the end of the day, you and the hundred other people with this problem shouldn't have to jump through all of these hoops just to install a security update from the world's largest PC supplier. They have the money, manpower, and resources to fix it, but they won't because it's almost certainly intentional. You've done your part, and so your options remain.

1. Wait for something that may never happen.
2. Fix it yourself by hacking into the security update.
3. Upgrade to Windows 11 to "fix" the issue.
4. Accept that not all updates for Windows 10 will work going forward.