Try update your bios using bios recovery method: BIOS Recovery Update Instructions for Intel® NUC
As you can see there are two ways to execute bios recovery:
- Power Button Menu
- Security jumper removed
In both methods the USB with the .bio file shall be inserted into USB slot.
1. Power Button Menu
1.1 Press power Button about 3 seconds (now more than 4 seconds). Release the power button after you hear 3 beeps and/or the blue led changes color to orange.
1.3 NUC will reboot into Power Button menu.
1.4 Press F4 to start the recovery process.
2. Security jumper removed.
2.1 Open the bottom NUC cover and remove the Security Jumper
2.2 Power ON the NUC. The recovery process will start automatically.
2.3 After completion, power OFF the NUC and replace the security jumper.
Hope this helps
OK so initially this fails the exact same way.
Following these instructions
I get to step 6, but then step 7 doesn't appear, it just reboots again and I see the bootloader for the installed OS.
The USB stick in question uses GPT scheme, not MBR. sgdisk reports the following info for that partition:
[chris@f26h ~]$ sudo sgdisk -i 1 /dev/sda
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 89814FF6-DB37-4641-B628-074E001864E4
First sector: 2048 (at 1024.0 KiB)
Last sector: 31277022 (at 14.9 GiB)
Partition size: 31274975 sectors (14.9 GiB)
Attribute flags: 0000000000000000
Partition name: 'Microsoft basic data'
The format is FAT32. This stick had been recently partitioned and formatted just for this firmware update. And the F7 update method in fact shows the firmware file on the stick.
Anyway, I went to a different stick MBR partitioned, and FAT32 formatted, with the same file saved on it. And the F4 method worked. I didn't try the F7 method first; and I don't have an easy way to test if there's a regression that makes either F4 or F7 methods dislike GPT partitioned USB sticks for flashing firmware, or if there's some other explanation.
Was the stick formatted from Linux? If so, there's your problem. Linux doesn't do FAT32, it does VFAT.
'mkdosfs -F 32' certainly is FAT32, and the EFI System partition on this NUC is created with that command, and the firmware finds the bootloader and loads it just fine. So that's definitely not the problem.
This message was posted on behalf of Intel Corporation
It's a strange behavior, from our end we have not seen cases similar like the one you are reporting. We always format in FAT32 from Windows, and the F7 method works fine.
I am glad to hear you were able to find a fix, and thank you for sharing it with the community.