Unable to access Windows Recovery Environment normally


  1. Posts : 1
    Windows 10
       #1

    Unable to access Windows Recovery Environment normally


    Hello everybody,

    I have a problem I've spent hours banging my head against and am hoping somebody here can help me. I am unable to access the Recovery Environment through the settings "Advanced Startup Options" option or the shift+restart method. shutdown /r /o also doesn't work.

    The recovery image is working correctly. If I use reagentc /boottore the recovery environment opens on the next startup just like it's supposed to.

    Reagentc /info shows the recovery environment is active and all the ids and paths show up in BCDEdit correctly.

    Windows RE status: Enabled
    Windows RE location: \\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: 930d0e52-dcd9-11e9-918e-30d16ba4678a
    Recovery image location:
    Recovery image index: 0
    Custom image location:
    Custom image index: 0
    Windows Boot Loader
    -------------------
    identifier {current}
    device partition=C:
    path \WINDOWS\system32\winload.efi
    description Windows 10
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {930d0e52-dcd9-11e9-918e-30d16ba4678a}
    displaymessageoverride Recovery
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice partition=C:
    systemroot \WINDOWS
    resumeobject {80a67990-dc96-11e9-bd09-a80b7881755e}
    nx OptIn
    bootmenupolicy Standard
    Windows Boot Loader
    -------------------
    identifier {930d0e52-dcd9-11e9-918e-30d16ba4678a}
    device ramdisk=[E:]\Recovery\WindowsRE\Winre.wim,{930d0e53-dcd9-11e9-918e-30d16ba4678a}
    path \windows\system32\winload.efi
    description Windows Recovery Environment
    locale en-US
    inherit {bootloadersettings}
    displaymessage Recovery
    osdevice ramdisk=[E:]\Recovery\WindowsRE\Winre.wim,{930d0e53-dcd9-11e9-918e-30d16ba4678a}
    systemroot \windows
    nx OptIn
    bootmenupolicy Standard
    winpe Yes
    Hopefully somebody can point me in the right direction!
      My Computer


  2. Posts : 35,575
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #2

    Hi, welcome to tenforums.

    To help anyone answering this- and there are some members who can help with this- please post a full screen screenshot of your disks and partitions using Minitool Partition Wizard (or similar) - not Disk Management.

    To post a screenshot please use the Insert Image icon above your post. Thanks.

    Please complete your system specs including disk details. (See mine for comparison). Tutorial available if needed.
    Programs like Speccy, HWinfo can help.

    What is your Windows build? Sadly it's not a forum requirement, so we have to keep asking people.
    Settings, About
      My Computers


  3. Posts : 39,996
    windows 10 professional version 1607 build 14393.969 64 bit
       #3

    Open administrative command prompt and copy and paste: (all at the same time)

    Code:
    bcdedit /enum all
    bcdedit /enum /v
    reagentc /info
    diskpart
    lis dis
    lis vol
    sel dis 0
    det dis
    lis par
    sel par 1
    det par
    sel par 2
    det par
    sel par 3
    det par
    sel par 4
    det par
    sel par 5
    det par
    sel par 6
    det par
    sel dis 1
    det dis
    lis par
    sel par 1
    det par
    sel par 2
    det par
    sel par 3
    det par
    sel par 4
    det par
    sel par 5
    det par
    sel par 6
    det par
    When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    Was there dual booting?
    device ramdisk=[E:]\Recovery\WindowsRE\Winre.wim,{930d0e53-dcd9-11e9-918e-30d16ba4678a}
    Last edited by zbook; 22 Sep 2019 at 02:26.
      My Computer


  4. Posts : 2,790
    Linux Mint 20.1 Win10Prox64
       #4

    Some entries in the bcd for the recovery environment is either corrupted or missing. To fix the problem, you;d need to rebuild the entries for the recovery environment.
    Here's the steps:
    1. Turn on folder options to show hidden files/folders. Open admin command then type: reagentc /disable
      - This will move 2 files from the recovery partition reagent.xml and winre.wim to C:\windows\system32\recovery
    2. If you have the Windows 10 ISO, double click on it to mount to a virtual cd/dvd else If you have the Windows 10 USB then navigate to Sources folder and look for install.esd or install.wim.
    3. Use 7-ZIP to open install.esd or install.wim, select and index. eg. 6 then navigate to Windows\system32\recovery. You'd see 2 files: Winre.wim and reagent.xml.
    4. Remove everything from C:\windows\system32\recovery (ie. your current winre.win and reagent.xml)
    5. Copy the new winre.wim and reagent.xml from the install.esd/install.wim to C:\windows\system32\Recovery
    6. From admin command, type: ReAgentc /enable

    Reboot to recovery. This will also fix the problem with shutdown /r /o
      My Computer


 

  Related Discussions
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 16:44.
Find Us




Windows 10 Forums