New
#330
Here's the shot @Kari:
Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile
-
-
New #331
There's another one apparently not resolved: too many partitions on disk - Windows 10 Forums
-
New #332
You saw it on the Last Post Wins thread? Last One To Post Wins [92] - Page 80 - Windows 10 Forums
Mine never remakes another recovery partition, so can't help you there. Mine are MBR. Would that be a GPT flaw?
-
New #333
It seems that sometimes the insider team listen the insiders, when it was announced that there was an issue with the app flighting capabilities and that Microsoft was correcting it, Brandon Leblanc stated that those at Skip Ahead would not be affected by this "correction", however, several insiders complained on Twitter because Story Remix had disappeared from the Photos app despite being on Skip Ahead, well, last night, with another update, Story Remix returned to the app.
-
New #334
-
-
New #336
Not here!It seems that sometimes the insider team listen the insiders, when it was announced that there was an issue with the app flighting capabilities and that Microsoft was correcting it, Brandon Leblanc stated that those at Skip Ahead would not be affected by this "correction", however, several insiders complained on Twitter because Story Remix had disappeared from the Photos app despite being on Skip Ahead, well, last night, with another update, Story Remix returned to the app.
-
New #337
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, 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
-
New #338
To clean that crap up, see this old post of mine. Tried and tested: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
Can somebody help me on how to reconfigure boot loader in Windows 10? - Page 3 - Windows 10 Forums
Read post #26 too.
-
Quote
Related Discussions
