Advance boot options empty

Page 2 of 2 FirstFirst 12

  1. Posts : 18,432
    Windows 11 Pro
       #11

    topgundcp said:
    From Admin Command, run: reagentc /info ====> Post the result
    then run: bcdedit /enum all =====> post the result
    and that will be the reason he doesn't have the advanced boot menu - there is something wrong that is causing the WindowsRE partition to be disabled.
      My Computer


  2. Posts : 5
    Windows 10 Education
    Thread Starter
       #12

    topgundcp said:
    From Admin Command, run: reagentc /info ====> Post the result
    then run: bcdedit /enum all =====> post the result
    C:\Windows\system32>reagentc /info
    REAGENTC.EXE: Operation failed: 3

    REAGENTC.EXE: An error has occurred.

    C:\Windows\system32>bcdedit /enum all

    Firmware Boot Manager
    ---------------------
    identifier {fwbootmgr}
    displayorder {bootmgr}
    {6ea5af83-d3be-11e6-b9f1-806e6f6e6963}
    {1e31914d-d3c4-11e6-b9f9-806e6f6e6963}
    {1e31914e-d3c4-11e6-b9f9-806e6f6e6963}
    {1e31914f-d3c4-11e6-b9f9-806e6f6e6963}
    timeout 1

    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 {fc9f18db-9d9c-11e6-afae-edc23264c6e3}
    displayorder {current}
    toolsdisplayorder {memdiag}
    timeout 30
    displaybootmenu No

    Firmware Application (101fffff)
    -------------------------------
    identifier {1e31914d-d3c4-11e6-b9f9-806e6f6e6963}
    description UEFI:CD/DVD Drive

    Firmware Application (101fffff)
    -------------------------------
    identifier {1e31914e-d3c4-11e6-b9f9-806e6f6e6963}
    description UEFI:Removable Device

    Firmware Application (101fffff)
    -------------------------------
    identifier {1e31914f-d3c4-11e6-b9f9-806e6f6e6963}
    description UEFI:Network Device

    Firmware Application (101fffff)
    -------------------------------
    identifier {6ea5af83-d3be-11e6-b9f1-806e6f6e6963}
    device unknown
    description UEFI: Patriot Memory PMAP, Partition 1

    Windows Boot Loader
    -------------------
    identifier {current}
    device partition=C:
    path \Windows\system32\winload.efi
    description Windows 10
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {fc9f18dd-9d9c-11e6-afae-edc23264c6e3}
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice partition=C:
    systemroot \Windows
    resumeobject {fc9f18db-9d9c-11e6-afae-edc23264c6e3}
    nx OptIn
    bootmenupolicy Legacy

    Windows Boot Loader
    -------------------
    identifier {fc9f18dd-9d9c-11e6-afae-edc23264c6e3}
    device ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{fc9f18de-9d9c-11e6-afae-edc23264c6e3}
    path \windows\system32\winload.efi
    description Windows Recovery Environment
    locale en-US
    inherit {bootloadersettings}
    displaymessage Recovery
    displaymessageoverride Recovery
    osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{fc9f18de-9d9c-11e6-afae-edc23264c6e3}
    systemroot \windows
    nx OptIn
    bootmenupolicy Standard
    winpe Yes

    Resume from Hibernate
    ---------------------
    identifier {fc9f18db-9d9c-11e6-afae-edc23264c6e3}
    device partition=C:
    path \Windows\system32\winresume.efi
    description Windows Resume Application
    locale en-US
    inherit {resumeloadersettings}
    recoverysequence {fc9f18dd-9d9c-11e6-afae-edc23264c6e3}
    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 {fc9f18de-9d9c-11e6-afae-edc23264c6e3}
    description Windows Recovery
    ramdisksdidevice partition=\Device\HarddiskVolume1
    ramdisksdipath \Recovery\WindowsRE\boot.sdi
      My Computer


  3. Posts : 2,799
    Linux Mint 20.1 Win10Prox64
       #13

    Similar problem was solved in this thread from 8 forum but would be the same for 10.
    Solved Could not find recovery environment

    However, try this command first before using the link above.
    reagentc.exe /setreimage /path \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE /target C:\windows
      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 09:32.
Find Us




Windows 10 Forums