Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile  


  1. Posts : 17,839
    Windows 10
       #330

    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
    Here's the shot @Kari:

    Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile-000398.png
      My Computer


  2. Posts : 19,460
    W11+W11 Developer Insider + Linux
       #331


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


  3. Posts : 5,833
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       #332

    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
    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?
      My Computers


  4. Posts : 2,204
    WINDOWS 10 Pro x64 build 19042.685
       #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.
      My Computer


  5. Posts : 3,323
    Windows 10 Pro x64
       #334

    HippsieGypsie said:
    Mine never remakes another recovery partition, so can't help you there. Mine are MBR. Would that be a GPT flaw?
    Don't recall Windows 10 ever creating an extra recovery partition on any of my PCs and they are all GPT. I leave the one that's created on my Insider machines, but would immediately delete any extras to regain the space.
      My Computer


  6. Posts : 19,460
    W11+W11 Developer Insider + Linux
       #335

    This is like this since CU clean install.
    Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile-image.png
      My Computers


  7. Posts : 17,839
    Windows 10
       #336

    LEOPEVA64 said:
    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.
    Not here!
      My Computer


  8. Posts : 17,660
    Windows 10 Pro
       #337

    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:

    Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile-image.png

    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:

    Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile-image.png

    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
      My Computer


  9. Posts : 26,824
    Win11 Pro, Win10 Pro N, Win10 Home, Windows 8.1 Pro, Ubuntu
       #338

    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:

    Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile-000398.png
    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:

    Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile-image.png

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

    Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile-image.png

    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.
      My Computers


  10. Posts : 17,660
    Windows 10 Pro
       #339

    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 :)
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 18:09.
Find Us




Windows 10 Forums