Where OEM Activation Key Bin File Name is used to specify path/filename of the OEM activation key file with extension. JBC Don't Check AC adapter and battery K1 Program the non-critical block for Splash Screen Logo update This is what the utility 'iFlashVEfi64.efi' can do from inside an EFI shell: I purchased a new 10 series NUC and was trying to see what my activation options were. Intel seems to have a new utility 'iFlashV. So for anyone that gets errors on NUC regarding EFI - make sure you're using an older Windows build, did not try 8.1 / 7 but I would think it would work. Tested NUC7 (i3), NUC6 (i5) and NUC5 (i7) latest BIOSes from this month. After erase/insert the new 2.5 SLIC would be seen fine in Windows 1809/1903. But on Windows 1809/1903 on other NUCs the utility did not work (the SLIC was naturally not used there just added it in the past to see whether it worked).īooting off Server 2016 (1607) install on these NUCs did work - so something must have changed in 'recent' Windows builds with regard to EFI variable manipulation which is why the utility would fail. What I found is that on Server 2016 NUC the utility (X007) worked fine to get status/erase/insert new SLIC. No amount of changing date back, BIOS settings, and so on helped. After over 1 year since I used this utility on my NUCs (to add SLIC 2.4) I thought I would update to 2.5 and found the utilities did not work (same error as posted before) on some NUCs.
