1 Reply Latest reply on Feb 6, 2018 10:47 PM by N.Scott.Pearson

    Downgrade BIOS NUC5I5RYK to 365

    nadotu

      After I'd updated the BIOS of my NUC5i5RYK to Ver. 368 (which was silenty withdrawn meanwhile from downloads) I faced several problems:

       

       

      Performance went significantly down, booting took much longer an I encountered constant weird errors with Windows10 according to 'Visual C++ redistributable', error code '0x000000c' among other irregular error codes. Several older Games do not run anymore or crash constantly.

       

       

      As I've an identical NUC5i5RYK with older BIOS V.365 which did not have this issues I assume the cause is the newer BIOS.

      These NUCs are totally identically equipped! Both have 16GB HyperX RAM and the same M2-SSD. The only differrence is the BIOS Version!

       

       

      But to my very irritation I'am not able to downgrade the BIOS to a version lower than V.367 anymore due to 'security reasons'.

      With the latest downgradeable V.367 the issues persist.

       

       

      I also interchanged RAM and M.2-SSD from one nuc to the other with the same result: One wiht BIOS V.365 works flawless, the one with now V.367 suffers from constant application crashes under Windows10.

       

       

      So please Intel - please let me just downgrade my NUC to the last working BIOS V.365 again!

       

       

      No, I don't want to complete endless questionnaires or spend hours on running diagnostic tools - just let me downgrade the BIOS again!

       

       

      I really do not care about obscure 'security reasons' as these NUCs do not even have connetion to the internet when running windows!

      I just want them back in the usable condition like before this BIOS V.367!

      Thank you!

        • 1. Re: Downgrade BIOS NUC5I5RYK to 365
          N.Scott.Pearson

          I am sorry, but once you are at BIOS 367, you simply cannot downgrade. This is because changes were made in the Management Engine firmware in BIOS 367 to mitigate the INTEL-SA-00086 security vulnerabilities (for more information, see here: INTEL-SA-00086 Advisory). Now, once a security update is made to the Management Engine firmware, it will not allow downgrades to any previous version. This is a design feature of the Management Engine that simply cannot be circumvented. I am sorry, but you will just have to wait for a new BIOS update to be made available.

           

          The BIOS was withdrawn because of instabilities in the microcode updates made for the SpectreB vulnerability (for more information, see here: Facts about The New Security Research Findings and Intel Products and here: INTEL-SA-00088 Advisory). Unfortunately, this instability manifested worst in the microcode for the Haswell (4th generation Core) and Broadwell (5th generation Core) processors. You have already encountered and described it's instabilities fairly well.

           

          Since the BIOS withdrawal was done, Intel has root-caused the microcode issue, made the appropriate changes to the various microcode releases and is in the process of validating these changes. Once the validation is complete (and presuming it is satisfactory), the microcode will be released to board manufacturers. They, in turn, will be responsible for including the appropriate microcode releases into their product BIOSs and releasing them to their customers. Intel's NUC team will be similarly responsible for doing this for the NUC products and also for the older Intel Desktop Board products. They will publish their schedules for delivery of the various BIOS updates to these locations:

           

             INTEL-SA-00088 Schedule for Intel NUC, Compute Stick and Compute Card

             INTEL-SA-00088 Schedule for Intel Desktop Boards

           

          Unfortunately, these schedules cannot be set until the microcode is made available (that's why they are blank right now). All I can say is, watch these sites for schedule updates.

           

          I wish I had a better answer, but it is what it is. Don't shoot the messenger; I am retired and a volunteer here.

          ...S