KB5034441 Security Update for Windows 10 (21H2 and 22H2) - Jan. 9 Win Update

dalchina said:

@ferrarabrainpan - the News section article very clearly explains that
a. There is a coding error, so you DON'T get the appropriate error message

b. Therefore you DO get this characteristic error number.

Please reread it if unsure. Thanks.
KB5034441 Security Update for Windows 10 (21H2 and 22H2) - Jan. 9

Thank you but upon reading the article and the instructions I see this is way too advanced for me to do on my own, especially since I looked at other replies in this thread where it was not fixed by all the recovery partition changes.

Can I trust that this issue will be fixed in the next batch of Windows updates?

@kufr
There is no reason to delete partition 1.
Partition 1 is a Recovery Partition because it has a certain ID=de94bba4-06d1-4d40-a16a-bfd50179d6ac.
That's all. If you assign a new Primary-ID it's a partition like all other partitions. A WinRE.wim doesn't make a partition to a Recovery Partition!
You probably have the old (1909) partition structure. Then there is also a hidden MSR-Partition with a size of 128 MB.
So be aware what you do.
Maybe s.o. can explain, why it is better to have unallocated space at the beginning of a disk than to have a partition.
In your case the cmd (admin) command
diskpart
sel disk 4
list par
exit
gives you the info you need.

dalchina said:

All I did was use Minitool Partition Wizard (free) in the usual way to make the Recovery partition larger.

Failed updates normally recur on the next update check, so consider hiding this one (tutorial available) if you don't want to use a partition manager. (Videos on Youtube and built in to program).

Or you could ask a friend..

I know the fail will reappear on the next update check but I am hoping when Windows issues new updates superceding the latest ones in a week or two, a newer Security update will replace the one that keeps failing. That is what happened in the past. My PC is running normally now and I am reluctant to spend hours doing fixes that I don't understand which may or may not work. If there is a way to hide update then I will try that for now. Thanks.

EDIT: I have hidden that particular update so it no longer appears when I run Windows Update. Since my PC is working fine, I am going to try to forget about this and carry on with my life. The next time Update shows a bunch of new updates in a week or two I will try 'unhiding' or showing the pesky update to see if it installs or just disappears from the list of available updates.

I need to buy a new PC and get Windows 11 eventually but for now things are working. Thanks to those of you who have offered help and guidance.

well i gotta chime in and say doing same thing i email my brother about this and either he didn't see it on his computer/laptop that also has windows 10 he claims no issues

now lets go back in time few years ago i had apc backup battery and i turn off monitor not computer went down to a wedding thing was a storm when came back home monitor wouldn't come up basically harddrive died

still not sure if it was due to apc battery backup or not brother gave me new harddrive got a backup at his house

i did mention to him does my computer even have a recovery partition? he has no clue and don't want to attempt to do that because i read that some folks try to do this still issues.

basically in a nutshell i'm sitting duck i hope microsoft will fixed this in a few weeks or pull update meh

dalchina said:

- it will also fail if the Recovery partition is not immediately after the Windows partition
(or so I've read...).

I don´t think so. I got the update in a computer in which WinRE is the first partition.

It's okay, I followed the Microsoft tutorial, my recovery partition is 768MB in total.
The update did not fail.

edit: In my language there was an error in the Microsoft tutorial, here
If your disk is GPT, run create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac followed by the command gpt attributes =0x8000000000000001 gpt attributes =0x8000000000000001

2 times gpt attributes =0x8000000000000001 even though it is only once.

My recovery "partition" is not actually a partition, it's a folder in an older XP install primary partition.
I can only assume if it's size was increased, it was done so without issues. Currently 539 MB

Is this update really necessary? I always delete the Recovery Partition and add the space to C: since I can do everything with install media that Recovery can do.