No win10 boot after firmware update KY0071.bio Skull Canyon NUC6i7KYK

[skitterlad]

NUC6i7KYK

I have 5 of these units. The fans have been breaking on me. I got one replacement from intel, it took 6 months but it worked.

I updated my bios by getting a file from intel KY0071.bio and putting it on a USB stick. booting up the computer F2, then update bios F7 choosing the file.

I restarted my computer, but I get "a bootable device has not been detected" or sometimes I would get a blinking cursor. I now have this problem on two computers with the above name.

I've tried changing jumper settings, moving SATA drive to other bay, toggling from Legacy to UFFI, moving location of RAM module. no luck. I can boot off a USB installation for windows 10 to load up, and I could then choose the SATA drive.  The SATA drive boots well on my other NUC with same exact bios settings.

What am I missing?

[AlHill]

I have the same nuc, and bios 0071, and no boot problems with any of the W10 versions, including 20H2.

[skitterlad]

I have another two units NUC6i7KYK with the same KY0071.bio firmware without issues.

I have one 8GB module, and added another 2GB module after the firmware change. The 2GB module may have changed something. I removed the 2gb DIMM and moved the 8GB around to reset it, but it didn't boot. 

Legacy shows no boot drive and UEFI shows the SATA drive. both have checkmarks.

I tried different combinations in bios settings, and even went back to a different version 68 to see if that would reset things.

The SATA drive boots fine in other units same 71 bios. 

[skitterlad]

When I disable legacy boot, it gives me the message, "no boot drive detected" when I enable legacy , then I get the blinking cursor that stays like that for ever.

I can see the drive as a boot ready drive in bios when legacy is checked.

I do not see the SATA m.2 drive for UEFI in bios.

How do I get the SATA drive to show up as a bootable drive for UEFI?

[skitterlad]

"reboot and select proper boot device" after waiting a while when cursor blinks.

how do I get UEFI to accept this boot device? or how do I boot in Legacy even when Legacy shows my data drive in the boot list?

[n_scott_pearson]

Here's the process:

1. Build a new USB flash drive using the Microsoft Media Creation Tool. If you download the latest version of this tool (from here: https://www.microsoft.com/en-us/software-download/windows10), it will build media to install 20H2.
2. Insert USB flash drive into system, power on and then open the boot selection menu by hitting F10. Select and boot from the entry for the USB Flash drive that starts with "UEFI:...".
3. When you get to the step in the Windows installation process where you specify what partition to install Windows 10 to, delete *all* partitions that exist on the M.2 drive and then tell the installer to install to the unused space entry on this drive (which should encompass the entire drive at this point).
4. Continue with Windows 10 install.

It's that simple. By deleting all partitions, you let the installer create the GPT partition table necessary for UEFI boot.

...S

[skitterlad]

update, it seems that my bios update on the other computers didn't actually go through. so legacy mode boot for windows 10 works for bios 63. but when I put the same SATA m.2 drive into a bios version 71 it doesn't boot. neither shows up UEFI boot drive as available, only legacy boot drive is available and it lists the name there.

[jboggin]

This should be obvious, but, this also applies to Linux.

Upgrading BIOS to fix a USB bug has caused Linux to fail to operate due to the lack of legacy boot functionality.  Boot devices are found, flashing cursor is all that remains. 

USB drives with installation media will only boot in their UEFI forms.  Upon boot, of course, I can mount the drives -- but, I'm stuck with MBR partitions and am not pleased at the prospect of having to backup these systems and riskily change the partition type.

Rather, this is a bug in the bios that should be fixed.

[skitterlad · Accepted solution]

• mbr2gpt.exe /convert /allowfullOS
• I had to convert my mbr to gpt
• New bios version 71 does not allow legacy boot anymore, at least for me
• once I converted to gpt, then UEFI detected the SATA m.2 as a boot drive, and windows 10 loaded

https://www.wintips.org/how-to-change-legacy-to-uefi-without-reinstall-windows-10/

Thats the site I used to find out. and no need to d/l anything , its all windows commands.

i used another nuc with older firmware to load windows 10, then run this in command prompt, and presto! 

[jboggin]

This really isn't a solution...  it's a work-around.

The solution would have been a fix to get the MBR partitions to boot the way they once had.

[AlHill]

No, UEFI boot and GPT is the norm in today's world.  Trying to stay on legacy and mbr is not going to help you.  Rather, it will cause you constant issues.

Doc (not an Intel employee or contractor)