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

Thanks

What I need to find is something that will test the actual sectors in the RAID array and move then and mark bad. I've been trying to move via ftp the files off to a friends site and it's been running for months due to the timeouts and errors becuz if I can get all the files off safely then I will reformat the drives in that RAID.

leon

> Trying to find a good utility to test the RAID.

The free version of the SPECCY app can display the S.M.A.R.T. status of a non-RAID disk-drive, and much more.

Otherwise, the "Intel RST" utility will report the status of the RAID, e.g., "normal" or "degraded".

.

Hi Melvin,

I found this tool windows update fixer and giving it a whirl and will also look at what you suggested.

a few quick items.

The Hyper-V is a Dell server with 64gb ram and 8 TB disk of which 6TB is my plex raid and 2gb is Windows Server 2012 R2. I believe its SAS drives 2TB each I think. Was given this machine a few years ago from a friend/co-worker

The guest is 200MB as that is what I defined it to be it's a virtual disk which is on the 2GB disk the server OS is as a separate drive.

somewhere on my plex data drive i think there are hardware issues. i have the plex data drive defined on the Host machine instead of the guest. Trying to find a good utility to test the raid. Got multiple things going on driving me nuts :-)

I'll keep you posted many thanks

Leon

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