I recently got an NUC8i7HVK (Hades Canyon NUC).
In attempting to set it up, I encountered "A bootable device has not been detected." after disabling Secure Boot when attempting to boot a USB stick with an EFI partition on it.
The USB stick boots perfectly from a Lenovo and another USB stick formatted ISO (containing an Ubuntu live CD image) boots perfectly in the NUC8i7HVK.
It was only after considerable troubleshooting that I stumbled upon a rather odd suggestion to try which actually worked...
Splitting the USB stick's EFI partition in two and cloning the contents/boot flags from the EFI partition to the other half of the split, such that there are two identical EFI partitions proceeding the data partitions allowed the USB stick to boot.
As I don't understand why this is necessary, I'm curious if someone from Intel can explain why this EFI split/clone exercise is required to use bootable USB EFI sticks with NUC8i7HVK?
(FYI this was done on an April Bios and the Nov 29 NUC8i7HVK bios)
The bootable media was created on OSX.
Software used to create EFI bootloader was a program called "Unibeast". The USB stick created by this software EFI bootloader came up in a Lenovo laptop with no issue without modification.
Here is the suggestion I found to work around the issue:
After modifying per that suggestion (split + clone EFI partition), I was able to boot to the EFI bootloader on the USB stick.
I did however by accident was able to get the NUC to detect my USB UEFI bootable disk by plugging in 2 USB sticks.
This may sound silly but i've tried plugging one USB (UEFI) in front and one at the back. It detected my rear UEFI USB and I was able to boot Windows 10 - 1803 and 1809.
Not sure if this bug only exists in NUC Gen 8s but this is how i got around this issue.
Also my USB UEFI bootable disk works on other PCs like Dell, Lenovo without any issue booting it.
Try this and see if it works. I can try to take a video on this NUC bug and how it can be easily replicated.
I've founded there is some problem in booting from USB in NUC8i7HVK. If you insert your bootable USB into one of blue colored USB socket, it will not be detected in Boot Menu. However if you will use the front, orange USB socket, you will be able to boot from this USB after entering the Boot Menu.
This problem doesn't exist in other NUCs I've tested (NUC6i5SYH and NUC7i7DNHE), where the bootable USB is detectable in all USB sockets.
After reading the last post from Leonardo, I've checked again booting from USB on my NUC8i7HVK. I've have the same boot configuration like Leonardo described in his post. All USB ports are enabled in Bios. Also USB is enabled as a boot device. I'm using Windows 10 installation media USB (i.e. EFI). When the USB is inserted to the front blue USB port, it is not booting and is neither not recognised in Boot Menu (F10). However, if the same USB is inserted into front orange port or one of the blue ports on back panel, it is booting and it is detected in Boot Menu.
Leonardo, please check again, booting from front blue port.
My bios is updated to version 0053.
I do not have Kingston USB stick. Have only Sandisk Ultra USB: 16GB and 32GB. One media prepared using Microsoft Media Creation Tool and the other with Rufus. Both are not recognised in Boot Menu when installed in front blue port. Both are working good in all other ports, so there are OK in other NUCs. Both are recognised by Windows while installed in front blue port.
It is interesting if somebody else have this problem too.
Thanks for the note about orange @LeonWaksman
I'm experiencing the same issue on UEFI 2.2.25 - No blue USB ports show bootable USB storage devices.
Thought I was going crazy and somehow forgot how to make a bootable disk. Going to try a firmware update and see if there's any improvement on the rest of the ports.
Sorry should have said I was on BIOS version 53.
Updated to Version 64 and can no longer recreate the issue - All USB ports appear to support bootable USB devices again.