Windows 10: 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:






What it is this unknown entry?
Can i fix it?

:)

 

Nokia servers down on sunday?

It has been down all day. Those with a phone that no longer boots for some unknown reason cannot restore it to working order for some other unknown reason. I can't find a status page or anywhere to report the problem. It is pretty poor support for their
customers.

 

Since "updating" to windows 10, my Linx 10 tablet doesn't see the inbuilt cameras.

I've done the clean boot and I now have a unknown device in my Device Manager, which I'm hoping maybe linked to my in-built cameras. But when I go to update it, it says 'Windows was unable to install your unknown device'.

 

You can delete it. Looks like it is an entry to an EFI shell (kind of like command prompt for UEFI).

 

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

 

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

paste the identifier in after /delete

 

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.

 

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, *Wink

 

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.

 

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.

 

Hi,

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

Cheers, *Wink

 

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>[/quote] According to here you can delete them all and they will be repopulated

Remove Duplicate Firmware Objects in BCD and NVRAM

 

This is my bcedit:





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

 

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, *Wink

 

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