Skip to main content
Better use of code blocks
Source Link
Nick Bolton
  • 3.4k
  • 10
  • 39
  • 53

I know VainMain's answer from above is probably more careful and thorough, but I've been able to successfully move the partion by simply doing:

In Windows 10: "reagentc /disable"
In Linux boot CD: adjust neighboring partition as needed/move recovery partition
In Windows 10: "reagentc /enable"
  1. In Windows 10: reagentc /disable
  2. In Linux boot CD: Adjust neighboring partition as needed/move recovery partition.
  3. In Windows 10 reagentc /enable

Recovery environment was automatically rediscovered and booted WinRE just fine with all recovery options (Reset/System Image restore/etc). I had only 1 C: partition, no special partitioning/dual booting/multiple recovery partition/crazy BCDEDIT settings beforehand, which helped. Tested inside a VM beforehard to make sure. Had no problems after executing live.

If I remember correctly, skipping the first step (disabling via reangetc) would cause the recovery environment to end up misconfigured, not properly re-bootable, and not easily fixed.

I know VainMain's answer from above is probably more careful and thorough, but I've been able to successfully move the partion by simply doing:

In Windows 10: "reagentc /disable"
In Linux boot CD: adjust neighboring partition as needed/move recovery partition
In Windows 10: "reagentc /enable"

Recovery environment was automatically rediscovered and booted WinRE just fine with all recovery options (Reset/System Image restore/etc). I had only 1 C: partition, no special partitioning/dual booting/multiple recovery partition/crazy BCDEDIT settings beforehand, which helped. Tested inside a VM beforehard to make sure. Had no problems after executing live.

If I remember correctly, skipping the first step (disabling via reangetc) would cause the recovery environment to end up misconfigured, not properly re-bootable, and not easily fixed.

I know VainMain's answer from above is probably more careful and thorough, but I've been able to successfully move the partion by simply doing:

  1. In Windows 10: reagentc /disable
  2. In Linux boot CD: Adjust neighboring partition as needed/move recovery partition.
  3. In Windows 10 reagentc /enable

Recovery environment was automatically rediscovered and booted WinRE just fine with all recovery options (Reset/System Image restore/etc). I had only 1 C: partition, no special partitioning/dual booting/multiple recovery partition/crazy BCDEDIT settings beforehand, which helped. Tested inside a VM beforehard to make sure. Had no problems after executing live.

If I remember correctly, skipping the first step (disabling via reangetc) would cause the recovery environment to end up misconfigured, not properly re-bootable, and not easily fixed.

I know VainMain's answerVainMain's answer from above is probably more careful and thorough, but I've been able to successfully move the partion by simply doing:

In Windows 10: "reagentc /disable"
In Linux boot CD: adjust neighboring partition as needed/move recovery partition
In Windows 10: "reagentc /enable"

Recovery environment was automatically rediscovered and booted WinRE just fine with all recovery options (Reset/System Image restore/etc). I had only 1 C: partition, no special partitioning/dual booting/multiple recovery partition/crazy BCDEDIT settings beforehand, which helped. Tested inside a VM beforehard to make sure. Had no problems after executing live.

If I remember correctly, skipping the first step (disabling via reangetc) would cause the recovery environment to end up misconfigured, not properly re-bootable, and not easily fixed.

I know VainMain's answer is probably more careful and thorough, but I've been able to successfully move the partion by simply doing:

In Windows 10: "reagentc /disable"
In Linux boot CD: adjust neighboring partition as needed/move recovery partition
In Windows 10: "reagentc /enable"

Recovery environment was automatically rediscovered and booted WinRE just fine with all recovery options (Reset/System Image restore/etc). I had only 1 C: partition, no special partitioning/dual booting/multiple recovery partition/crazy BCDEDIT settings beforehand, which helped. Tested inside a VM beforehard to make sure. Had no problems after executing live.

If I remember correctly, skipping the first step (disabling via reangetc) would cause the recovery environment to end up misconfigured, not properly re-bootable, and not easily fixed.

I know VainMain's answer from above is probably more careful and thorough, but I've been able to successfully move the partion by simply doing:

In Windows 10: "reagentc /disable"
In Linux boot CD: adjust neighboring partition as needed/move recovery partition
In Windows 10: "reagentc /enable"

Recovery environment was automatically rediscovered and booted WinRE just fine with all recovery options (Reset/System Image restore/etc). I had only 1 C: partition, no special partitioning/dual booting/multiple recovery partition/crazy BCDEDIT settings beforehand, which helped. Tested inside a VM beforehard to make sure. Had no problems after executing live.

If I remember correctly, skipping the first step (disabling via reangetc) would cause the recovery environment to end up misconfigured, not properly re-bootable, and not easily fixed.

Source Link
crimshauw
  • 521
  • 4
  • 2

I know VainMain's answer is probably more careful and thorough, but I've been able to successfully move the partion by simply doing:

In Windows 10: "reagentc /disable"
In Linux boot CD: adjust neighboring partition as needed/move recovery partition
In Windows 10: "reagentc /enable"

Recovery environment was automatically rediscovered and booted WinRE just fine with all recovery options (Reset/System Image restore/etc). I had only 1 C: partition, no special partitioning/dual booting/multiple recovery partition/crazy BCDEDIT settings beforehand, which helped. Tested inside a VM beforehard to make sure. Had no problems after executing live.

If I remember correctly, skipping the first step (disabling via reangetc) would cause the recovery environment to end up misconfigured, not properly re-bootable, and not easily fixed.