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

It is curious that the size of the current disk-drive is 200 GB.

This implies that the disk-drive is very old, because "new" disk-drives usually are sized as 120 or 128 or 240 or 256 or 500 or 512 or 1024 GB. Old disk-drives "spin", causing "rotational delay" each time there is read/write access. Also, old disk-drives transfer data at either "SATA" (1.5 Gbps) or "SATA2" (3 Gbps) or "SATA3" (6 Gbps) speeds. New disk-drives transfer at "SATA3" speed, if the motherboard supports it, or at "SATA2" speed. New disk-drives have ZERO "rotational delay", making them much faster.

The posted image points to "partition5" as the WinRE partition -- not to "partition1". So, I suspect that if you attempt a "recovery", then "partition1" will NOT be used. One way to confirm this is:

1. take a brand-new SSD (or NVMe), at least 256 GB in size
2. use disk-cloning software to copy the current disk-drive onto the new SSD, keeping the partition-sizes the same,
3. on the new disk-drive, delete (or format) that 450 MB partition,
4. disconnect the old disk-drive, and connect the new disk-drive,
5. set aside the old disk-drive, and label it as "last used on December 2024", to be used in any "disaster recovery" plan that you might have,
6. restart Windows from the new disk-drive.

Is the computer any faster, when using the new disk-drive?

Note that the old disk-drive probably is many years beyond its initial 1 or 2 year warranty. Compare to an auto tire with almost no tread left -- not too safe, because the tire (or the old disk-drive) may "blow" at any time.

Note: when cloning, by keeping the partitions the same size, you should have some "free" space at the end of "partition5". You should be able to use DISKPART to "expand" that partition, to make it much larger. Or, when "cloning", allow the process to "expand" that "partition5", as it copies it, because you are cloning from a 200 GB disk-drive to a 240 (or 256) GB disk-drive.

Then, rerun Windows Update, to see if applies successfully.

Good luck!

Hi Melvin, thanks for the reply.

let me take one at a time.

1. the W10 guest is on a W2012 R2 HyperV host. The guests also seem to run in slow motion. but thats another issue. Right now there is the Host and two W10 guests, one is my plex server which is disabled since I am working on recovering the plex drive.
2. W11 is only on my desktop, and just updated last week, and not related to the HyperV machine.
3. on the 100% disk, it lasts a long time, it must be related to the slowness of the guest running which would then make sense.

I'll see if I have some time this weekend to move the 450mb partition and add it to the active RE partition

is this the cause of the non-install issue I am getting even though the partition is way big enough?

Thanks leon

> On this end this is a W10 Hyper-V guest.

Do you have a Windows 11 "host", with Hyper-V having a Windows 10 "guest" operating system?

> I also have two recovery partitions one is 450mb and the other is 789mb which is the active one and is at the end of the disk after my C:

The early releases (in 2015) located the "Recovery" partition at the start of the disk-drive. That explains the 450 MB partition.

When I use the "reagentc /info" command, I see:

**Recovery Environment:** 

*\?\GLOBALROOT\device\harddisk0\partition2\Recovery*

Harddisk "zero" is my computer's first disk-drive,

while "partition2" is the 3rd partition on my disk-drive.

Do you see "partition1" in the output on your computer, or "partition5 ? If the former, then that partition is too small for the update to be applied. If the latter, then the 789 MB might be too small.

Do not believe that "0% used" tag for your "partition 5".

Unfortunately, the "hidden" files/folders are not counted, when giving that "0%" result. Sigh.

You must have installed Windows 11 a LONG time ago, to have that partition at the start of your disk-drive.

There do exist free utilities that will "shrink" your "C:" partition by some amount, e.g., 1000 MB, and then to "expand" your 5th partition by that amount, namely 1000 MB plus the 790 MB.

Then, retry the Microsoft update.

I also have the dreaded C: 100% disk utilization on this guest.

Since you seem to be using Hyper-V, are you measuring the utilization on the "host" operating system, or are you measuring the (virtual) disk utilization on the "guest" ?

Note that restarting Windows (10 or 11) after a Windows Update may trigger:

• a virus-scan
• disk-drive optimization ("defragmenting")
• updating the Windows Search "cache" after noticing new/changed files

Any of these will result in a short-term "100%" condition.

ok looks like now that there is a message I can upload images???

I've looked through this thread and tried I think almost every idea but still fails. On this end this is a W10 Hyper-V guest.

For some reason i can not upload any images here it fails to upload :-(

I also have two recovery partitions one is 450mb and the other is 789mb which is the active one and is at the end of the disk after my C:

I also have the dreaded C: 100% disk utilization on this guest.

I'm almost at wits end with the same issues seeming to keep cropping up.

TIA Leon Zetekoff