locked
When there are multiple recovery partitions how can you determine which one to delete RRS feed

  • Question

  • When there are multiple recovery partitions how can your determine which one to delete?

    Using administrative command prompt many commands were entered to display results.

    Before running the command bcdedit /enum all there were additional commands ran that are not displayed ( the volumes were assigned letters U and V.

    Microsoft Windows [Version 10.0.16299.309]
    (c) 2017 Microsoft Corporation. All rights reserved.
    C:\WINDOWS\system32>reagentc /info
    Windows Recovery Environment (Windows RE) and system reset configuration
    Information:
        Windows RE status:         Disabled
        Windows RE location:
        Boot Configuration Data (BCD) identifier: 3bc8de50-00c0-11e8-9dfb-b11179f22ce6
        Recovery image location:
        Recovery image index:      0
        Custom image location:
        Custom image index:        0
    REAGENTC.EXE: Operation Successful.

    C:\WINDOWS\system32>diskpart
    Microsoft DiskPart version 10.0.16299.15
    Copyright (C) Microsoft Corporation.
    On computer: DESKTOP-GEOTAKI
    DISKPART> list disk
      Disk ###  Status         Size     Free     Dyn  Gpt
      --------  -------------  -------  -------  ---  ---
      Disk 0    Online          238 GB  1024 KB        *
    DISKPART> list volume
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
      Volume 0     D                       DVD-ROM         0 B  No Media
      Volume 1     C                NTFS   Partition    237 GB  Healthy    Boot
      Volume 2                      RAW    Partition    450 MB  Healthy    Hidden
      Volume 3                      FAT32  Partition    100 MB  Healthy    System
      Volume 4                      RAW    Partition    818 MB  Healthy    Hidden
    DISKPART> select disk 0
    Disk 0 is now the selected disk.
    DISKPART> list partition
      Partition ###  Type              Size     Offset
      -------------  ----------------  -------  -------
      Partition 1    Recovery           450 MB  1024 KB
      Partition 2    System             100 MB   451 MB
      Partition 3    Reserved            16 MB   551 MB
      Partition 4    Primary            237 GB   567 MB
      Partition 5    Recovery           818 MB   237 GB
    DISKPART> select partition 1
    Partition 1 is now the selected partition.
    DISKPART> detail partition
    Partition 1
    Type    : de94bba4-06d1-4d40-a16a-bfd50179d6ac
    Hidden  : Yes
    Required: Yes
    Attrib  : 0X8000000000000001
    Offset in Bytes: 1048576
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
    * Volume 2                      RAW    Partition    450 MB  Healthy    Hidden
    DISKPART> select partition 5
    Partition 5 is now the selected partition.
    DISKPART> detail partition
    Partition 5
    Type    : de94bba4-06d1-4d40-a16a-bfd50179d6ac
    Hidden  : Yes
    Required: Yes
    Attrib  : 0X8000000000000001
    Offset in Bytes: 255201378304
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
    * Volume 4                      RAW    Partition    818 MB  Healthy    Hidden
    DISKPART> select partition 2
    Partition 2 is now the selected partition.
    DISKPART> detail partition
    Partition 2
    Type    : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
    Hidden  : Yes
    Required: No
    Attrib  : 0X8000000000000000
    Offset in Bytes: 472907776
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
    * Volume 3                      FAT32  Partition    100 MB  Healthy    System
    DISKPART> select partition 3
    Partition 3 is now the selected partition.
    DISKPART> detail partition
    Partition 3
    Type    : e3c9e316-0b5c-4db8-817d-f92df00215ae
    Hidden  : Yes
    Required: No
    Attrib  : 0X8000000000000000
    Offset in Bytes: 577765376
    There is no volume associated with this partition.
    DISKPART> select partition 4
    Partition 4 is now the selected partition.
    DISKPART> detail partition
    Partition 4
    Type    : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
    Hidden  : No
    Required: No
    Attrib  : 0000000000000000
    Offset in Bytes: 594542592
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
    * Volume 1     C                NTFS   Partition    237 GB  Healthy    Boot
    DISKPART> exit
    Leaving DiskPart...
    C:\WINDOWS\system32>bcdedit /enum all
    Firmware Boot Manager
    ---------------------
    identifier              {fwbootmgr}
    displayorder            {bootmgr}
    timeout                 0
    Windows Boot Manager
    --------------------
    identifier              {bootmgr}
    device                  partition=\Device\HarddiskVolume2
    path                    \EFI\Microsoft\Boot\bootmgfw.efi
    description             Windows Boot Manager
    locale                  en-US
    inherit                 {globalsettings}
    default                 {current}
    resumeobject            {3bc8de4e-00c0-11e8-9dfb-b11179f22ce6}
    displayorder            {current}
    toolsdisplayorder       {memdiag}
    timeout                 30
    Windows Boot Loader
    -------------------
    identifier              {current}
    device                  partition=C:
    path                    \WINDOWS\system32\winload.efi
    description             Windows 10
    locale                  en-US
    inherit                 {bootloadersettings}
    recoverysequence        {3bc8de50-00c0-11e8-9dfb-b11179f22ce6}
    displaymessageoverride  Recovery
    recoveryenabled         Yes
    isolatedcontext         Yes
    allowedinmemorysettings 0x15000075
    osdevice                partition=C:
    systemroot              \WINDOWS
    resumeobject            {3bc8de4e-00c0-11e8-9dfb-b11179f22ce6}
    nx                      OptIn
    bootmenupolicy          Standard
    Windows Boot Loader
    -------------------
    identifier              {3bc8de50-00c0-11e8-9dfb-b11179f22ce6}
    device                  ramdisk=[V:]\Recovery\WindowsRE\Winre.wim,{3bc8de51-00c0-11e8-9dfb-b11179f22ce6}
    path                    \windows\system32\winload.efi
    description             Windows Recovery Environment
    locale                  en-US
    inherit                 {bootloadersettings}
    displaymessage          Recovery
    osdevice                ramdisk=[V:]\Recovery\WindowsRE\Winre.wim,{3bc8de51-00c0-11e8-9dfb-b11179f22ce6}
    systemroot              \windows
    nx                      OptIn
    bootmenupolicy          Standard
    winpe                   Yes
    Resume from Hibernate
    ---------------------
    identifier              {3bc8de4e-00c0-11e8-9dfb-b11179f22ce6}
    device                  partition=C:
    path                    \WINDOWS\system32\winresume.efi
    description             Windows Resume Application
    locale                  en-US
    inherit                 {resumeloadersettings}
    recoverysequence        {3bc8de50-00c0-11e8-9dfb-b11179f22ce6}
    recoveryenabled         Yes
    isolatedcontext         Yes
    allowedinmemorysettings 0x15000075
    filedevice              partition=C:
    filepath                \hiberfil.sys
    bootmenupolicy          Standard
    debugoptionenabled      No
    Windows Memory Tester
    ---------------------
    identifier              {memdiag}
    device                  partition=\Device\HarddiskVolume2
    path                    \EFI\Microsoft\Boot\memtest.efi
    description             Windows Memory Diagnostic
    locale                  en-US
    inherit                 {globalsettings}
    badmemoryaccess         Yes
    EMS Settings
    ------------
    identifier              {emssettings}
    bootems                 No
    Debugger Settings
    -----------------
    identifier              {dbgsettings}
    debugtype               Local
    RAM Defects
    -----------
    identifier              {badmemory}
    Global Settings
    ---------------
    identifier              {globalsettings}
    inherit                 {dbgsettings}
                            {emssettings}
                            {badmemory}
    Boot Loader Settings
    --------------------
    identifier              {bootloadersettings}
    inherit                 {globalsettings}
                            {hypervisorsettings}
    Hypervisor Settings
    -------------------
    identifier              {hypervisorsettings}
    hypervisordebugtype     Serial
    hypervisordebugport     1
    hypervisorbaudrate      115200
    Resume Loader Settings
    ----------------------
    identifier              {resumeloadersettings}
    inherit                 {globalsettings}
    Device options
    --------------
    identifier              {3bc8de51-00c0-11e8-9dfb-b11179f22ce6}
    description             Windows Recovery
    ramdisksdidevice        partition=V:
    ramdisksdipath          \Recovery\WindowsRE\boot.sdi
    C:\WINDOWS\system32>
    Tuesday, March 27, 2018 3:59 PM

All replies

  • Hi,

    Every time when you upgrade Windows to the next version, the upgrade program will create a recovery partition if it detects that there is no sufficient space on your recovery partition (GPT disk) or system reserved partition (MBR disk). There is no wonder that you have many recovery partitions after upgrading to Windows 10. If you don’t want Windows to create another recovery partition, you can increase the size of recovery partition or system reserved partition before upgrading to Windows 10.

    According to Microsoft, the previous Windows version recovery partition will be nonfunctional, so you can delete the previous recovery partition to free up some disk space. As you may know that Windows can only shrink a partition from its right side, so you can tell which recovery partition was new created by upgrading to Windows 10.

    As you know, you are not allowed to remove recovery partition in Disk Management, but you use Diskpart.exe to delete partitions from command prompt.

    For more information, read this article:

    https://www.disk-partition.com/windows-10/recovery-partition-after-upgrading-to-windows-10-4348.html

    Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, March 28, 2018 6:52 AM
  • There are multiple computer in use and this computer is the computer that I practice steps on and perform in place upgrade repairs or clean installs when necessary.

    At the present time the computer has Windows 10 version 1709 and works fine.  Using diskpart there were 2 recovery partitions.  When helping others that have failed Windows 10 upgrades I have seen others remove the multiple recovery partitions so that this would be one less impediment for a successful upgrade.

    On this computer there are two recovery partitions.  They have different sizes.  Diskpart displays them both as RAW.  Reagentc /info displays disabled.

    Some questions:

    1) The computer easily goes into the safe mode.  How can the computer go into safe mode if Reagentc /info displays disabled?  Wouldn't it need to be enable to go into safe mode?

    Do you know of good information on reagentc:  when to use the command and its importance for Windows 10 upgrade BSOD or failure to upgrade problems.

    2) How come both partitions display RAW in diskpart?  Wouldn't they be working if the computer can go into safe mode?

    3) How can you tell which partition is in active use?

    4) There does not appear to be a date for the recovery partitions.  How can you tell which one is related to the latest Windows 10 upgrade?

    5) If the newer recovery partition is deleted would the computer no longer be able to open safe mode?

    6) If the computer can no longer go into safe mode using the Windows recovery on the computer will it be able to use the Windows 10 iso windows advanced troubleshooting menu?  If so what are the steps to format the recovery partitions, and install a new recovery partition?

    Wednesday, March 28, 2018 8:40 AM