I had no problems when I disabled Bluetooth, Infrared, and other security sensitive settings BEFORE OS install. However, NUC booted to a black screen when I attempted to deselect Virtualization Technology setting AFTER installing the OS. This leads me to believe that Intel Virtual BIOS is not easily modified AFTER OS install without causing significant problems to the bootloader.
My bios settings for the boot priority are:
UEFI: SATA: PORT 2: Windows Boot Manager: PAR 1: OS Bootloader
SATA: Port 2: Samsung SSD 850 EVO M.2 120GB: Part 0: Boot drive
LAN: IBA CL Slot 00FE v0104
You may well be right about the Visual BIOS being sensitive to changes after OS install. At least in the interim my workaround is to disable the items in the OS.
I've run into the exact same problem as the OP: I had disabled Bluetooth and IR in the firmware config and experienced the hang at the "F2/F7/F10" splash screen. Since I intend to roll a lot of these NUCs out to customers, I took some time to define the problem a little further:
My Hardware Build:
- Intel NUC6i5SYK (NUC6i5SYB board) BIOS0028, all latest drivers from Intel website as of 2/18/2016
- Kingston 8GB RAM (p/n: KVR21S15D8/8)
- Intel 535 Series M.2 180GB MLC SSD (p/n: SSDSCKJW180H601)
My general (final) firmware config:
- UEFI boot only; BIOS compatibility disabled
- Fast Boot: disabled
- Failsafe Watchdog: enabled
- All boot devices disabled except: Windows partition, PXE Network Boot, Optical drive
- Boot order is: 1) Windows partition, 2) Optical drive, 3) PXE
- Secure Boot was not enabled during any of my tests
- Audio, HDMI/DP Audio: both enabled
- LAN, WLAN: both enabled
- NFC, SD Card, IR: all disabled
- Intel VT and VT-d: both enabled
- I also played a lot with most of the firmware settings, but nothing seemed to affect the hang other than enabling/disabling BT. Caveat, though: I didn't explicitly test each of the settings I played with for the hang problem. It wasn't practical to test every possible combination of settings, of course.
My installed operating system:
- Very clean Windows 10 Pro 64-bit install plus all latest drivers from Intel's website as of 2/18/2016.
- If you wait long enough, it will eventually boot into Windows (very consistently ~17.25 minutes from "F2/F7/F10" to "Windows" on my test NUC).
- It's the Bluetooth setting, specifically. Disabling BT in the firmware config will cause the hang. Enabling BT allows the boot to proceed normally.
- Neither disabling BT in Windows Device Manager nor uninstalling the Windows drivers affects the boot hang. It's only the firmware config setting that affects it.
- With BT disabled in the firmware and Fast Boot enabled, the Windows logo will actually get displayed and it'll hang there for the ~17.25 minutes before continuing.
- It's not the firmware itself that's hanging. It's the Windows operating system. Windows is getting stuck REALLY early in its boot process. It hangs earlier than the point at which it displays the little spinning circle, which happens pretty immediately during a normal boot. But it's actually launching the boot loader from the SSD at this point. So the implication is that it's the Windows operating system that's hanging up because of something it doesn't like about the firmware. I tested this theory by booting a Clonezilla boot CD (the only UEFI bootable CD I happened to have handy). It booted without the ~17 minute delay. So the firmware itself isn't hanging. It's Windows. (But that doesn't necessarily mean that it's Microsoft's fault.)
Regardless of what the root cause of the hang or what the actual solution is, the work-around seems to be to leave Bluetooth enabled in the firmware and if you must disable it for a Windows OS, do it in Windows Device Manager.
Final note: I've already spent hours on this. I'm not going any further. But if someone else wants to pick up the mantle, perhaps some Windows debug/troubleshooting could yield some more info. Might be interesting to know what Windows is doing when it hangs. And why ~17.25 minutes?
I tested this NUC with the latest BIOS version 0033 and I am not getting any BSOD. I have tested the NUC with Windows® 10 64bit.
Latest BIOS version: 0033
I have also the same problem as you.
When I disable Bluetooth in BIOS, I Have the following message during the boot of the NUC (Just before windows starts to load) :
BIOS has detected unsuccessful POST attemp(s).
Possible causes include recent hardware changes.
Performance options or recent hardware change.
Press 'Y' to enter setup or N, to cancel, etc .....
If Bluetooth stays enabled, no problem, I already try different BIOS Version "24, 28, 33 and 36" and the issue was always happening.
I also ask to Intel to perform an warranty return, they accepted and I still have this problem with the new NUC.
So I'm wondering if you resolved your issue ?
I have lots of the options disabled in the BIOS - Bluetooth being one of them.
I think my install went something like this - BIOS defaults - Install WIndows 10 off UEFI USB stick - Install all drivers - Decided to disable things I am not using in the BIOS, as the NUC is mounted behind the TV - Disabled options in the BIOS (Legacy Boot, Audio, Bluetooth, LAN, SD Card, NFC, IR, Charging Port - Booted into Windows and uninstalled from Programs and Features this components I was not using.
This message was posted on behalf of Intel Corporation
There is a new BIOS version: 0039 Let us know how it works. Now, it is better to keep UEFI and Legacy Boot options enable. 6gen NUCs are new but there are many old devices in the market that will not work with UEFI.