Is there a workaround for KB5034441 install failure that doesn't require partition modification?

KB5034441 is a pain.

After digging around, in bios I found its in legacy mode and the drives were created using MBR.

My recovery partition was already approaching 1Gb so didn't resize, as according to the maths that go with KB5034441 that part was sucessful!!

So why is KB5034441 failing?

Turns out there is no WinRE recovery image (winre.wim) on my recovery drive, mounting it reveals its totally empty!

Found some instructions on how to extract recovery files from an iso, placed it on the main system partition then pointed REagentC to its location. KB5034441 now installs, increasing the size of the wim file from 450ish to 700ish Mb.

In my case 0x80070643 probably means no WinRE recovery image found!

Ideally why would you even enlarge the recovery partition? Why not just create a new partition at the end of the disk and just re-point the recovery partition pointer to that after proper formatting and data copying?

No need for deletions, no need for reagentc commands aside from /info.

But why would you use Paragon (MiniTool/AOMEI/EaseUs) to shrink drive C if you have disk management available? No reboot, and certainly no 20 minutes required.

You never need a tool to shrink drive C as there is always disk management and diskpart.

You never need to delete a partition unless you resize relying on Windows facilities.

You never need to resize with BitLocker disabled.

So let me get this right, because the arithmetic is confusing me. You resize the partition from 500MB to 1GB. That takes 1200 seconds? That is a operating speed of just over 447KB/sec. Which makes no sense on a modern Windows machine with even an Intel i3 and an HDD.

Ideally why would you even enlarge the recovery partition? Why not just create a new partition at the end of the disk and just re-point the recovery partition pointer to that after proper formatting and data copying? And on an SSD that would be the proper thing to do and just trim out the old retired one. However, because of the complexity of the OS, only Microsoft developers know where the pointers needing change reside.

So Microsoft putting this on users and not fixing it with a second KB sets a pretty low quality bar, IMHO. Especially if it requires "outside of the repository" software installs to fix, or kludgy fixes with several steps and high probability of failure for those lacking knowledge. Having an uninstallable update increases the attack surface of the OS because of the unknown future ramifications of it not installing. At least until whenever in 2025 that Windows 10 crosses the Rainbow Bridge. Then it won't matter unless you keep using it ;-)

You have to extended the recovery partition.

I used Paragon Software Free Edition.

After install it will ask for recovery solution, just cancel and go right into the partition resizing.

Adjust space of main partition which provides room for the recovery.

It will ask you to reboot.

It will pop up a Paragon boot screen while it makes the adjustment. Mine took around 20 minutes.

Booted back into Windows as normal

Ran the KB update.

Installed as expected.

Done. https://www.paragon-software.com/us/home/hdm-windows/

My recovery partition is currently 584Mb and apparently has 100% free!

See this reply by Ramesh Srinivasan: "Disk Management doesn't show the free space in the Recovery partition. It always shows 100% free. It's misleading."

Can't install 2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)