hello Intel customer support members,
iam IT-professional and i have a problem with my private NUC. We bought our NUC5I5RYH nearly 2,5 years ago with the following setup:
2x 8GB Crucial Ram-Kit ( CT2C8G3S160BMCEU )
1x Crucial 500GB MX200 M.2 SSD ( CT512M550SSD4 - latest firmware installed )
1x 2TB SAMSUNG 2,5" HDD ( HN-M201RAD)
In the first year, the NUC was running without any issues. I cant remember if there was an specific event which caused the following troubles. Maybe it was a bios update, maybe a reinstallation of win7 with a switch from GPT to MBR partitons or something else (both sounds plausible), but after ~1 year, the following described issues came up. Between year 1 and 2,5, i just ignored this issue and did a workaround by pressing F10 because of laziness. I just found muse to solve this issue in the last weeks.
The problem is, that the NUC wont boot Windows 10 from the ssd or the hdd if its installed with the following setting in the VisualBIOS: [UEFI BOOT unchecked / LEGACY BOOT checked]. If i install a fresh win10 from a clean and working USB stick under this condition, win10 will install with a MBR-partition. If the NUC restarts the first time during the install-process, it wont find the bootable drive with the MBR-partition and shows me a black screen with "no bootable device found"-message. Remember: i have the right boot order in the visual bios + its the same if i have online one of the both drives attached.
BUT 1: If i push F10 during POST-Screen, i can choose the drive with the MBR-partition manualy and it will boot if i select it! Its not a problem to end the install plus use the NUC day after day by pushing F10 during POST-Screens.
+ BUT 2: If i select [UEFI BOOT checked / LEGACY BOOT unchecked] and start a fresh installation of win10 and a GPT-partition again, it will (re)boot without any issues during the installation process and from day to day.
Again: It makes no difference if both or only one of the drives is attached. Its only a thing of UEFI or LEGACY settings. All other bios settings are default! Resetting to factory defaults or setting the jumper didnt solve the problem.
Please also note: Im pretty sure that this is a issue of the NUC5 and maybe other generations or its bios, its not problem of my exemplar. I can say this because i had a different problem* with the NUC-exemplar i bought 2,5years ago, so i opened a ticket and the result was a warranty exchange of the complete NUC just this week. Both, the old and the newly arrived exemplar came/comes with the exact same behavior.
* The additional problem was, that the old NUC was not able to save some bios settings (i.e. order of the drives under the LEGACY BOOT checkbox) plus i was not able to do bios updates anymore.
Pleas intel, fix this issue. Seems not to be a feature.
PS: I found some similar topics here:
Re: Nuc6i5syh F10 boot sequence non existent disk detected. <--- Please take look on post #10!!!!! Might be the reason