Is BIOS Update [HNKBLi70.86A] safe to upgrade?

[CJian29]

BIOS Update [HNKBLi70.86A]

Description: This download record provides options for updating the BIOS of Intel® NUC Kits NUC8i7HNK and NUC8i7HVK.

Version: 0063

Release date: September 3, 2020

Size: 7.42 MB

New Fixes/Features:
• Updated ME FW version to 11.8.79.3722
• Updated BIOS code for security fixes.
• Fixed issue where “Native ACPI OS PCIe Support can’t be enabled
in BIOS if Thunderbolt Controller is enabled”.
• Fixed issue with SGX driver v2.7.101.2 causing “System BSoD
during restart Windows 10 20H1 (2004)”.
• Fixed issue to able to read storage Admin Passwords created using
older BIOS versions.
• Added feature to be able to set BIOS passwords on (2) storage
units installed independently.
• Fixed issue when S4/S5 settings were not saved in BIOS.
• Fixed issue where “Set default Family Name” for Microsoft
request.
• Fixed issue to display “Energy star logo”.
• Fixed issue to display “Press F12 for network service boot” in
UEFI.

[PRyan4]

Upgraded 63 here no issues yet, but I had no issues with 60 and 61.

Paul

[CJian29]

You are so lucky.

Last time, I upgrade to 0061 but got https://community.intel.com/t5/Intel-NUCs/NUC8i7HVK-got-BIOS-update-from-IDA-but-stuck-to-boot-after.... 

So I need to be careful with the BIOS upgrade this time.

[dxtyh]

I had issues with 0060, had to run the power button menu BIOS recovery.

Just upgraded to 0063 and ran into the same problems again, had to do another BIOS recovery to 0059.

[powerarmour]

BIOS 0063 is working fine for me so far on my 8i7HVK with Linux, though I haven't booted into Windows yet to test the SGX driver fix that apparently previously caused the BSoD's with the 0061 BIOS (though I'm sure Win10's v2004 is as much to blame here, as it's a buggy mess of an update...).

Reading between the lines it might be a good idea disabling SGX in the BIOS anyway (rather than the 'Software Controlled' default) if you don't need/require that functionality.

https://en.wikipedia.org/wiki/Software_Guard_Extensions

[Alan_J_T]

Worked for me but I also had no problems with Version 61

[GregK]

Nope it Isn't
I have problem to boot with NVMe drive (Seagate Firecuda 520) on Hades Canyon...
Just did Bios Recovery do 059 now it works fine...
Quo Vadis Intel?! it's 3rd release in a row making people angry...

[BHarr8]

0063 loaded without issue.

[beninoz]

What drives do you have?

[BHarr8]

2 800P in RAID 0. Intel drives so no surprise that everything works. 0060 and 0061 also worked just fine.

[beninoz]

I'm running Crucial P1s, and had issues with version 61. I fear version 63 has the same issues and was wondering if anybody with these drives has successfully updated. 

[n_scott_pearson]

I don't have any myself, but I can tell you that Intel specifically validated with P1's before releasing BIOS 63 as this was an often-cited drive for the BIOS 60-62 issues.

...S

[beninoz]

Where can I find that information?

[powerarmour]

Still no issues for me with BIOS 0063, and that's now after switching between Linux/Windows over the weekend and rebooting a ton of times with different drives.

Seems pretty stable so far and I prefer the additional Tau options in the power profiles too with this BIOS, nice work. 

[beninoz]

I can confirm this BIOS works with Crucial P1s. Before flashing, I made sure widows 10 had all available updates, then I took the leap. I booted straight back into windows, which didn't happen with version 61. so far so good. I will report back if I get any BSOD. 

[n_scott_pearson]

Where can you find what information?

[GregK]

Reboot your nuc couple times, please.
Mine boots 1/2 reboots , second half i am getting message about: No Bootable Devices Found.

[PRyan4]

Hi GregK
Try resetting bios to defaults may fix that error.

[GregK]

I did.
There is a bios bug started with 0060 where some NVMe drives stoped working properly - Seagate FireCUDA was working with this release and 0061, 0063 it stopped working.
What i found during investigation, is that even embedded efi shell have problem access this drive.
executing ls FS0:Microsoft/Boot in efi shell shows information about Media being changed....
Downgrade (with bios recovery procedure) to 0059/0060/0061 solves issue, and HadesCanyon boots every time.

[rana966]

What hard Drive Brand do you have? I have Western Digital and also had the same issue with 60 and 61.