Onedrive seems to have created its own drive G partition and moved my previous drive G partition to drive L

Anonymous
2021-10-01T22:00:28+00:00

One drive has messed up my partitions in that I had a drive G called WorkArea (G) that has the one drive folders to sync on it, along with all other files and folders on it. Somehow my G drive WorkArea (G) (partition) was reallocated to drive L WorkArea (L), and a separate partition G now called Local Disk (G). has appeared in the original drive G's place. (not talking about drive Mapping here).

In windows explorer I see the following screen shot

whereas in disk management, G does NOT show up at all and I cannot change WorkArea (L) back to G.

Drive L does show up in windows explorer, but is not in the screen shot. .

and trying to re-assign WorkArea to G I cannot, as it is unavailable.

how do I fix this?

I tried to uninstall OneDrive, and reboot but nothing changed.

Can someone please help me fix this as my backup plans are set for G as what is in WorkArea L and now backup of G only shows OneDrive files, that were not part of the backup plan to begin with.

Thanks for any help you can offer. Much appreciated.

Garry G

Windows for home | Windows 10 | Files, folders, and storage

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

47 answers

Sort by: Newest
  1. Anonymous
    2021-10-18T00:17:24+00:00

    You are welcome. That looks like a big success so far. Disk Management is showing the Recovery partitions appropriately in both its upper (disk 0 partition 4) & lower pane. DiskPart shows the letter is gone. You are free to use G: elsewhere. Hopefully, the mishap will not recur. I'm unsure what caused it in the first place. I do know, in these later versions of Windows, a letter gets automatically put onto the Recovery partition when you boot into the recovery environment. Also, the letters may scramble & be different there. But it all should be back to normal when rebooted back to Windows. Matbe it was that Attrib value at fault. It wanted Windows to keep the letter on Recovery.

    I think your BCD needs a lot of work. I'm inclined to suggest we generate a new one altogether. You've got a {bootmgr} section in there, but it is malformed & unused. There are other unused sections. Instead, from fiirmware (fwbootmgr), there is a jump to this thing...

    Firmware Application (101fffff)


    identifier {c4337ee6-11b0-11ec-ab4f-806e6f6e6963}

    device partition=\Device\HarddiskVolume2

    path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

    description Windows Boot Manager

    That Device & Path belong in your {bootmgr}, & the firmware should be going there. But yours does appear to get the job done. If you hold Shift & click "Restart", does Windows reboot to the recovery environment at the "Choose an Option" screen? And does it have the full panoply of options, including Troubleshoot & Advanced Options buttons? I don't know, maybe we should let it be, but I'm inclined to want to regenerate your BCD. Here is what mine looks like...

    (a) {bootmgr} is on top in the Firmware Boot Manager.

    (b) There are no duplicate, malformed or unused sections.

    Microsoft Windows [Version 10.0.19043.1288]

    (c) Microsoft Corporation. All rights reserved.

    C:\Windows\system32>bcdedit /enum all

    Firmware Boot Manager


    identifier {fwbootmgr}

    displayorder {bootmgr}

                        {140ab3f9-3491-11e7-a4a0-952787f57a8e} 
    
                        {140ab3fa-3491-11e7-a4a0-952787f57a8e} 
    

    timeout 1

    Windows Boot Manager


    identifier {bootmgr}

    device partition=\Device\HarddiskVolume1

    path \EFI\Microsoft\Boot\bootmgfw.efi

    description Windows Boot Manager

    locale en-US

    inherit {globalsettings}

    default {current}

    resumeobject {140ab3fc-3491-11e7-a4a0-952787f57a8e}

    displayorder {current}

    toolsdisplayorder {memdiag}

    timeout 30

    Firmware Application (101fffff)


    identifier {140ab3f9-3491-11e7-a4a0-952787f57a8e}

    description Onboard NIC(IPV4)

    Firmware Application (101fffff)


    identifier {140ab3fa-3491-11e7-a4a0-952787f57a8e}

    description Onboard NIC(IPV6)

    Windows Boot Loader


    identifier {current}

    device partition=C:

    path \Windows\system32\winload.efi

    description Windows 10

    locale en-US

    inherit {bootloadersettings}

    recoverysequence {140ab3fe-3491-11e7-a4a0-952787f57a8e}

    displaymessageoverride CommandPrompt

    recoveryenabled Yes

    isolatedcontext Yes

    allowedinmemorysettings 0x15000075

    osdevice partition=C:

    systemroot \Windows

    resumeobject {140ab3fc-3491-11e7-a4a0-952787f57a8e}

    nx OptIn

    bootmenupolicy Standard

    Windows Boot Loader


    identifier {140ab3fe-3491-11e7-a4a0-952787f57a8e}

    device ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{140ab3ff-3491-11e7-a4a0-952787f57a8e}

    path \windows\system32\winload.efi

    description Windows Recovery Environment

    locale en-us

    inherit {bootloadersettings}

    displaymessage Recovery

    osdevice ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{140ab3ff-3491-11e7-a4a0-952787f57a8e}

    systemroot \windows

    nx OptIn

    bootmenupolicy Standard

    winpe Yes

    Resume from Hibernate


    identifier {140ab3fc-3491-11e7-a4a0-952787f57a8e}

    device partition=C:

    path \Windows\system32\winresume.efi

    description Windows Resume Application

    locale en-US

    inherit {resumeloadersettings}

    recoverysequence {140ab3fe-3491-11e7-a4a0-952787f57a8e}

    recoveryenabled Yes

    isolatedcontext Yes

    allowedinmemorysettings 0x15000075

    filedevice partition=C:

    filepath \hiberfil.sys

    bootmenupolicy Standard

    debugoptionenabled No

    Windows Memory Tester


    identifier {memdiag}

    device partition=\Device\HarddiskVolume1

    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 {140ab3ff-3491-11e7-a4a0-952787f57a8e}

    description Windows Recovery

    ramdisksdidevice partition=\Device\HarddiskVolume4

    ramdisksdipath \Recovery\WindowsRE\boot.sdi

    C:\Windows\system32>

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-10-17T21:46:48+00:00

    Hi PCR ....

    Here is the latest as per your instructions. Thank you for your reply once again. Most appreciated.

    The disk management screen shot is at the end of the cmd information.

    In your last reply after the instructions, you said: the following, but I do not know what this means or what needs to be done next if anything. Can you please explain / clarify further ?

    "(2) The Firmware Boot Manager in the BCD is a window to the BIOS Boot menu screen. Yours isn't set normally for a UEFI installation.,,

    Firmware Boot Manager

    ---------------------

    identifier {fwbootmgr}

    displayorder

    {c4337ee6-11b0-11ec-ab4f-806e6f6e6963} <<<Direct boot to EFI

    {c4337ee7-11b0-11ec-ab4f-806e6f6e6963} <<<Direct to a hard drive

    {c4337ee8-11b0-11ec-ab4f-806e6f6e6963} <<<Also direct boot to EFI

    {c4337ee3-11b0-11ec-ab4f-806e6f6e6963} <<<Boot to CD/DVD drive

    timeout 0

    It should instead boot to the Windows Boot Manager ({bootmgr}). You do have one in the BCD, but it is missing its device & path values. There is a lot amiss in your BCD. I'm thinking we should generate a new one altogether instead of tinkering with this one.

    -----------------------------------------------------------------------------------

    cmd details follow here:

    Microsoft Windows [Version 10.0.19042.1237]

    (c) Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>diskpart

    Microsoft DiskPart version 10.0.19041.964

    Copyright (C) Microsoft Corporation.

    On computer: GARRY-INTEL1

    DISKPART> select disk 0

    Disk 0 is now the selected disk.

    DISKPART> select part 4

    Partition 4 is now the selected partition.

    DISKPART> detail part

    Partition 4

    Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac

    Hidden : Yes

    Required: No

    Attrib : 0000000000000000

    Offset in Bytes: 999546683392

    Volume ### Ltr Label Fs Type Size Status Info


    * Volume 4 G NTFS Partition 627 MB Healthy Hidden

    DISKPART> remove Letter=G

    DiskPart successfully removed the drive letter or mount point.

    DISKPART> GPT ATTRIBUTES=0x8000000000000001

    DiskPart successfully assigned the attributes to the selected GPT partition.

    DISKPART> detail part

    Partition 4

    Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac

    Hidden : Yes

    Required: Yes

    Attrib : 0X8000000000000001

    Offset in Bytes: 999546683392

    Volume ### Ltr Label Fs Type Size Status Info


    * Volume 4 NTFS Partition 627 MB Healthy Hidden

    DISKPART> exit

    and the view in file explorer now looks like this and note that there is no longer a drive G showing. I will now rename L: to G: so that my backups work again.

    Once again, thank you very much for your help so far. Nice to know that there is knowledgeable community help available, and that there are those like yourself willing to help. so grateful.

    Cheers!

    Garry

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-10-15T23:13:13+00:00

    (1) Here are your partitions on Disk 0...

    Partition ### Type Size Offset


    Partition 1 Reserved 128 MB 17 KB <<<MSR (Microsoft Reserved)

    Partition 2 System 100 MB 129 MB <<<EFI System partition

    Partition 3 Primary 930 GB 229 MB <<<Windows (C:)

    Partition 4 Recovery 627 MB 930 GB <<<Recovery partition

    The MSR doesn't show up in Disk Management by design. I'd rather it immediately precede Windows, but that's OK as is. The details of each is fine except for Recovery...

    Partition 4

    Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac

    Hidden : Yes

    Required: No

    Attrib : 0000000000000000

    Offset in Bytes: 999546683392

    Volume ### Ltr Label Fs Type Size Status Info


    * Volume 4 G NTFS Partition 627 MB Healthy Hidden

    The type code (GUID) is good. Required should be "yes". Let's remove the letter & set the Attrib properly...

    DiskPart <<<Enter DiskPart

    Select Disk 0 <<<Focus on Disk 0

    Select Part 4 <<<Focus on partition 4 (Recovery)

    Detail Part <<<Show the old details

    Remove Letter=G <<<Remove letter G

    GPT ATTRIBUTES=0x8000000000000001 <<<Set Attrib

    Detail Part <<<Show the new details

    Exit <<<Exit DiskPart

    Notes:

    0x8000000000000000 Prevents the partition from having a drive

                                      letter automatically assigned.
    

    0x0000000000000001 Marks the partition as required.

    After that, G: will no longer show up in File Explorer. Let's see a new picture of Disk Management to see whether it looks better for Recovery in the upper & lower panes.

    (2) The Firmware Boot Manager in the BCD is a window to the BIOS Boot menu screen. Yours isn't set normally for a UEFI installation.,,

    Firmware Boot Manager


    identifier {fwbootmgr}

    displayorder

    {c4337ee6-11b0-11ec-ab4f-806e6f6e6963} <<<Direct boot to EFI

    {c4337ee7-11b0-11ec-ab4f-806e6f6e6963} <<<Direct to a hard drive

    {c4337ee8-11b0-11ec-ab4f-806e6f6e6963} <<<Also direct boot to EFI

    {c4337ee3-11b0-11ec-ab4f-806e6f6e6963} <<<Boot to CD/DVD drive

    timeout 0

    It should instead boot to the Windows Boot Manager ({bootmgr}). You do have one in the BCD, but it is missing its device & path values. There is a lot amiss in your BCD. I'm thinking we should generate a new one altogether instead of tinkering with this one.

    (a) Have you ever been in BIOS & altered the Boot Menu?

    (b) Is BIOS set to boot in UEFI or Legacy mode? The missing {bootmgr} under Displayorder (above) has me wondering.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-10-15T14:20:10+00:00

    Hi PCR ..

    thanks again for your help. the following is the information you requested for partition 0.

    Hope this enable you to tell me how to fix tis.

    Much appreciated,

    Garry

    Microsoft Windows [Version 10.0.19042.1237]

    (c) Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>diskpart

    Microsoft DiskPart version 10.0.19041.964

    Copyright (C) Microsoft Corporation.

    On computer: GARRY-INTEL1

    DISKPART> list Vol

    Volume ### Ltr Label Fs Type Size Status Info


    Volume 0 Y DVD-ROM 0 B No Media

    Volume 1 Z DVD-ROM 0 B No Media

    Volume 2 C Local Disk NTFS Partition 930 GB Healthy Boot

    Volume 3 FAT32 Partition 100 MB Healthy System

    Volume 4 G NTFS Partition 627 MB Healthy Hidden

    Volume 5 D Application NTFS Partition 58 GB Healthy

    Volume 6 E Data1 NTFS Partition 429 GB Healthy

    Volume 7 F Data2 NTFS Partition 488 GB Healthy

    Volume 8 L WorkArea1 NTFS Partition 886 GB Healthy

    Volume 9 I Removable 0 B No Media

    Volume 10 J Removable 0 B No Media

    Volume 11 K Removable 0 B No Media

    Volume 12 M Removable 0 B No Media

    DISKPART> list Disk

    Disk ### Status Size Free Dyn Gpt


    Disk 0 Online 931 GB 0 B *

    Disk 1 Online 1863 GB 1024 KB

    Disk 2 No Media 0 B 0 B

    Disk 3 No Media 0 B 0 B

    Disk 4 No Media 0 B 0 B

    Disk 5 No Media 0 B 0 B

    DISKPART> select disk 0

    Disk 0 is now the selected disk.

    DISKPART> list part

    Partition ### Type Size Offset


    Partition 1 Reserved 128 MB 17 KB

    Partition 2 System 100 MB 129 MB

    Partition 3 Primary 930 GB 229 MB

    Partition 4 Recovery 627 MB 930 GB

    DISKPART> select part 1

    Partition 1 is now the selected partition.

    DISKPART> detail part

    Partition 1

    Type : e3c9e316-0b5c-4db8-817d-f92df00215ae

    Hidden : Yes

    Required: No

    Attrib : 0000000000000000

    Offset in Bytes: 17408

    There is no volume associated with this partition.

    DISKPART> select part2

    Microsoft DiskPart version 10.0.19041.964

    DISK - Shift the focus to a disk. For example, SELECT DISK.

    PARTITION - Shift the focus to a partition. For example, SELECT PARTITION.

    VOLUME - Shift the focus to a volume. For example, SELECT VOLUME.

    VDISK - Shift the focus to a virtual disk. For example, SELECT VDISK.

    DISKPART> detail part 2

    The arguments specified for this command are not valid.

    For more information on the command type: HELP DETAIL PARTITION

    DISKPART> list part

    Partition ### Type Size Offset


    * Partition 1 Reserved 128 MB 17 KB

    Partition 2 System 100 MB 129 MB

    Partition 3 Primary 930 GB 229 MB

    Partition 4 Recovery 627 MB 930 GB

    DISKPART> select part 2

    Partition 2 is now the selected partition.

    DISKPART> detail part

    Partition 2

    Type : c12a7328-f81f-11d2-ba4b-00a0c93ec93b

    Hidden : Yes

    Required: No

    Attrib : 0000000000000000

    Offset in Bytes: 135266304

    Volume ### Ltr Label Fs Type Size Status Info


    * Volume 3 FAT32 Partition 100 MB Healthy System

    DISKPART> list part

    Partition ### Type Size Offset


    Partition 1 Reserved 128 MB 17 KB

    * Partition 2 System 100 MB 129 MB

    Partition 3 Primary 930 GB 229 MB

    Partition 4 Recovery 627 MB 930 GB

    DISKPART> select part 3

    Partition 3 is now the selected partition.

    DISKPART> detail part

    Partition 3

    Type : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

    Hidden : No

    Required: No

    Attrib : 0000000000000000

    Offset in Bytes: 240123904

    Volume ### Ltr Label Fs Type Size Status Info


    * Volume 2 C Local Disk NTFS Partition 930 GB Healthy Boot

    DISKPART> list part

    Partition ### Type Size Offset


    Partition 1 Reserved 128 MB 17 KB

    Partition 2 System 100 MB 129 MB

    * Partition 3 Primary 930 GB 229 MB

    Partition 4 Recovery 627 MB 930 GB

    DISKPART> select part 4

    Partition 4 is now the selected partition.

    DISKPART> detail part

    Partition 4

    Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac

    Hidden : Yes

    Required: No

    Attrib : 0000000000000000

    Offset in Bytes: 999546683392

    Volume ### Ltr Label Fs Type Size Status Info


    * Volume 4 G NTFS Partition 627 MB Healthy Hidden

    DISKPART> exit

    Leaving DiskPart...

    C:\WINDOWS\system32>BCDEdit /Enum All

    Firmware Boot Manager


    identifier {fwbootmgr}

    displayorder {c4337ee6-11b0-11ec-ab4f-806e6f6e6963}

                        {c4337ee7-11b0-11ec-ab4f-806e6f6e6963} 
    
                        {c4337ee8-11b0-11ec-ab4f-806e6f6e6963} 
    
                        {c4337ee3-11b0-11ec-ab4f-806e6f6e6963} 
    

    timeout 0

    Windows Boot Manager


    identifier {bootmgr}

    device unknown

    description Windows Boot Manager

    locale en-US

    inherit {globalsettings}

    default {current}

    resumeobject {00699258-3744-11eb-956e-efd836ee9db2}

    displayorder {current}

    toolsdisplayorder {memdiag}

    timeout 30

    Firmware Application (101fffff)


    identifier {c4337ee3-11b0-11ec-ab4f-806e6f6e6963}

    description CD/DVD Drive

    Firmware Application (101fffff)


    identifier {c4337ee6-11b0-11ec-ab4f-806e6f6e6963}

    device partition=\Device\HarddiskVolume2

    path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

    description Windows Boot Manager

    Firmware Application (101fffff)


    identifier {c4337ee7-11b0-11ec-ab4f-806e6f6e6963}

    description Hard Drive

    Firmware Application (101fffff)


    identifier {c4337ee8-11b0-11ec-ab4f-806e6f6e6963}

    device partition=\Device\HarddiskVolume2

    path \EFI\Microsoft\Boot\bootmgfw.efi

    description Windows Boot Manager

    Windows Boot Loader


    identifier {current}

    device partition=C:

    path \WINDOWS\system32\winload.efi

    description Windows 10

    locale en-US

    inherit {bootloadersettings}

    recoverysequence {201ca33c-3744-11eb-ab08-a9da93046d68}

    displaymessageoverride Recovery

    recoveryenabled Yes

    allowedinmemorysettings 0x15000075

    osdevice partition=C:

    systemroot \WINDOWS

    resumeobject {00699258-3744-11eb-956e-efd836ee9db2}

    nx OptIn

    bootmenupolicy Standard

    Windows Boot Loader


    identifier {201ca33c-3744-11eb-ab08-a9da93046d68}

    device partition=G:

    path \windows\system32\winload.efi

    description Windows Recovery Environment

    locale en-US

    inherit {bootloadersettings}

    displaymessage Recovery

    osdevice partition=G:

    systemroot \windows

    nx OptIn

    bootmenupolicy Standard

    winpe Yes

    Windows Boot Loader


    identifier {becbfbbb-74c1-11e3-a193-d3e592cc6be4}

    device partition=C:

    path \windows\system32\winload.efi

    description Windows Recovery Environment

    inherit {bootloadersettings}

    osdevice partition=C:

    systemroot \windows

    nx OptIn

    winpe Yes

    Resume from Hibernate


    identifier {00699258-3744-11eb-956e-efd836ee9db2}

    device partition=C:

    path \WINDOWS\system32\winresume.efi

    description Windows Resume Application

    locale en-US

    inherit {resumeloadersettings}

    recoverysequence {201ca33c-3744-11eb-ab08-a9da93046d68}

    recoveryenabled Yes

    allowedinmemorysettings 0x15000075

    filedevice partition=C:

    filepath \hiberfil.sys

    bootmenupolicy Standard

    debugoptionenabled No

    Windows Memory Tester


    identifier {memdiag}

    device unknown

    path \boot\memtest.exe

    description Windows Memory Diagnostic

    locale en-US

    inherit {globalsettings}

    badmemoryaccess Yes

    EMS Settings


    identifier {emssettings}

    bootems No

    Debugger Settings


    identifier {dbgsettings}

    debugtype Serial

    debugport 1

    baudrate 115200

    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 {201ca33d-3744-11eb-ab08-a9da93046d68}

    description Windows Recovery

    ramdisksdidevice partition=G:

    ramdisksdipath \Recovery\WindowsRE\boot.sdi

    Device options


    identifier {becbfbbc-74c1-11e3-a193-d3e592cc6be4}

    description Ramdisk Options

    ramdisksdidevice partition=C:

    ramdisksdipath \Recovery\becbfbbb-74c1-11e3-a193-d3e592cc6be4\boot.sdi

    C:\WINDOWS\system32>

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-10-14T01:08:42+00:00

    (1) Oops, I wanted Disk 0. Please repeat DiskPart for Disk 0...?...

    DiskPart <<<Enter DiskPart

    List Vol <<<List the Volumes

    List Disk <<<List the Disks

    Select Disk 0 <<<Focus on Disk 0

    List Part <<<List the partition numbers on Disk 0

    == For each partition number (x) enter the following two commands ==

    Select Part x <<<Focus on partition x

    Detail Part <<<Show partition info

    == After that, exit DiskPart ==

    Exit <<<Exit DiskPart

    BCDEdit /Enum All <<<And let's see the BCD

    (2) I see G:drive is there in your List Vol...

      Volume 4  **G**  NTFS Partition  627 MB  Healthy Hidden
    

    It is the 627 MB partition appearing after C: in your Disk Management (DM). But it looks wrong in DM. It should look like mine...

    Image

    With or without a letter on my Recovery partition, I get that designation (disk 0 partition 4) in the top pane. And the bottom is as circled. Neither the letter nor the label I put on it (WinRE 21H1) show up in the bottom pane. (I'm sure they used to in prior versions.) They only show in DiskPart & File Explorer now. And here is what mine looks like in DiskPart...

    DISKPART> Detail Part

    Partition 4

    Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac

    Hidden : Yes

    Required: Yes

    Attrib : 0X8000000000000001

    Offset in Bytes: 999313944576

    Volume ### Ltr Label Fs Type Size Status Info


    * Volume 3 WinRE 21H1 NTFS Partition 847 MB Healthy Hidden

    We want to get the letter off yours, but most important will be the Type code & possibly the Attrib. I suspect your Type code has gone bad & must be made to match mine. Hopefully, that will get your Disk Management to match mine. Then, we need to activate the Recovery partition either using ReagentC (which may not work) or by putting the code for it directly into the BCD.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments