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

My problem with any such fix is philosophical, and because when "adjusting" partitions a full drive backup is highly recommended, which is a pain.

The philosophical problem stems from the fact that nobody reading this post has configured the size of their Recovery partition, initially. That has been something done at the whim of the operating system when it was installed on the hard disk. I've installed hundreds of Windows machines, and not one asked me to set the size of the Recovery partition. You probably can, but that is not the default install. Since the configuration was done by Microsoft software, and the issue occurs because of a Microsoft change, it doesn't seem to be something under the control of or caused by the user.

*<removed - COC violation>*Then they wonder why we are hesitant to add dubious AI capability to the OS. Or to migrate to 11. And, BTW, I have no AI bias, I subscribe to OpenAI and Gemini.

This error has been showing up on my PC for months.

TPM access is enabled on this device.

I am not about to start doing crazy things to my system like resizing partitions.

Can Microsoft please fix this?
Or is this some lame brained ploy to get people to upgrade to Windows 11?

Because Windows 11 is a downgrade if you ask me. Less options and less useful!

So it's been like 4 months and this update STILL fails...

I just reimaged a new desktop with Windows 10 Pro and ran all updates. This update is the only one that fails... When will Microsoft get ANYONE to actually fix issues?

This desktop does NOT have TPM at all, but it's also not on Windows 11 so this shouldn't be an issue.

Apologies as I have not read all 11 pages of the thread, I'm only here to add and not investigate so wasn't going to punish myself.

We were not going to resize RE partitions of our server estate so when this update and issue came out I logged a call with MS Support, this is the fix they provided and (to date) it has worked on all affected servers:

As scoped issue, we got to know that you are getting WinRE partition on deployed devices to address security vulnerabilities.

but this update is particularly meant to the server which have WinRE partition. 

a.   If the System just don’t have Recovery partition but WinRE is still enabled on OS, it should not prevent the device from receiving the updates for WinRE.

i.          Instead, the WinRE servicing should succeed without any additional steps since we have more space to use on OS

b.  If the System is having a Recovery partition but WinRE is disabled, you need to try run “reagentc /enable” to enable the WinRE onto the Recovery partition.

i.          If the enable failed as Recovery partition is not big enough, you will need to extent the Recovery partition.

c.   If the System didn’t have a Recovery partition and WinRE is disabled (as cannot be install onto OS partition due to BitLocker), you need to manually create a Recovery partition first.

Else :

1.   Ignore installation errors on devices that do not have WINRE partitions.

2.   or fallow the below AP to bypass the updates:

Action Plan:

1. Registry key workaround that can be fallowed when installing KB5034439, KB 5034440 and KB5034441 on systems where WINRE has been disabled, or on devices with no WINRE:
   reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /f /v WinREVersion /t REG_SZ /d "10.0.20348.2201".

Same here. Increased the WinRE size to 1024MB and it worked. Spent hours on this. Thanks for the recommendation.