• Confusion on bcdedit and removing dual boot

    Home » Forums » AskWoody support » Windows » Windows 8.1 » Questions: Win 8.1 (and Win 8) » Confusion on bcdedit and removing dual boot

    Author
    Topic
    #487926

    I installed Windows 8 on both my home and work PC dual-booting with Windows 7. It was really easy to do and helped me get over the hump on learning Win8 while still having Win7 to work on. Now that I have eliminated Win7 from both PCs, I still have stuff to clean up in BCD on both PC’s.

    At home, I have the Win8 partition (C:) set up as everything now…system, boot, active, etc. There is an empty partition (G:) that is a combination of the Recovery partition and the Win7 partition…removing this partition currently gives me an unbootable situation.

    When I run bcdedit /enum /v … it has an entry for Bootmgr and says it is located on the G: drive. There is nothing on that partition anymore, least of all the Bootmgr. The PC boots up into Win8 just fine. Isn’t there some simple way to correct the BCD storefile so that it knows the bootmgr is on C:, which it is.

    And then there is the work PC. The BCDedit entry appears mostly OK. There’s one mysterious boot loader entry that has the win8 partition address and just says “identifier”, but doesn’t have any other descriptions and doesn’t show up in the menu at all.

    But I don’t see that entry I have at home claiming that the bootmgr is on a separate partition. Both PCs come up fine. I don’t know where that hibernate entry came from…I didn’t add it. It doesn’t show on the menu. So besides the general wreckage on my drives, I am wondering how to correct the BCD storefile at home to remove/correct that reference to the bootmgr being on another drive. It looks to me like dual-booting is something you want to think long and hard about doing. Easy to do, but hard to undo.

    It sounds like all I had to do at home is let it go unbootable and then boot up the Win8 disk and go into repair mode to fix where it is booting from. Is that the only option?

    Also, I’ve been using Paragon Hard Disk Manager 12 to add more space to one partition and take from the other (my Win7 partion was on the left) as I was gradually moving applications over to Win8…the last time I did this (and I still have more space to recover), I got a list of minor errors on the win7 and win8 partitions…something to do with hard links. That doesn’t give me any warm fuzzy feelings. Everything is working fine, but I can’t help but wonder whether I have some corruption now. The Win7 partition no longer has an OS on it all.

    Work BCD: (I can add the entry for home later)

    Windows Boot Loader
    ——————-
    identifier {323f4c97-53a5-11e2-b192-8707d0383f5b}
    device partition=C:
    path Windowssystem32winload.exe
    description Windows 8
    locale en-US
    inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence {323f4c98-53a5-11e2-b192-8707d0383f5b}
    integrityservices Enable
    recoveryenabled Yes
    allowedinmemorysettings 0x15000075
    osdevice partition=C:
    systemroot Windows
    resumeobject {323f4c96-53a5-11e2-b192-8707d0383f5b}
    nx OptIn
    bootmenupolicy Standard
    quietboot No

    Windows Boot Loader
    ——————-
    identifier {323f4c98-53a5-11e2-b192-8707d0383f5b}

    Windows Boot Loader
    ——————-
    identifier {d28b0fe8-7163-11e2-bedc-d4bed9a07e54}
    device partition=C:
    path Windowssystem32winload.exe
    description Windows 8 Safe Mode
    locale en-US
    inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence {323f4c98-53a5-11e2-b192-8707d0383f5b}
    integrityservices Enable
    recoveryenabled Yes
    allowedinmemorysettings 0x15000075
    osdevice partition=C:
    systemroot Windows
    resumeobject {323f4c96-53a5-11e2-b192-8707d0383f5b}
    nx OptIn
    safeboot Minimal
    bootmenupolicy Standard
    quietboot No

    Windows Boot Loader
    ——————-
    identifier {d28b0fe9-7163-11e2-bedc-d4bed9a07e54}
    device partition=C:
    path Windowssystem32winload.exe
    description Windows 8 Save Networking
    locale en-US
    inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence {323f4c98-53a5-11e2-b192-8707d0383f5b}
    integrityservices Enable
    recoveryenabled Yes
    allowedinmemorysettings 0x15000075
    osdevice partition=C:
    systemroot Windows
    resumeobject {323f4c96-53a5-11e2-b192-8707d0383f5b}
    nx OptIn
    safeboot Network
    bootmenupolicy Standard
    quietboot No

    Resume from Hibernate
    ———————
    identifier {323f4c96-53a5-11e2-b192-8707d0383f5b}
    device partition=C:
    path Windowssystem32winresume.exe
    description Windows Resume Application
    locale en-US
    inherit {1afa9c49-16ab-4a5c-901b-212802da9460}
    recoverysequence {323f4c98-53a5-11e2-b192-8707d0383f5b}
    recoveryenabled Yes
    allowedinmemorysettings 0x15000075
    filedevice partition=C:
    filepath hiberfil.sys
    bootmenupolicy Standard
    debugoptionenabled No

    Viewing 3 reply threads
    Author
    Replies
    • #1376177

      Try booting to the Win 8 installation disk and choose Repair My Pc and then automatic repair options. This should fix the MBR.

      Also you can use an app such as Partition Wizardto reclaim the space that was Win 7 and the Recovery Partition. Open Partition Wizard from Win 8 and delete both of these partitions. This will leave unallocated space, then highlight the Win 8 partition and drag it’s edge across the unallocated space to the opposite edge of the unallocated space. When you choose Apply, the PC will reboot and the changes will be made outside of Windows.

      31827-PartitionWizard

      Note: my screen shot shows resizing the partition to the right. This can also be done to the left.

    • #1376184

      Alternatively, open a command prompt and run bcdboot c:windows /s c:
      This will put the boot files on C: and you should then be able to remove G:.

      cheers, Paul

      • #1376186

        Here is my home BCD info…why do I have this first entry at all, but don’t have it at work and how can I get it pointing at C instead of G?

        Windows Boot Manager
        ——————–
        identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
        device partition=G:
        description Windows Boot Manager
        locale en-US
        inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
        integrityservices Enable
        default {a74407fc-6517-11e2-b487-f9e5dd5cd3f1}
        resumeobject {a74407fb-6517-11e2-b487-f9e5dd5cd3f1}
        displayorder {a74407fc-6517-11e2-b487-f9e5dd5cd3f1}
        {a74407ff-6517-11e2-b487-f9e5dd5cd3f1}
        {a7440800-6517-11e2-b487-f9e5dd5cd3f1}
        toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
        timeout 30

        Windows Boot Loader
        ——————-
        identifier {a74407fc-6517-11e2-b487-f9e5dd5cd3f1}
        device partition=C:
        path Windowssystem32winload.exe
        description Windows 8
        locale en-US
        inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
        recoverysequence {a74407fd-6517-11e2-b487-f9e5dd5cd3f1}
        integrityservices Enable
        recoveryenabled Yes
        allowedinmemorysettings 0x15000075
        osdevice partition=C:
        systemroot Windows
        resumeobject {a74407fb-6517-11e2-b487-f9e5dd5cd3f1}
        nx OptIn
        bootmenupolicy Standard
        quietboot No

        Windows Boot Loader
        ——————-
        identifier {a74407ff-6517-11e2-b487-f9e5dd5cd3f1}
        device partition=C:
        path Windowssystem32winload.exe
        description Win 8 Safe Networking Mode
        locale en-US
        inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
        recoverysequence {a74407fd-6517-11e2-b487-f9e5dd5cd3f1}
        integrityservices Enable
        recoveryenabled Yes
        allowedinmemorysettings 0x15000075
        osdevice partition=C:
        systemroot Windows
        resumeobject {a74407fb-6517-11e2-b487-f9e5dd5cd3f1}
        nx OptIn
        safeboot Network
        bootmenupolicy Standard

        Windows Boot Loader
        ——————-
        identifier {a7440800-6517-11e2-b487-f9e5dd5cd3f1}
        device partition=C:
        path Windowssystem32winload.exe
        description Windows 8 Safe Mode
        locale en-US
        inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
        recoverysequence {a74407fd-6517-11e2-b487-f9e5dd5cd3f1}
        integrityservices Enable
        recoveryenabled Yes
        allowedinmemorysettings 0x15000075
        osdevice partition=C:
        systemroot Windows
        resumeobject {a74407fb-6517-11e2-b487-f9e5dd5cd3f1}
        nx OptIn
        safeboot Minimal
        bootmenupolicy Standard

    • #1376194

      BCDBOOT will rebuild the boot information and put the required files where you need them.

      cheers, Paul

    • #1376210

      I was going to add that the MBR can be fixed manually I the auto repair option does not work, but my esteemed colleagues have filled in that missing piece.

    Viewing 3 reply threads
    Reply To: Confusion on bcdedit and removing dual boot

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: