Can't access Windows Recovery Environment (BCD issue)

Discussion in 'Windows 7 Help and Support' started by Dillano609, May 6, 2013.

  1. Dillano609

    Dillano609 New Member

    Joined:
    May 6, 2013
    Messages:
    6
    Likes Received:
    0
    Hello all, this is my first post here so please be kind, haha.

    Anyway, recently my hard drive forgot that there were partitions on it and came up as nothing when I plugged it in a different computer. Disk management told me it was all unallocated space. I recovered the partitions C:\ (TI106166W0D) and E:\ (HDDRECOVERY). Everything works fine again, but I can't access the WinRE. Every time I press F8 it says:

    Status: 0xc000000e

    Info: The boot selection failed because a required device is inaccessible.

    I tried using startup repair using an OEM disk and tried the bootrec commands to no avail. Who can help me?

    (Additional Info)

    I'm convinced that this issue resides in the BCD. I entered the command prompt and went to bcdedit /enum all and got the following results:

    Windows Boot Manager
    --------------------
    identifier {bootmgr}
    device partition=\Device\HarddiskVolume1
    path \bootmgr
    description Windows Boot Manager
    locale en-US
    inherit {globalsettings}
    default {current}
    resumeobject {16cd0409-404a-11e2-87ee-e1b942f7ed70}
    displayorder {current}
    toolsdisplayorder {memdiag}
    timeout 30


    Windows Boot Loader
    -------------------
    identifier {16cd040a-404a-11e2-87ee-e1b942f7ed70}
    device unknown
    path \windows\system32\winload.exe
    description Windows 7
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {16cd040b-404a-11e2-87ee-e1b942f7ed70}
    recoveryenabled Yes
    osdevice unknown
    systemroot \windows
    resumeobject {16cd0409-404a-11e2-87ee-e1b942f7ed70}
    nx OptIn


    Windows Boot Loader
    -------------------
    identifier {16cd040b-404a-11e2-87ee-e1b942f7ed70}


    Windows Boot Loader
    -------------------
    identifier {current}
    device partition=C:
    path \Windows\system32\winload.exe
    description Windows 7 Home Premium (recovered)
    locale en-US
    recoverysequence {16cd040b-404a-11e2-87ee-e1b942f7ed70}
    recoveryenabled Yes
    osdevice partition=C:
    systemroot \Windows
    resumeobject {26d01fcc-b175-11e2-bb95-806e6f6e6963}


    Windows Boot Loader
    -------------------
    identifier {16cd040e-404a-11e2-87ee-e1b942f7ed70}
    device ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Win
    re.wim,{16cd040f-404a-11e2-87ee-e1b942f7ed70}
    path \windows\system32\winload.exe
    description Windows Recovery Environment (recovered)
    locale
    osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Win
    re.wim,{16cd040f-404a-11e2-87ee-e1b942f7ed70}
    systemroot \windows
    winpe Yes


    Resume from Hibernate
    ---------------------
    identifier {16cd0409-404a-11e2-87ee-e1b942f7ed70}
    device unknown
    path \windows\system32\winresume.exe
    description Windows Resume Application
    locale en-US
    inherit {resumeloadersettings}
    filedevice unknown
    filepath \hiberfil.sys
    debugoptionenabled No


    Resume from Hibernate
    ---------------------
    identifier {26d01fcc-b175-11e2-bb95-806e6f6e6963}
    device partition=C:
    path \Windows\system32\winresume.exe
    description Windows 7 Home Premium (recovered)
    locale en-US
    inherit {resumeloadersettings}
    filedevice partition=C:
    filepath \hiberfil.sys
    debugoptionenabled No


    Windows Memory Tester
    ---------------------
    identifier {memdiag}
    device partition=\Device\HarddiskVolume1
    path \boot\memtest.exe
    description Windows Memory Diagnostic
    locale en-US
    inherit {globalsettings}
    badmemoryaccess Yes


    EMS Settings
    ------------
    identifier {emssettings}
    bootems Yes


    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 {16cd040c-404a-11e2-87ee-e1b942f7ed70}
    description Ramdisk Options
    ramdisksdidevice unknown
    ramdisksdipath \Recovery\WindowsRE\boot.sdi


    Device options
    --------------
    identifier {16cd040f-404a-11e2-87ee-e1b942f7ed70}
    ramdisksdidevice partition=\Device\HarddiskVolume1
    ramdisksdipath \Recovery\WindowsRE\boot.sdi
     
  2. MikeHawthorne

    MikeHawthorne Essential Member
    Microsoft Community Contributor

    Joined:
    May 25, 2009
    Messages:
    6,045
    Likes Received:
    300
    Hi

    I don't know if this will help with your issue but for me using EasyBCD makes it easier to work on stuff like this.
    At least it shows you boot settings in an easy to understand format, and give you the tools to change it easily or create a new one.

    Download EasyBCD Community Edition 2.2.0.182 Free - A handy tool for tweaking your system - Softpedia

    I have to admit that I have no idea what the problem on your computer is, but if it's in the boot sector maybe this will help.

    Hopefully someone else will recognise this issue and have more input.

    Mike
     
  3. Dillano609

    Dillano609 New Member

    Joined:
    May 6, 2013
    Messages:
    6
    Likes Received:
    0
    Ahh, I shall look into it. Hopefully it helps. Apparently its a very rare issue. I was only able to find a single other instance that was close to mine but it is with a system with solely one partition. My configuration has two partitions. Here is a link to that thread:

    Windows 7, "Repair your computer" F8 boot option not working (SOLVED) | Knowledge Base

    The answer comes so close, but I need confirmation of the identifiers I need to use since I have 2 partitions. I want to have access to my Toshiba recovery partition again, I just don't know how to make the link :/
     
    #3 Dillano609, May 6, 2013
    Last edited: May 6, 2013
  4. Dillano609

    Dillano609 New Member

    Joined:
    May 6, 2013
    Messages:
    6
    Likes Received:
    0
    WinRE issue SOLVED! (Mostly)

    So as it turns out the recoverysequence and the device value in boot loader value were not the same so I did the following in cmd running as an admin:

    bcdedit /set recoverysequence {16cd040f-404a-11e2-87ee-e1b942f7ed70}
    bcdedit /set {16cd040f-404a-11e2-87ee-e1b942f7ed70} description "Windows Recovery Environment"
    bcdedit /set {16cd040f-404a-11e2-87ee-e1b942f7ed70} locale en-US

    Then to make sure everything is as it should be I entered the commands:

    reagentc /info (This is for the Extended configuration for the Recovery Environment)
    reagentc /disable
    reagentc /enable

    My only remaining issue now is that when WinPE comes up the background is black and the Toshiba Recovery Wizard instead of asking if I want to re-install windows is asking me to put in recovery media when I have a recovery partition that I've used before. :/
     
    #4 Dillano609, May 6, 2013
    Last edited: May 6, 2013
  5. Saltgrass

    Saltgrass Excellent Member
    Microsoft Community Contributor

    Joined:
    Oct 16, 2009
    Messages:
    15,157
    Likes Received:
    393
    Re: WinRE issue SOLVED! (Mostly)

    Since the BCD listing you posted is now out of date, you might think about submitting another one. Have you checked the GUID number on the folder that holds the Wimre.wim file. You can do that using the command prompt and dir /a command in the C:\Recovery folder, which is a System folder so you may need to allow viewing of those.

    As far are your Toshiba recovery, since I do not have any OEM installs I cannot say for sure, but it was probably listed in the BCD store and gave you another option during boot. But I have no information as to how it would have worked or how it would have accessed its recovery utility so it could use the Factory Recovery files.

    Edit: I suppose I should mention, if you used 40f for you Ramdisk ID, you already had a 40f for a Device Options entry. But I will check again if you re-post the BCD information.
     
    #5 Saltgrass, May 7, 2013
    Last edited: May 7, 2013

Share This Page

Loading...