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

I had the recovery partition all up and working a day or two ago. I tried to do an inplace install and keep my apps and setting using an iso from Microsoft which exits out with a fail to install windows 10 when it tried to restart. I'm trying to fix some srm dll hash mismatches and some directory overlap dual ownership issues so that my sfc /scannow will pass. I decided to check the recovery partition and now see it is "raw" and the reagentc /info shows disabled. My sfc /scannow works on windows 10 home but not win 10 pro.

question: Is it known what causes the recovery partition to become raw? I'll have to go back and redo the setting up of the recovery partition again....

Hi,

I started a discussion here.

windows update of KB5034441 return error 80070643

Basically in the end I had moved the "winRE" to the C: drive , And I had lost the recovery partition

Today as it was suggested to me i have done:

I restored the partition from a backup.

I enlarged it, mapped a drive letter to the partition E:, and issued the command "reagentc /setreimage /path e:\recovery\windowsRE".

everything seems OK.

However, I saw that the KB5034441 update was installed on 1/11/2024. And I didn't realize the update had been installed.

I'm thinking that he installed the update on the previous winre location which was on disk C:

How do I know if I missed the update?

swegmike said:

======= Redo the Recovery partition =====
I reformatted and assigned the setid and gptid values on partition 4 which came after partition 3 (OS). To comfirm one can run "detail" after selecting partition 4 in diskpart.

== updating winre.wim ======
My winre.wim that I copied from the Recovery directory within the install.wim that came from the downloaded iso from microsoft didn't have the correct update date. It was May of 2023. Thus I knew that it didn't contain this KB # in the Jan 2024 update.

I didn't understand how to run the powerscript for an OS version greater than2004 per https://support.microsoft.com/en-us/...5-7fc406910c10 as to what to enter and how at the package location prompt.

Moreover, I didn't run reagentc /disable to move the winre.wim on the recovery partition to the location C drive recovery area since it was already disabled due to me reformatting the recovery partition. I had copied the reagent.xml and winre.wim from the extracted install.wim as noted above to the C:\windows\system32\recovery directory. I then ran reagentc /enable which moved them to the recovery partition.

Since I already had this KB # installed a few days ago I had to uninstall it. Microsoft stated it can't be uninstalled once installed to the image. I presume they mean the winre.wim (image). So I went to windows update and selected it from the installed list to be uninstalled - which it did. I then reran windows update, but it didn't redownload and reinstall the KB # and said I was up to date.

I took a guess and went to the registry location Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion and deleted the WinReRevision entry at the end of this list of key data and saved the changes. I then reran windows update and it then downloaded the KB # update and installed it. It then updated the winre.wim on the recovery partition and get-hotfix in powershell shows it as updated. I then checked the registry entry WinReVersion and it was put back in with the value 10.0.19041.3920

To confirm the version on my disk 0 partition 4 was the correct version and the date it was updated to is today, I ran this



Of course my reagentc /info shows I'm enabled too



===== To make a backup of the ReAgent.xml and winre.wim files =======


signed by einstein1970! Hmmm. I didn't know there were so many of us :)

- - - Updated - - -



See my post above. Since I also had installed the KB # update but needed a way for it to reupdate my winre.wim on the recovery partition.

To make a backup of the ReAgent.xml and winre.wim files :
execute reagentc /disable
the winre.win is moved from the recovery partition to c:\windows\system32\recovery\winre.wim; you can save c:\windows\system32\recovery\winre.wim to a location of your choice
execute reagentc / enable
the content of the WindowsRE folder of the recovery partition is recreated (winre.wim, boot.sdi and ReAgent.xml) and c:\windows\system32\recovery\winre.wim is delete since it has been moved.

dalchina said:

History: originally Windows installations placed the Recovery partition first (to the left). Then MS realised that was daft, as they had to enlarge them, so the started putting it to the right. Presumably yours is quite an old installation.

It'll be the one on the right (larger).

Non-destructive methods to check which is active:
Attachment 403267

and if you're clever, use e.g. Minitool Partition Wizard, rt click on partition, click explore, and you can see the content and date of content.. the most recent is the current one...

Pentagon said:

@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.

Hello and sorry for the late I was travelling due to work so could not reply earlier I did install the Minitool Partition Wizard and explored the dirfferent partitions on my Drive c to see the content of them all. Here I am sharing those screenshots that I took for you. Please have a look. I have about 5 partitions on my drive see which you can clearly see in screenshot 4.

@Pentagon @dalchina @ghot
I have pasted the partitons with their date of the content for you to have a look too in all screenshots.

Screenshot 1


Screenshot 2


Screenshot 3


Screenshot 4


Now please have a look and tell me step by step what I need to do fix this. Microsoft has really screwed so many users like me who are not experts in the technical issues like this. Please bear in mind that I am a bit of a noob in such things please. I will wait for your kind reply.

I really am not too confortable to use the MinoTool Partition Wizard to manually change or play with my partitions so that I don't mess anything at all. But I also don't understand what these multiple partitions are specially screenshot 2 & 3 on my Drive C are for ?

@kufr
All these screenshots are not really helpful.
Consider just screenshot of your post #54.
Use cmd (admin) and type (copy&paste)
diskpart
sel disk 4
sel par 1
set id="ebd0a0a2-b9e5-4433-87c0-68b6b72699c7"
gpt attributes=0x0000000000000000
exit

Now the 1st partition is a standard partition and forget this one.
In "Diskmanagement" right click on (C:) and select shrink volume. In the highlighted field type 500
and OK. That's all you have to know. For the rest you find meanwhile hundreds of advices.
But do yourself a favour: Don't play around with partition 1 and don't delete it!
This tutorial for the rest is not bad.
Create recovery partition in Windows 10/11 UEFI - YouTube

Guys,

Some help here, please.

I did all steps for creating recovery partition, it is harddisk2 and partition 2 for me. It is 515Mb big, I assigned letter to it temporarily, just to see if it will be filled up with some files. It is MBR, so I did set id=27.

When I did reagentc /enable and reagentc /info it shows me

\\?\GLOBALROOT\device\harddisk2\partition1\Recovery\WindowsRE

where my Windows is installed and not showing partition 2, created as recovery and it stays empty. I did all things to set path to partition 2, everything was successful, but reagentc /enable put it in wrong partition. I want this scenario

\\?\GLOBALROOT\device\harddisk2\partition2\Recovery\WindowsRE

Checking log file it says that does not have enough of space, but it did, when I calculate sizes of files. This is not related to Windows update yet which requires more space, it is related just to creating recovery partition where I want it to.

What can I do here to make reagent /enable put recovery files to my dedicated partition

\\?\GLOBALROOT\device\harddisk2\partition2\Recovery\WindowsRE

Thank you.