1 Reply Latest reply on Jul 9, 2017 8:41 AM by N.Scott.Pearson

    [ISSUE] NUC5i3RYH updating to any version after 0356 is not successful - unsupported legacy bios OR update successful but effectively not installed

    alQamar

      Scenario

      I have 3 of same NUCs and one of them is freaking out.

       

      I have already called the Intel support and the operator gave me instructions how to use the F7 method and also how to recover the BIOS (pushbutton > F4). The F7 method won't update either.

      Model: NUC5i3RYH

      Current BIOS: RYBDWi35.86A.0356.2016.0506.1355, 06.05.2016

      BIOS protection jumper is set to: 1-2

       

       

      Behaviour

      when trying to install RYBDWi35.86A.0362.EB after reboot it says your BIOS was successfully updated, however it did not even try to update on boot. No error message.

      when trying to install RYBDWi35.86A.0358.EB after reboot it says unsupported legacy BIOS

      when trying to install 0358.bio, via F7, no error message on boot, won't update

      when trying to install 0362.bio, via F7, no error message on boot, won't update

       

      when trying to recover BIOS using F4 with 0356.bio this is successful with no errors.

       

      Expected behaviour

      Update to subsequent version 0358 or later should work using F7 method or Windows Installer

       

       

      Currently there is no way to force any upgrade from 0356 to a later version, if there will be no solution I have to consider to return the device (09/2015)

       

      Solutions from cant update BIOS: unsupported legacy BIOS and

      BIOS-Wiederherstellung-Update-Anleitungen für Intel® NUC

       

      were all tested and solve the issue.

       

      bios.PNG

        • 1. Re: [ISSUE] NUC5i3RYH updating to any version after 0356 is not successful - unsupported legacy bios OR update successful but effectively not installed
          N.Scott.Pearson

          Karl,

           

          I do not recommend using the EBU method for BIOS update; stick with the F7 method or (always better) the Recovery Method. The EBU method relies on a trick to reboot the PC without memory being overwritten but, in certain circumstances, Windows 10 can be in a state where this doesn't work. In these cases, the BIOS does not "see" the update to install after the reboot and it just continues on into the Windows restart. Then, to make matters worse, the status tool incorrectly determines that the installation either completed successfully or failed for a completely wrong reason. It would be nice if Intel fixed this issue; it is so much simpler (and faster!) just running an .EXE from within Windows (no flash stick, no waiting to catch the short window for hitting the F7 key, etc.). Unfortunately, this may prove impossible with all dicking around that Microsoft is doing with Windows 10...

           

          Intel's BIOS update method requires the update image be placed into memory and the system rebooted. After the reboot, the BIOS, in a fully-secured state, sees that the image is present in memory, validates its integrity and then installs it. This process can fail if the NUC is having memory initialization problems. When the BIOS initializes memory, if the memory proves incapable of running at the configured (wait-states, etc.) settings, the memory will hang the system. The Recovery Timer reawakens the system and the BIOS can then retry the initialization and/or at a lowered settings level. If this is successful, the system can continue with POST - and this whole process happens without you seeings any visible signs. The problem is that the BIOS update that was in process will have been forgotten and there will be no indications that the process failed. If you don't see the BIOS installation progress screen, you will know that you need to try the update again. If, like me, you turn away and do something else while the process is being completed and thus miss seeing the progress screen, check the version string in the BIOS to see if it actually updated.

           

          Note that I am NOT saying you have a memory problem; I am just pointing out possibilities here...

          ...S