After 3 months since KB5034441 was released, it still won't install

I read - it must be empty.
But it's not - screenshot replace 5, which is the same as one I previously posted - replace 1, but the time stamp has changed
And the recovery partition we created last night is also empty - screenshot replace 6

And executing the reagent file that is in the (not empty) C:\windows\system32\recovery folder gives details in screenshot replace 7 - meangingless to me but looks to be in some script and probably does mean something to you.

So if it's done, as you say, how do I proceed to the steps you outline involving queensway and dism?

Run Windows Update

Ran Update.
There were 2 items in the update list - a defender anti-virus item, and kb5034441.
The KB sat there showing install 0% like it always has before. For a noticeable time, and I thought "it's going to break again" then it just - disappeared. No message, and no restart requested. Checked history and it's worked! screenshot.

Much relief. And many thanks to you for tolerating an old dumbass. 5 stars

Now you are member of the Champions League

Has this update been included in any of the official Microsoft Windows 10 ISOs? I typically don't use the Media Creation Tool, instead use verifiable media with something like Rufus and would like to simply do a clean install that would put me past having to worry about this update for the future.

Thank you!

As far as I know, it hasn't been updated. But the new Recovery Partition will be too small as well. In case you run a new installation, you have to now how to use copy & paste.
Then the new Recovery will be ready in less than 5 minutes.

reagentc /disable

diskpart
sel disk # (replace # by the right disk number. see diskmanagement, mostly 0 or1)
sel par 4
delete partition override
sel par 3
extend
shrink minimum=1025
create partition primary
format quick fs=ntfs label="Recovery"
set id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
gpt attributes=0x8000000000000001
exit

reagentc /enable

Pentagon said:

As far as I know, it hasn't been updated. But the new Recovery Partition will be too small as well. In case you run a new installation, you have to now how to use copy & paste.
Then the new Recovery will be ready in less than 5 minutes.

reagentc /disable

diskpart
sel disk # (replace # by the right disk number. see diskmanagement, mostly 0 or1)
sel par 4
delete partition override
sel par 3
extend
shrink minimum=1025
create partition primary
format quick fs=ntfs label="Recovery"
set id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
gpt attributes=0x8000000000000001
exit

reagentc /enable

Thank you. I also saw this solution linked in the Rufus GitHub page, what do you think of this? Feature Request: Option to increase default size of generated windows recovery partition. (if possible) . Issue #2446 . pbatard/rufus . GitHub

Code:

reagentc /disable
dir /a /s c:\winre.wim
reagentc /setreimage /path C:\$WinREAgent\Backup
reagentc /enable

That's definitely not a solution! Why do you try to find alternatively steps that don't work?

Feature Request: Option to increase default size of generated windows recovery partition. (if possible) . Issue #2446 . pbatard/rufus . GitHub

I was looking into to seeing if Rufus had a way to implement the "fix" the recovery partition, and when I researched it I found that discussion.

For what it's worth, I tested both solutions (yours and the one I posted above in the Rufus GitHub page) in a Hyper-V VM and both at least worked to the degree that I was able to get the failing Windows Update installed.

It was more of a for science and to see what was being suggested would even work, but I personally don't understand what it seems to be doing differently or why they believe it is a solution - I'm simply a learner inquiring :)

It is easy to update the WinRE.wim in the ISO.
Just 3 Dism-Commands and the ISO is up to date.
Rufus doesn't help to create a partition-size that is safe for all future SafeOS updates.