Difference between revisions of "IPC3 ME Firmware Update"

From fit-PC wiki
Jump to: navigation, search
(Created page with "The following procedure suitable IPC3 computers equipped with Intel Core gen 7 (KabyLake) processors.<br> == Security fix for INTEL-SA-00086 vulnerability == # Download Link...")   (change visibility)
 
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
The following procedure suitable IPC3 computers equipped with Intel Core gen 7 (KabyLake) processors.<br>
+
The following procedure is applicable for IPC3 computers equipped with Intel Core gen 7 (KabyLake) processors.<br>
  
 
== Security fix for INTEL-SA-00086 vulnerability ==
 
== Security fix for INTEL-SA-00086 vulnerability ==
# Download Link [https://fit-iot.com/support/intelSA00086/IPC3(Corporate5MB)/ME11.8.50.3425_for_IPC3.zip/ SA-00086 IPC3 Fix] - MD5:0DB0F9A094D26D3A2973EE85165FEE1B  
+
# Download Link [https://fit-iot.com/support/intelSA00086/IPC3(Corporate5MB)/ME11.8.50.3425_for_IPC3.zip SA-00086 IPC3 Fix] - MD5:0DB0F9A094D26D3A2973EE85165FEE1B  
 
# Extract archive content to USB flash formatted FAT32.
 
# Extract archive content to USB flash formatted FAT32.
 
# Insert USB Flash into IPC3 and boot "UEFI: Build-in EFI Shell" option from boot menu (press F7 during IPC3 power-up).
 
# Insert USB Flash into IPC3 and boot "UEFI: Build-in EFI Shell" option from boot menu (press F7 during IPC3 power-up).

Latest revision as of 13:56, 8 October 2018

The following procedure is applicable for IPC3 computers equipped with Intel Core gen 7 (KabyLake) processors.

Security fix for INTEL-SA-00086 vulnerability

  1. Download Link SA-00086 IPC3 Fix - MD5:0DB0F9A094D26D3A2973EE85165FEE1B
  2. Extract archive content to USB flash formatted FAT32.
  3. Insert USB Flash into IPC3 and boot "UEFI: Build-in EFI Shell" option from boot menu (press F7 during IPC3 power-up).
  4. Automated script will process ME update to version ME 11.8.50.3425.
For Intel's SA-00086 Detection tool [Intel's SA-00086 detection tool: click here
For more information please refer to Intel's security advisory: / click here