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

  1.    05 Aug 2017 #330

    Kari said: View Post
    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:

    Click image for larger version. 

Name:	000398.png 
Views:	16 
Size:	329.7 KB 
ID:	147278
      My ComputerSystem Spec

  2.    05 Aug 2017 #331


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


  3. Posts : 38,043
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       05 Aug 2017 #332

    Kari said: View Post
    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 ComputersSystem Spec


  4. Posts : 772
    WINDOWS 10 Pro x64 builds 17134.191, 17733.1000, 18204.1001.
       05 Aug 2017 #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 ComputerSystem Spec

  5.    05 Aug 2017 #334

    HippsieGypsie said: View Post
    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 ComputerSystem Spec

  6.    05 Aug 2017 #335

    This is like this since CU clean install.
    Click image for larger version. 

Name:	image.png 
Views:	3 
Size:	33.8 KB 
ID:	147281
      My ComputersSystem Spec

  7.    05 Aug 2017 #336

    LEOPEVA64 said: View Post
    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 ComputerSystem Spec


  8. Posts : 14,380
    Windows 10 Pro
       05 Aug 2017 #337

    Edwin said: View Post
    Here's the shot @Kari:
    CountMike said: View Post
    There's another one apparently not resolved:
    HippsieGypsie said: View Post
    You saw it on the Last Post Wins thread?
    Thanks geeks, exactly what I was looking for.


    HippsieGypsie said: View Post
    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:

    Click image for larger version. 

Name:	image.png 
Views:	61 
Size:	33.4 KB 
ID:	147283

    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:

    Click image for larger version. 

Name:	image.png 
Views:	61 
Size:	25.9 KB 
ID:	147284

    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 ComputerSystem Spec


  9. Posts : 21,206
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu
       05 Aug 2017 #338

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

    Click image for larger version. 

Name:	000398.png 
Views:	16 
Size:	329.7 KB 
ID:	147278
    CountMike said: View Post

    There's another one apparently not resolved: too many partitions on disk - Windows 10 Forums
    Kari said: View Post
    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:

    Click image for larger version. 

Name:	image.png 
Views:	61 
Size:	33.4 KB 
ID:	147283

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

    Click image for larger version. 

Name:	image.png 
Views:	61 
Size:	25.9 KB 
ID:	147284

    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 ComputersSystem Spec


  10. Posts : 14,380
    Windows 10 Pro
       05 Aug 2017 #339

    Cliff S said: View Post
    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 ComputerSystem Spec


 

Related Threads
883370827718172672 Source: Announcing Windows 10 Insider Preview Build 16237 for PC - Windows Experience Blog How to Start or Stop Receiving Insider Builds in Windows 10
786612992179712000 Source: Announcing Windows 10 Insider Preview Build 14946 for PC and Mobile | Windows Experience Blog PC: How to Start or Stop Receiving Insider Builds in Windows 10
784439136002375681 784446397466681344 Source: Announcing Windows 10 Insider Preview Build 14942 for PC | Windows Experience Blog How to Start or Stop Receiving Insider Builds in Windows 10
UPDATE: July 15th 2016 754001939445219329 752986516746493952 Source: Announcing Windows 10 Insider Preview Build 14388 for PC and Mobile | Windows Experience Blog
UPDATE: 742889757512867840 Source: Announcing Windows 10 Insider Preview Build 14366 Mobile Build 14364 | Windows Experience Blog
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:23.
Find Us