Reply to thread

Message

<blockquote data-quote="Paul B." data-source="post: 409205" data-attributes="member: 32175">I haven&#039;t tried this, and I don&#039;t have a Win8 box in front of me, so proceed at your own risk. But my guess is the way to clean this up would be to go into BCDEdit in an elevated command window, and then find the GUID for the partition its recovery function points to. Then use DiskPart to find the recovery partition that has that ID. The others &quot;should&quot; be deletable without consequence (But from experience I would recommend a full disk image backup!).Presumably the working partition will be the last one in the series, having been added last. If so, that would leave a bit of space before it. That&#039;s inconsequential, probably, but you could move the true recovery partition forward, and then use Windows repair to get the whole thing working again - I think...MS doosn&#039;t want to mess with other partitions, but this is rather sloppy. Doesn&#039;t engender a whole lot of confidence.</blockquote>

[QUOTE="Paul B., post: 409205, member: 32175"] [U]I haven't tried this[/U], and I don't have a Win8 box in front of me, [U]so proceed at your own risk[/U]. But my guess is the way to clean this up would be to go into BCDEdit in an elevated command window, and then find the GUID for the partition its recovery function points to. Then use DiskPart to find the recovery partition that has that ID. The others "should" be deletable without consequence (But from experience I would recommend a full disk image backup!). Presumably the working partition will be the last one in the series, having been added last. If so, that would leave a bit of space before it. That's inconsequential, probably, but you could move the true recovery partition forward, and then use Windows repair to get the whole thing working again - I think... MS doosn't want to mess with other partitions, but this is rather sloppy. Doesn't engender a whole lot of confidence. [/QUOTE]

Verification