Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile Insider

There's another one apparently not resolved: too many partitions on disk - Windows 10 Forums

This is like this since CU clean install.

Edwin said:

Here's the shot @Kari:

CountMike said:

There's another one apparently not resolved:

HippsieGypsie said:

You saw it on the Last Post Wins thread?

Thanks geeks, exactly what I was looking for.

HippsieGypsie said:

Would that be a GPT flaw?

Yes. I am examining this as at the moment the way recovery partitions are handled and created is completely broken.

If a user selects default partitioning (clean install, let Windows setup partition the disk), the 450 MB recovery partition is put first on primary disk, followed by 100 MB EFI system partition and 16 MB Microsoft reserved (MSR, not shown in Disk Management) partition, Windows partition C: being volume 4 after those three system partitions.

When subsequent upgrades require more space on recovery partition, an additional recovery partition is created after C: partition. As recovery partition can expand backwards, any additional upgrades requiring more space for recovery partition then take the space needed by shrinking C: and expanding backwards. This makes the max number of recovery partitions to two.

If partitioning is done manually placing the recovery partition not first as by default but directly after C: instead, there should never be more than that one recovery partition. An example from a virtual machine installation of mine, after clean install manually partitioning with a Diskpart script, recovery partition (yellow highlight) is after C: drive:



The same VM after a build upgrade, as 58 MB more space was required by the recovery partition, it shrunk C: drive and took what it needed:



That is, that's how it should work. However, at the moment (since I think last15K builds or so), upgrade simply creates new recovery partitions like shown in that Wynona's screenshot.

I want to find out why, have been studying this since I noticed this erratic behaviour.

Kari

Kari said:

@Wynona, your assistance required :)

Some days ago you posted a screenshot of your Disk Management (build 16251 thread, if I remember it correctly), showing like half a dozen recovery partitions after C: partition, created by successive upgrades. As this, how feature upgrade handles recovery partitions is something I am trying to figure out and work around, I would like to see that screenshot again as reference but I seem to be unable to find it.

Could you please repost it, if you still have the screenshot image, or point me to correct post?

Kari

Kari said:

Sorry to bump such a recent post but geeks, do any of you remember seeing the screenshot I am talking about and able to link me to post in question:




I am also interested in any Disk Management screenshots from UEFI / GPT systems showing three or more recovery partitions.

Kari

Edwin said:

Here's the shot @Kari:

CountMike said:

There's another one apparently not resolved: too many partitions on disk - Windows 10 Forums

Kari said:

Thanks geeks, exactly what I was looking for.




Yes. I am examining this as at the moment the way recovery partitions are handled and created is completely broken.

If a user selects default partitioning (clean install, let Windows setup partition the disk), the 450 MB recovery partition is put first on primary disk, followed by 100 MB EFI system partition and 16 MB Microsoft reserved (MSR) partition, Windows partition C: being volume 4 after those three system partitions.

When subsequent upgrades require more space on recovery partition, an additional recovery partition is created after C: partition. As recovery partition can expand backwards, any additional upgrades requiring more space for recovery partition then take the space needed by shrinking C: and expanding backwards. This makes the max number of recovery partitions to two.

If partitioning is done manually placing the recovery partition not first as by default but directly after C: instead, there should never be more than that one recovery partition. An example from a virtual machine installation of mine, after clean install manually partitioning with a Diskpart script, recovery partition (yellow highlight) is after C: drive:



The same VM after a build upgrade, as more space was required, the recovery partition shrunk C: drive and took what it needed:



That is, that's how it should work. However, at the moment (since I think last15K builds or so), upgrade simply creates new recovery partitions like shown in that Wynona's screenshot.

I want to find out why, have been studying this since I noticed this erratic behaviour.

Kari

To clean that crap up, see this old post of mine. Tried and tested:
Can somebody help me on how to reconfigure boot loader in Windows 10? - Page 3 - Windows 10 Forums
Read post #26 too.

Cliff S said:

To clean that crap up, see this old post of mine. Tried and tested:
Can somebody help me on how to reconfigure boot loader in Windows 10? - Page 3 - Windows 10 Forums
Read post #26 too.

Thanks Cliff.

Cleaning is one thing, to understand why the mess was created another :)