This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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)
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.
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.
Not possible. It's not Reserved, it's System. Essential.
Try updating without resizing.
Disable Windows RE and delete the recovery partition as usual.
Then enable Windows RE, run Windows Update and install KB5034441 which will work.
Disable Windows RE again.
Create the new recovery partition as usual.
Enable Windows RE again in hopes the updated Windows RE will accept the new recovery partition.
The additional space required is all about the update process which can take place on drive C.
Thanks for the quick response, Volume Z! Interesting. Here's what I see in DISKPART when I run LIST PART, select the partition that sits between my big partition with the OS and recovery partition, and then get details on that in-between partition:
Partition 2 is the big partition where the OS lives. Partition 4 is the Recovery partition. In between is Partition 3, which is listed as a "healthy" system partition. It's only 100 Mb in size. No indication that it is a Reserved partition.
How can I determine whether this partition is safe to delete?
If someone has ideas on why the resizing fails, and what I can do about it, that will be much appreciated!
This could happen with a Microsoft Reserved Partition in between, which could be deleted immediately.
Thanks, Nelson. I appreciate the help. Unfortunately the link you posted is the same one we have all been referring to for over two months now, and the instructions it links to, https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf, on how to manually resize the WinRE partition, are the same ones I and others have been using all this time. As my post of March 7 describes, those instructions have worked on most of my Win10 machines. I now have successfully re-sized the WinRE partition on three Win10 machines, so I am quite comfortable with the process.
However, the resizing process keeps failing on a fourth Win10 PC (which otherwise has all updates installed), I have run the instructions for manually resizing twice. As a result, in DISKPART when I run LIST DISK it now shows that my SSD disk has 500 Mb free -- this is because the procedure frees up 250 Mb from the system partition, and I have run that procedure twice. However, when I delete and then recreate the WinRE partition, during the re-creation the free space is not being utilized, and the newly created WinRE partition is exactly the same size, 510 Mb, as the old WinRE partition I deleted. Today I tried to re-size the WinRE partition using these instructions and it still fails. The free space again is unused, and the WinRE partition again is the same size.
If someone has ideas on why the resizing fails, and what I can do about it, that will be much appreciated!
Thank you for this, this got me working again. Didn't think I'd have to recreate the recovery partition entirely, but Microsoft always loves breaking their own systems in new, creative ways lmao.
