I did also web research and founded possible solution for the problem you have described: After installing creator update, NUC failed with 0x80070057 on Win - Microsoft Community
You will need to use Intel Integrator Toolkit to change in Bios system manufacturer and the system product.
The all process is well described in the referenced post.
And finally may be Intel will update bios to meet Windows 10 requirements?
Hope this will fix this error.
2 of 2 people found this helpful
This did fix the issues. The NUC is now is activated and can run Windows Updates (again). I'm going to elaborate a little on the solution, just so folks reading here can get an idea of what this entails.
1) Download the Intel Integrator Toolkit. At the time of this writing, the current version was 6.1.6.
2) Unzip the package and Copy the 'ITK6.efi' file to a FAT32 formatted USB Flash Drive. For ease of typing and getting the following commands correct the first time, I put the two commands needed in a .txt file and named it 'commands.nsh'. Those commands, for me, were:
ITK6.efi -s -t system -f manufacturer -v "Intel Corporation"
ITK6.efi -s -t system -f product -v DN2820FYKH
This .nsh file runs like a batch file in the EFI Shell environment. I copied this .nsh file I made to the USB Flash Drive, too. Put the USB Flash Drive in the NUC (if you were doing this on a different machine like I was).
3) Reboot the NUC and hit F2 to get into the BIOS Settings. In my case, the NUC runs the BIOS default settings, so I had to dig through the Boot Configuration stuff and find the switch to enable the EFI Shell as a boot option. It is OFF by default. Turn it ON, save and exit.
4) At the next boot cycle, choose F10 for the boot options to appear. You should see the EFI Shell as a choice. Pick it.
5) You'll be presented with a funny Yellow and White text, DOS-like environment. You need to navigate to the USB Flash Drive. For me, this showed up as 'fs4', so at the command prompt I typed 'fs4:' to change to that drive. I then typed 'ls' to list the files and make sure I was on the USB Stick. Once confirmed, I typed the name of the .nsh file and it executed the two stored commands - both returned an acknowledgement that they executed successfully. Then I typed 'exit' to get out of the EFI Shell, and the unit rebooted.
6) Once back in Windows 10, I ran Windows Update successfully, and I could see the OS was Activated.
It would save customers a lot of effort if Intel would update the BIOS to fix this. In my opinion, this fix goes beyond the comfort level of an average user.
I have re-created this and have opened a bug fix request.
I'll let you know when I have a status update.
1 of 1 people found this helpful
Due to this model being end of life, this won't be fixed, but I will post these instructions as a sticky on the appropriate page. Thanks for the heads up JamesU.