0

The Server 2022 Recovery Partition has been causing all sorts of pain lately.

  1. By default it places this partition at the end of the disk which makes it impossible to extend the primary partition without doing some sort of partition rearrangement.

  2. This months update fails on all of our 2022 servers since that partition is too small for some updates it's trying to apply. This partition is before the primary partition which now makes it non-trivial to expand.

So I was going to see if I could just created a small dependent disk and just have the Recovery Partition be housed all on it's own.

I'm working in a vSphere environment.

There was a nice step by step by @VainMan here --> How to move the recovery partition on Windows 10? Everything appears to go well and the copied Recovery Partition is placed on the new volume. Even when I do a reagentc /info, it shows that it is enabled. Disk Management shows it as a Healthy (Recovery Partition)

However, when I try to test this via reagentc /boottore then reboot, I get the following:

Boot Manager Error

Prior to doing the steps in the above link, I did verify that the Recovery Partition did work via reagentc /boottore. Soon as I copy it over to the new volume, it no longer works.

I also verified that the identifiers were correct via bcdedit.

Is what I'm doing even possible or am I missing something?

Improve this question
11
  • 1
    "I could just create a small dependent disk and just have the Recovery Partition be housed all on it's own." - You could but you would have the same problem, Windows would be unable to extend or rebuild the WinRE partition, forcing you to rebuild it yourself. The WinRE partition most certainly should NOT exist before the system partition. It should exist after the Windows partition, which makes the recreation and expansion of the partition, trivial. This says as much.
    – Ramhound
    Commented Jan 11 at 22:41
  • 1
    I suggest using Microsoft's instructions to create the WinRE partition.
    – Ramhound
    Commented Jan 11 at 22:46
  • Or try the MS script to fix the update failure: bleepingcomputer.com/news/microsoft/… . Note their warning the script comes with no warranty.
    – DrMoishe Pippik
    Commented Jan 11 at 23:09
  • 1
    Here is the direct link. So the script applies the updated WinRE image but doesn’t fix the size issue with the partition itself.
    – Ramhound
    Commented Jan 12 at 2:38
  • Thanks all for responding! @Ramhound - Prior to server 2022, the WinRE Partition was always before the primary. In a VM environment, this worked just fine because now and then we need to extend the primary. Once 2022 come along, we no longer could do this. This was a problem. So we adjusted our 2022 image via GParted to match how all previous versions of Server, which allowed us to extend the Primary if the need arose. Partitions in this day of VM's seem antiquated and should just use separate VMDK's instead of Partitions. That way each one can be expanded via hypervisor as needed.
    – LuckyMe
    Commented Jan 12 at 16:13

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .