>>> REAGENTC.EXE /setreimage /path r:\Recovery\WindowsRE ...
I assume that you have mounted the Recovery Partition as your "R:" drive-letter. Correct?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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:
Microsoft Windows [Version 10.0.19045.3930]
(c) Microsoft Corporation. All rights reserved.
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
Copyright (C) Microsoft Corporation.
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.
>>> REAGENTC.EXE /setreimage /path r:\Recovery\WindowsRE ...
I assume that you have mounted the Recovery Partition as your "R:" drive-letter. Correct?
No I have not mounted the recovery partition. The instructions from MS said nothing about mounting it.
I have now download3d the win 10 ISO, mounted it and extracted the required file, then converted it to a .wim file. I chave not been able to MOUNT the recovery partition, to copy the new .wim file to it.
Of course, all Microsoft documentation is 100% perfect, and 100% applicable in all situations. NOT!
It makes no sense for the command-line to include "R:" when Windows has not assigned any partition/device to that drive-letter.
Have you tried:
?
I have not tried that yet.
I have a third computer, that fails on the same update, for lack of sufficient space in the recovery partition. I will not perform this procedure until and unless I get a solution that works.
One person in this chain says MS will (eventually?) Provide a new update that actually works with MBR format.
I would rather update my working, two yr old Win 10 computer, than buy a new one with Win 11 that is going out of date already.
I will check your reccomendation and see what it does.
>> I will not perform this procedure until and unless I get a solution that works.
That choice closes and locks the door to the security-safe that contains the solution. Sigh.
Have you considered ignoring the update, and accepting the risk that not applying this security-update will, in practice, leave your computer only slightly more susceptible that it currently is? Expressed differently, if your computer is compromised by some other means, it will be compromised, plus/minus this update.
If you never need to use the Windows Recovery environment, and your computer is protected from other attack-vectors, then there is no need to apply this update.
Short answer: try the suggested update, and report back.
>>> Win 11 is going out of date already.
Nonsense. Microsoft has a ten-year Product Lifecycle for all its products.
While October 2025 is the end of support for Windows 10, the end-date for Windows 11 is far in the future -- ten years after Oct 4, 2021.
Do you replace your automobile after its warranty ends, or do you drive it until the time when the repair/maintenance costs exceed the value of extending its life?