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

Leon, for a non-RAID disk, maybe the free software: https://learn.microsoft.com/en-us/sysinternals/downloads/diskview  will do it.

Also, for a non-RAID disk, the Macrium Reflect software will definitely tell you about a "bad" sector, when you try to use it to "clone" the disk to an empty disk-drive. Note that the target disk needs only to be as large as the "used" size of the source disk, because it does an "intelligent" copy -- not trying to copy "free" sectors from the source.

The Macrium software used to be free for personal use, but those days are gone, unless you download from:

https://www.majorgeeks.com/files/details/macrium\_reflect\_free\_edition.html

However, for a RAID set, the "bad" sectors may be in different locations on each of the disk-drives. So, when Macrium reports a "bad" sector, you won't know which disk-drive owns it.

It's also possible that a "RAID-1" (mirrored) setup may return the data from the "good" sector on either disk. Similarly, a "RAID-5" (striped) may error-correct to return a "good" sector of data.

What to avoid is "breaking" the RAID set, by physically testing each disk-drive one at a time. Connecting the disk-drive to Windows will break the set, forcing a "rebuild".

Hopefully, booting Macrium Reflect will avoid such "breaking".

Maybe, the best solution for a RAID-1 set would be

1. purchase 2 new disk-drives.
2. connect & configure these drives as a new RAID-1 set.
3. use Macrium to "clone" from the current set onto the newly-created set.
4. disconnect the current set.
5. connect one of the old drives to a different computer.
6. run "CHKDSK" with the "/R" option, to locate bad sectors and recovers readable information.

Note that Macrium has a "continue anyway" option when it cannot read a "bad" sector. Use DISKMAP to map that sector-number to a filename.

I hope this helps.

SOLVED... WHAT AXE! :)

Hi Melvin,

tried twice to move that partition into free space with AOMEI Partition Assistant (which I had used awhile back) and not able to move it. very frustrating. Tomorrow being the first I will give it another shot when I can spend a little free (?) time. :-)

I may also go down into the basement and reboot into the RAID BIOS and see what it says too and report back

Happy New Year, Leon

update started by itself and now get 0x80070050 error this is with the partitions like this

still working to move the free space

leon

Leon,

given:

and a "spare" disk-drive (at least 2B in size), can you:

1. boot into AOMEI -- not booting into Windows,
2. "clone" that 789 MB onto the spare,
3. delete that 789 MB partition, to create 463+789 MB of free-space,
4. allocate just 1 MB of space of that free-space,
5. clone from the spare into the remaining 463-plus-789-minus-1 amount of free-space.

I am a little worried that the "reagentc /info" command originally pointed to "partition 4" as the Recovery partition, but now the 463 MB is "partition 4", while the recovery partition is "partition5".

Or, play it simple, and "clone" your original disk-drive onto a brand-new (and faster) disk-drive, while "resizing" each partition. Expand "partition 1", slightly shrinking the "C:" partition, and expanding "partition3".