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?
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,
Last edited by fdegrove; 05 Sep 2017 at 11:17.
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,
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.
According to here you can delete them all and they will be repopulatedCode: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>Remove Duplicate Firmware Objects in BCD and NVRAMOn 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}
Quote