Page 1 of 2 12 LastLast
  1.    05 Sep 2017 #1
    Join Date : Nov 2015
    Posts : 46
    Windows 10 X64

    Unknown device in boot order


    Hallo i have an asrock z97 motherboard in uefi mode with windows 10.

    In boot order menu in bios menu it lists windows boot manager, dvd rom, hdd and a boot entry that is says unknown device.
    So when i boot in my system i used the command bcdedit /enum firmware and i have this:

    Click image for larger version. 

Name:	cmd.jpg 
Views:	25 
Size:	317.2 KB 
ID:	151995


    What it is this unknown entry?
    Can i fix it?
      My ComputerSystem Spec
  2.    05 Sep 2017 #2
    Join Date : Jul 2015
    Posts : 9,397
    Windows 10 Pro

    You can delete it. Looks like it is an entry to an EFI shell (kind of like command prompt for UEFI).
      My ComputerSystem Spec
  3.    05 Sep 2017 #3
    Join Date : Nov 2015
    Posts : 46
    Windows 10 X64
    Thread Starter

    It is possible that the bootx64.efi is the backup of windows boot manager if nvram fails?


    ANd how can i delete it ?
    thanks for the help
    Billy
      My ComputerSystem Spec
  4.    05 Sep 2017 #4
    Join Date : Jul 2015
    Posts : 9,397
    Windows 10 Pro

    Select and copy the identifier, then:
    bcdedit /delete {identifier}

    paste the identifier in after /delete
      My ComputerSystem Spec
  5.    05 Sep 2017 #5
    Join Date : Sep 2014
    DFW Area
    Posts : 439
    Windows 8&10

    Some folks over on the Dell site were suggesting adding such a boot entry to get their systems to boot after having a "no boot device" type message.

    It seems to work although I have not needed to try.
      My ComputerSystem Spec
  6.    05 Sep 2017 #6
    Join Date : Oct 2015
    Posts : 2,043
    Windows 10 Pro X64

    Hi,

    It's not an EFI shell loader. It's a bootloader that you can create to be able to load Windows in either EFI or BIOS mode.

    For instance: bcdboot C:\Windows /s S: /f ALL
    Where "S:" is the partition's drive letter.

    It's what I have done on a USB stick so if my boot partition has been nuked I can still access Windows by simply booting off that stick.

    In TS's case these file may have been created by the OEM after the image was applied.

    Cheers,
    Last edited by fdegrove; 05 Sep 2017 at 11:17.
      My ComputersSystem Spec
  7.    05 Sep 2017 #7
    Join Date : Nov 2015
    Posts : 46
    Windows 10 X64
    Thread Starter

    It is possible to rename it?
    From unknown device to something like backup boot?
    Or it is better to delete it?

    This machine is formated by me in uefi mode in a an asus motherboard. And when motherboard failed i change it with an asrock. I dont know if it has nothing to do with it.
      My ComputerSystem Spec
  8.    05 Sep 2017 #8
    Join Date : Sep 2014
    DFW Area
    Posts : 439
    Windows 8&10

    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.
      My ComputerSystem Spec
  9.    05 Sep 2017 #9
    Join Date : Oct 2015
    Posts : 2,043
    Windows 10 Pro X64

    Hi,

    Indeed. It did not get there all by itself. It might have been created because Windows no longer booted up.

    Cheers,
      My ComputersSystem Spec
  10.    05 Sep 2017 #10
    Join Date : Jul 2015
    Posts : 3,730
    10 Pro

    I've got loads with blank descriptions or meaningless descriptions. It is obviously motherboard specific and presumably there is some upper limit but if it is working you could just leave it.

    Code:
    PS C:\Windows\system32> bcdedit /enum firmware
    
    Firmware Boot Manager
    ---------------------
    identifier              {fwbootmgr}
    displayorder            {bootmgr}
                            {3be0327d-176e-11e7-b4ff-c30418e09fae}
                            {3be03263-176e-11e7-b4ff-c30418e09fae}
                            {3be03263-176e-11e7-b4ff-c30418e09fae}
    timeout                 5
    
    Windows Boot Manager
    --------------------
    identifier              {bootmgr}
    device                  partition=\Device\HarddiskVolume2
    path                    \EFI\refind\refind_x64.efi
    description             rEFInd
    locale                  en-US
    inherit                 {globalsettings}
    flightsigning           Yes
    default                 {current}
    resumeobject            {3be0327f-176e-11e7-b4ff-c30418e09fae}
    displayorder            {current}
    toolsdisplayorder       {memdiag}
    timeout                 30
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be03263-176e-11e7-b4ff-c30418e09fae}
    description             Boot Camp
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be03264-176e-11e7-b4ff-c30418e09fae}
    description
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be03265-176e-11e7-b4ff-c30418e09fae}
    path                    \EFI\BOOT\BOOTX64.efi
    description
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be03266-176e-11e7-b4ff-c30418e09fae}
    description             Mac OS X
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be03267-176e-11e7-b4ff-c30418e09fae}
    description
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be03268-176e-11e7-b4ff-c30418e09fae}
    path                    \EFI\BOOT\BOOTX64.efi
    description
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be03269-176e-11e7-b4ff-c30418e09fae}
    description             Mac OS X
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be0326a-176e-11e7-b4ff-c30418e09fae}
    description             Mac OS X
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be0326b-176e-11e7-b4ff-c30418e09fae}
    description
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be0326c-176e-11e7-b4ff-c30418e09fae}
    description             Mac OS X
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be0326d-176e-11e7-b4ff-c30418e09fae}
    description
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be0326e-176e-11e7-b4ff-c30418e09fae}
    path                    \EFI\BOOT\BOOTX64.efi
    description
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be0326f-176e-11e7-b4ff-c30418e09fae}
    description             Mac OS X
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be03270-176e-11e7-b4ff-c30418e09fae}
    description
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be03271-176e-11e7-b4ff-c30418e09fae}
    path                    \EFI\BOOT\BOOTX64.efi
    description
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be03272-176e-11e7-b4ff-c30418e09fae}
    description             Mac OS X
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be03273-176e-11e7-b4ff-c30418e09fae}
    description             Mac OS X
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be03274-176e-11e7-b4ff-c30418e09fae}
    description
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be03275-176e-11e7-b4ff-c30418e09fae}
    path                    \EFI\BOOT\BOOTX64.efi
    description
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be03276-176e-11e7-b4ff-c30418e09fae}
    description             Mac OS X
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be03277-176e-11e7-b4ff-c30418e09fae}
    description
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be03278-176e-11e7-b4ff-c30418e09fae}
    description             Mac OS X
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be03279-176e-11e7-b4ff-c30418e09fae}
    description
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be0327a-176e-11e7-b4ff-c30418e09fae}
    path                    \EFI\BOOT\BOOTX64.efi
    description
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be0327b-176e-11e7-b4ff-c30418e09fae}
    description             Mac OS X
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be0327c-176e-11e7-b4ff-c30418e09fae}
    description             Mac OS X
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be0327d-176e-11e7-b4ff-c30418e09fae}
    path                    \EFI\refind\refind_x64.efi
    description             Mac OS X
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {3be0327e-176e-11e7-b4ff-c30418e09fae}
    description
    PS C:\Windows\system32>
    According to here you can delete them all and they will be repopulated
    On computers where the EFI firmware initializes NVRAM entries for local devices, you may delete all GUID entries if desired. Do not delete the entry for {bootmgr}
    Remove Duplicate Firmware Objects in BCD and NVRAM
      My ComputerSystem Spec

 
Page 1 of 2 12 LastLast


Similar Threads
Thread Forum
Unknown USB Device (Device Descriptor Request Failed)
After installing Windows 10 anniversary update, I get the following error in the device manger: Unknown USB Device (Device Descriptor Request Failed) Tried uninstalling and restarting PC. Reinstalled Windows made from media tool. Nothing fixed...
Drivers and Hardware
Creators Update Broke My XBOX 360 Headset Device (Unknown Device)
I can no longer use the mic that came with my Xbox 360 wired controller on my Windows 10 PC after I upgraded to the Creators Update a few days ago. In the Device Manager it is listed as 'Unknown device' and if I try to 'Upgrade Drivers' then I get...
Drivers and Hardware
Solved unknown device in device manager
Hey guys , I thought I might ask here as I don't seems to be getting a solution on Dells forum . Unknown device ACPI\CPL0002\2&DABA3FF&0 is showing up with a clean install of windows 10 pro on a dell alienware 13 ,2015 model . Any ideas what...
Drivers and Hardware
Solved Unknown USB Device (device descriptor request failed)
Fresh install of Windows 10 and the last driver I need to sort out is the above. I believe it is my powered USB 3 hub to which I plug in my keyboard and mouse. Technically it is working but I don't like seeing yellow triangles on devices. So...
Drivers and Hardware
Solved Unknown USB Device ( Device Descriptior Request Failed )
Greetings folks I have a problem that bugs me for years, I never intentionally solved it, sometimes those errors disappears and all USB ports work fine, sometimes they do not. So anyone can help me please, it would be great. Some of my ports...
Drivers and Hardware
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 08:20.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums