Unknown device in boot order

Page 2 of 2 FirstFirst 12
  1. boombastik's Avatar
    Posts : 402
    Windows 10 X64 latest
    Thread Starter
       #11

    Saltgrass said:
    I think, just to be safe, I would run a basic bcdedit command or bcdedit /enum all to see what Windows Loader is showing as {Current}.

    It would be nice to see where that boot option, if it is actually being used, went.

    This is my bcedit:

    Unknown device in boot order-.jpg

    It is ok?

    And bellow follows enum all:

    C:\WINDOWS\system32>bcdedit /enum all

    Firmware Boot Manager
    ---------------------
    identifier {fwbootmgr}
    displayorder {bootmgr}
    {f8b33ddc-c0d7-11e6-a310-c1023f92ffa3}
    {f8b33dde-c0d7-11e6-a310-c1023f92ffa3}
    {f8b33de1-c0d7-11e6-a310-c1023f92ffa3}
    {f8b33de0-c0d7-11e6-a310-c1023f92ffa3}
    timeout 1

    Windows Boot Manager
    --------------------
    identifier {bootmgr}
    device partition=\Device\HarddiskVolume2
    path \EFI\Microsoft\Boot\bootmgfw.efi
    description Windows Boot Manager
    locale el-GR
    inherit {globalsettings}
    default {current}
    resumeobject {f8b33dd7-c0d7-11e6-a310-c1023f92ffa3}
    displayorder {current}
    toolsdisplayorder {memdiag}
    timeout 30

    Firmware Application (101fffff)
    -------------------------------
    identifier {f8b33ddc-c0d7-11e6-a310-c1023f92ffa3}
    device partition=\Device\HarddiskVolume2
    path \EFI\BOOT\BOOTX64.EFI
    description Unknown Device

    Firmware Application (101fffff)
    -------------------------------
    identifier {f8b33dde-c0d7-11e6-a310-c1023f92ffa3}
    description Hard Drive

    Firmware Application (101fffff)
    -------------------------------
    identifier {f8b33de0-c0d7-11e6-a310-c1023f92ffa3}
    description USB

    Firmware Application (101fffff)
    -------------------------------
    identifier {f8b33de1-c0d7-11e6-a310-c1023f92ffa3}
    description CD/DVD Drive

    Windows Boot Loader
    -------------------
    identifier {current}
    device partition=C:
    path \WINDOWS\system32\winload.efi
    description Windows 10
    locale el-GR
    inherit {bootloadersettings}
    recoverysequence {f8b33dd9-c0d7-11e6-a310-c1023f92ffa3}
    displaymessageoverride StartupRepair
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice partition=C:
    systemroot \WINDOWS
    resumeobject {f8b33dd7-c0d7-11e6-a310-c1023f92ffa3}
    nx OptIn
    bootmenupolicy Standard

    Windows Boot Loader
    -------------------
    identifier {f8b33dd9-c0d7-11e6-a310-c1023f92ffa3}
    device ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{f8b33dda-c0d7-11e6-a310-c1023f92ffa3}
    path \windows\system32\winload.efi
    description Windows Recovery Environment
    locale el-GR
    inherit {bootloadersettings}
    displaymessage Recovery
    osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{f8b33dda-c0d7-11e6-a310-c1023f92ffa3}
    systemroot \windows
    nx OptIn
    bootmenupolicy Standard
    winpe Yes

    Resume from Hibernate
    ---------------------
    identifier {f8b33dd7-c0d7-11e6-a310-c1023f92ffa3}
    device partition=C:
    path \WINDOWS\system32\winresume.efi
    description Windows Resume Application
    locale el-GR
    inherit {resumeloadersettings}
    recoverysequence {f8b33dd9-c0d7-11e6-a310-c1023f92ffa3}
    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
    locale el-GR
    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 {f8b33dda-c0d7-11e6-a310-c1023f92ffa3}
    description Windows Recovery
    ramdisksdidevice partition=\Device\HarddiskVolume1
    ramdisksdipath \Recovery\WindowsRE\boot.sdi
      My Computer


  2. Posts : 2,764
    Windows 10 Pro X64
       #12

    Hi,

    It seems that entry is not in use. I'd make a full image backup (using Macrium Reflect Free for example) and then delete the entry if it bothers you that much.

    Neosmart has a GUI for BCDedit called EasyBCD, you only need to register, download it and run it. Just make sure to delete the correct entry.

    Cheers,
      My Computers

  3. boombastik's Avatar
    Posts : 402
    Windows 10 X64 latest
    Thread Starter
       #13

    fdegrove said:
    Hi,

    It seems that entry is not in use. I'd make a full image backup (using Macrium Reflect Free for example) and then delete the entry if it bothers you that much.

    Neosmart has a GUI for BCDedit called EasyBCD, you only need to register, download it and run it. Just make sure to delete the correct entry.

    Cheers,
    Last question i need easybcd or i can simple delete with:
    bcdedit /delete {identifier}
      My Computer


  4. Posts : 2,764
    Windows 10 Pro X64
       #14

    Hi,

    You can do it manually, no problem. Just make sure you're covered.

    Cheers,
      My Computers


  5. Posts : 459
    Windows 8&10
       #15

    Thanks for the BCDedit listing. It appears the Bootx64.efi is the only reference, no OS loader is shown. If I remember correctly, the Bootx64.efi and bootmgfw.efi are the same file, just renamed.

    I suppose the listing just sends you directly to a Boot Manager and goes from there. In any case, I agree it does not appear to be needed.
      My Computer

  6. boombastik's Avatar
    Posts : 402
    Windows 10 X64 latest
    Thread Starter
       #16

    I created a full backup with macrium reflect and i delete it.
    I dont see any ill effects so all are ok.

    Now i dont see anymore this unknown device in my boot bios-uefi order.

    Thanks all for your time.
      My Computer


 
Page 2 of 2 FirstFirst 12

  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:15.
Find Us




Windows 10 Forums