How to install KB5034441: Windows Recovery Environment update for Windows 10, version 21H2 and 22H2: January 9, 2024

Anonymous

I tried to manually resize the partition by 250 MB per the instructions here: https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf#articleFooterSupportBridge=communityBridge

I had to exit Disk Part because I can not shrink the OS partition first:

C:\WINDOWS\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

Windows RE status:         Enabled  
Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE  
Boot Configuration Data (BCD) identifier: 610c3ed8-af74-11ee-92f0-acd56448675c  
Recovery image location:  
Recovery image index:      0  
Custom image location:  
Custom image index:        0

REAGENTC.EXE: Operation Successful.

C:\WINDOWS\system32>reagentc /disable
REAGENTC.EXE: Operation Successful.

C:\WINDOWS\system32>diskpart

Microsoft DiskPart version 10.0.19041.3636

DISKPART> list disk

Disk ### Status Size Free Dyn Gpt

Disk 0 Online 119 GB 11 MB *

DISKPART> sel disk 0

Disk 0 is now the selected disk.

DISKPART> list part

Partition ### Type Size Offset

Partition 1 System 750 MB 1024 KB
Partition 2 Reserved 128 MB 751 MB
Partition 3 Primary 117 GB 879 MB
Partition 4 Recovery 1022 MB 118 GB

DISKPART> sel part 1

Partition 1 is now the selected partition.

DISKPART> shrink desired=250 minimum=250

You may not shrink OEM, ESP, or recovery partitions, or, offline volumes.
The volume you have selected may not be shrunk.
Please select another volume and try again.

DISKPART> list part

* Partition 1 System 750 MB 1024 KB
Partition 2 Reserved 128 MB 751 MB
Partition 3 Primary 117 GB 879 MB
Partition 4 Recovery 1022 MB 118 GB

DISKPART> exit

Leaving DiskPart...

C:\WINDOWS\system32>reagentc /enable
REAGENTC.EXE: Operation Successful.

C:\WINDOWS\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

Windows RE status:         Enabled  
Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE  
Boot Configuration Data (BCD) identifier: 610c3eda-af74-11ee-92f0-acd56448675c  
Recovery image location:  
Recovery image index:      0  
Custom image location:  
Custom image index:        0

REAGENTC.EXE: Operation Successful.

C:\WINDOWS\system32>

Is there another way to install this update?

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

65 answers

Anonymous

2024-03-10T12:23:33+00:00

Installs the latest build of Windows 10.
Was this answer helpful?

0 comments No comments
Anonymous

2024-03-10T13:19:09+00:00

Does it fix the recovery partition issue? My computer has one, but reagentc does not recognize it.
Was this answer helpful?

0 comments No comments
Anonymous

2024-03-10T13:34:45+00:00

Yes, it repairs the recovery environment and fixes KB5034441 not installing.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2024-03-10T18:43:46+00:00

Thank you, I will try it to ight
Was this answer helpful?

0 comments No comments
Anonymous

2024-04-01T04:16:51+00:00

Finally, I took a different approach.

I realized that the 500 GB disk-drive in the computer was manufactured in 2017, making it over 6 years old, and thus was greatly out-of-warranty, and that the "C:" partition was nowhere near full.

So, I purchased a 500 GB SSD (SATA), and used disk-cloning software to copy all the partitions. The software allowed me to slightly shrink the "C:" partition, by less than 1 GByte, during the process of copying the partition. There was no need to "shrink" the "C:" partition on the 2017-vintage disk-drive, and thus no danger that a "shrink" might have gone terribly wrong on this "production" volume.

The "recovery" partition physically followed the "C:" partition.

Although the Windows "Disk Manager" incorrectly reported the partition as "0%-used", the software I used correctly reported that the files occupied about 400 MBytes.

While copying the "Recovery" partition, the software allowed it to grow in size to consume that new disk-space.

When I booted from the SSD, everything was fine. The new "recovery" partition uses less than 2 GB (out of the 500 GB).

One note: there was one cluster of sectors on the 2017-vintage disk-drive that could not be read by the cloning software. The software identified the file that "owned" that cluster, and the software allowed me to "continue" with the cloning. Obviously, Windows never was using that inaccessible file. So, its "loss" is not a problem for me.

Due to the new SSD disk-drive, Windows works much faster. This is a bonus, and I also have the 2017-vintage drive labelled as "full backup in March 2024", should I ever need it.

Done. :-)
Was this answer helpful?

0 comments No comments