Appreciate your patience - there is a known issue about this here: https://support.microsoft.com/topic/kb5034441-windows-recovery-environment-update-for-windows-10-version-21h2-and-22h2-january-9-2024-62c04204-aaa5-4fee-a02a-2fdea17075a8
Unable to update (KB5034441) using below links
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf (I was following steps from this link. I saw that I have 520MB of Healthy Recovery Partition in which I failed to shrink and the error was "you may not shrink OEM, ESPY or recovery partitions, or, offline volumes. The volume you have selected may not be shrunk. Please select another volume and try again.".) (Also when I shrink from C: and then I do not see new partition which suppose to be seen).
So kindly help.
Windows for home | Windows 10 | Windows 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.
68 answers
Sort by: Newest
-
Anonymous
2024-03-16T23:49:33+00:00 -
Anonymous
2024-03-07T14:25:32+00:00 I have successfully fixed two different Win 10 Pro machines by following all the steps in KB5028997, which are the same steps that several people have re-posted to this thread. On a third Win 10 Pro system, the process fails despite multiple efforts. The WinRE partion on this system is 510 Mb. According to SHRINK QUERYMAX, my Primary partition has 46 Gb available for shrinking. Per the instructions I run the "shrink desired=250 minimum=250" command on the Primary partition and get a response that the partition successfully has been shrunk by 250 Mb. Then I complete the steps to delete and then re-create the WinRE partition. When all that is done, the partition is, again, 510 Mb! For some reason the additional 250 Mb created by shrinking the Primary partition is NOT being utilized when the WinRE partition is re-created. I do not get any error messages in the process. Any suggestions on what I can look out to identify and correct the problem?
-
Anonymous
2024-03-06T21:59:24+00:00 Virtual Disk Service error:
The specified shrink size is too big and will cause the volume to be
smaller than the minimum volume size.
There is no point for you in shrinking partition 4 anyway.
If you have deleted the Recovery Partition already, enable the recovery environment right now. Run
reagentc /enable
Run Windows Update. Installation of KB5034441 will succeed. You may make an attempt at restoring WinRE to a newly created Recovery Partition in the same spot later, but it's unlikely to work.
-
Anonymous
2024-03-06T21:57:12+00:00 Virtual Disk Service error:
The specified shrink size is too big and will cause the volume to be
smaller than the minimum volume size.
There is no point for you in shrinking partition 4 anyway.
If you have deleted the Recovery Partition already, enable the recovery environent right now. Run
reagentc /enable
Run Windows Update. Installation of KB 5034441 will succeed. You may make an attempt at restoring WinRE to a newly created Recovery Partition in the same spot later, but it's unlikely to work.
-
Anonymous
2024-03-06T21:57:01+00:00 Virtual Disk Service error:
The specified shrink size is too big and will cause the volume to be
smaller than the minimum volume size.
There is no point for you in shrinking partition 4 anyway.
If you have deleted the Recovery Partition already, enable the recovery environent right now. Run
reagentc /enable
Run Windows Update. Installation of KB 5034441 will succeed. You may make an attempt at restoring WinRE to a newly created Recovery Partition in the same spot later, but it's unlikely to work.