Page 1 of 2 1 2 LastLast
Results 1 to 10 of 18
  1. #1
    New ROGer Array Broheim PC Specs
    Broheim PC Specs
    MotherboardASUS Z170-A
    Processori7-6700K

    Join Date
    Jan 2018
    Reputation
    10
    Posts
    10

    ASUS Z170-A ME firmware update problem, Error 8719, no help from support

    I have a problem with updating vulnerable ME firmware on my Z170-A motherboard with BIOS 3504. First I updated ME Driver to the latest version 11.7.0.1040. MEUpdateTool (version - 2017/11/22) doesn't work - system is still vulnerable according to Intel-SA-00086 Detection Tool. Running "FWUpdLcl64.exe -f ME.bin" gives the same "Error 8719: Firmware update cannot be initiated because Local Firmware update is disabled". Tried solutions from forums, such as clean Windows 10 Pro x64 install, clearing CMOS, running FWUpdLcl64 from flash drive - do not work.

    This problem came up in another thread, with a solution to downgrade BIOS to old versions where Local Firmware update was enabled, see https://rog.asus.com/forum/showthread.php?97312-New-BIOS-Version-out-today-(11-09-17)-MH-VIII-Hero&p=698032#post695129
    (its a post by Kaelek on the 11th page). Searching the net regarding Error 8719 gives additional weight to the conclusion that this is usually a BIOS bug https://www.win-raid.com/t596f39-Int....html#msg22625.

    However, versions that I can downgrade to have Local Firmware update disabled (remember, Z170-A doesn't have USB BIOS flashback). I can't downgrade to 0901 for example that seems to solve the problem for MH VIII Hero.

    ASUS support was not helpful, since they suggested that this is a hardware error: "Obviously, ME firmware is damaged or cannot be updated due to hardware fault". Curious how guys with MH VIII Hero were able to solve it by downgrading BIOS. Support proposed that I send my motherboard to the service center of the shop where I purchased it, which is not local, so that way I will be without a working computer for at least a month. That I will not do, so it seems I just have to live with a vulnerable firmware.

    Did anyone with Z170-A and BIOS 3504 or one of the other 3xxx versions managed to update their ME firmware? Make sure it really was upgraded by running Intel-SA-00086 Detection Tool, because ASUS MEUpdateTool will not notify you of the Error 8719, and will look like update was successful when it was not.

    Anyone have any solution to this problem other that what support suggested?
    Last edited by Broheim; 01-12-2018 at 03:39 PM.

  2. #2
    New ROGer Array Broheim PC Specs
    Broheim PC Specs
    MotherboardASUS Z170-A
    Processori7-6700K

    Join Date
    Jan 2018
    Reputation
    10
    Posts
    10

    Similar error with MSI BIOS: https://forum-en.msi.com/index.php?topic=296123.0, https://www.msi.com/faq/notebook-2916 - "If you have "Error 8719:Firmware update cannot be initiated because Local Firmware update is disabled." after running the ME Update tool, there will be new BIOS release to solve the problem. New BIOS will be released right away once finished testing. Thank you for your understanding and patience.". So I do believe that this is a bug in recent versions of Z170-A BIOS and not a hardware fault or damaged firmware, as support suggests.

  3. #3
    ROG Enthusiast Array KSMerg PC Specs
    KSMerg PC Specs
    MotherboardASUS ROG Maximus IX Code
    ProcessorIntel Core i7-7700k
    Memory (part number)HiperX Predator HX433C16PB3K2/16
    Graphics Card #1ROG STRIX-GTX1080-A8G-GAMING
    MonitorAsus PG278Q
    Storage #1Samsung 970 PRO
    Storage #2950 PRO/960 PRO
    CPU CoolerNoctua NH-D15S
    CaseFractal Design Define C
    Power SupplyChieftec Nitro 2 (BPS-750C2)
    Keyboard Logitech G710+
    Mouse Logitech G402
    Headset/Speakers Microlab H11
    OS W10
    Network RouterAsus RT-AS87U

    Join Date
    Jul 2017
    Reputation
    10
    Posts
    32


  4. #4
    New ROGer Array Broheim PC Specs
    Broheim PC Specs
    MotherboardASUS Z170-A
    Processori7-6700K

    Join Date
    Jan 2018
    Reputation
    10
    Posts
    10

    Thanks for the link, KSMerg. Do you know if it fixes the issue? Is it production-ready? If so, why is it not listed on the BIOS & Firmware downloads page https://www.asus.com/us/Motherboards...HelpDesk_BIOS/?

  5. #5
    ROG Enthusiast Array KSMerg PC Specs
    KSMerg PC Specs
    MotherboardASUS ROG Maximus IX Code
    ProcessorIntel Core i7-7700k
    Memory (part number)HiperX Predator HX433C16PB3K2/16
    Graphics Card #1ROG STRIX-GTX1080-A8G-GAMING
    MonitorAsus PG278Q
    Storage #1Samsung 970 PRO
    Storage #2950 PRO/960 PRO
    CPU CoolerNoctua NH-D15S
    CaseFractal Design Define C
    Power SupplyChieftec Nitro 2 (BPS-750C2)
    Keyboard Logitech G710+
    Mouse Logitech G402
    Headset/Speakers Microlab H11
    OS W10
    Network RouterAsus RT-AS87U

    Join Date
    Jul 2017
    Reputation
    10
    Posts
    32

    Version 3703
    2018/01/128.09 MBytes
    Z170-A BIOS 3703
    Fixed SAMSUNG M.2 device issue.
    Fixed SanDisk M.2 device issue.
    Fixed AMD RADEON SSD device issue.
    Improved DRAM compatibility.
    Fixed SteelSeries keyboard issue.
    Updated Intel CPU microcode.

  6. #6
    New ROGer Array Broheim PC Specs
    Broheim PC Specs
    MotherboardASUS Z170-A
    Processori7-6700K

    Join Date
    Jan 2018
    Reputation
    10
    Posts
    10

    BIOS 3703 did not help

    So after 3703 appeared on ASUS Z170-A BIOS download page today, I updated to it - it still doesn't solve the problem with Error 8719. MEUpdateTool doesn't update ME firmware. Intel-SA-00086 Detection Tool reports that the system is vulnerable, same result with running FWUpdLcl64.exe -f ME.bin, Intel MEInfo 11.8.50.3425 also reports Local FWUpdate as Disabled.

    Is ASUS going to fix this problem or not? Or am I stuck with a vulnerable firmware on my motherboard, when it is a fairly recent model?

    Furthermore, they should fix their MEUpdateTool because it misleads users that their system was updated and, therefore, safe:
    Click image for larger version. 

Name:	MEUpdateToolError.jpg 
Views:	44 
Size:	39.5 KB 
ID:	70493
    When in fact, it wasn't updated and is still vulnerable:
    Click image for larger version. 

Name:	IntelTool - Copy.jpg 
Views:	2 
Size:	143.9 KB 
ID:	70494
    Last edited by Broheim; 01-13-2018 at 05:45 AM.

  7. #7
    ROG Enthusiast Array KSMerg PC Specs
    KSMerg PC Specs
    MotherboardASUS ROG Maximus IX Code
    ProcessorIntel Core i7-7700k
    Memory (part number)HiperX Predator HX433C16PB3K2/16
    Graphics Card #1ROG STRIX-GTX1080-A8G-GAMING
    MonitorAsus PG278Q
    Storage #1Samsung 970 PRO
    Storage #2950 PRO/960 PRO
    CPU CoolerNoctua NH-D15S
    CaseFractal Design Define C
    Power SupplyChieftec Nitro 2 (BPS-750C2)
    Keyboard Logitech G710+
    Mouse Logitech G402
    Headset/Speakers Microlab H11
    OS W10
    Network RouterAsus RT-AS87U

    Join Date
    Jul 2017
    Reputation
    10
    Posts
    32

    Click image for larger version. 

Name:	Screenshot_2.jpg 
Views:	2 
Size:	32.6 KB 
ID:	70498
    Try to update under "DOS / EFI / Linux"

  8. #8
    New ROGer Array Broheim PC Specs
    Broheim PC Specs
    MotherboardASUS Z170-A
    Processori7-6700K

    Join Date
    Jan 2018
    Reputation
    10
    Posts
    10

    Thanks, KSMerg. Do you mean run FWUpdLcl under linux with ME.bin from ASUS's MEUpdateTool? I tried that using FWUpdLcl from Intel CSME System Tools v11 r6 from win-raid.com under Ubuntu. It doesn't work, it gives the same error as the Windows version.

    As far as I understand, Local FWUpdate is simply a setting for ME to allow or disallow firmware updates, see for example this manual from Intel.
    Click image for larger version. 

Name:	LocalFWUpdate - Copy.jpg 
Views:	0 
Size:	59.9 KB 
ID:	70500
    So I don't think that running the same tool in a different OS will change anything.

    So I think the only way to update ME in my case is to somehow change this setting that is not available in Z170-A BIOS UI. Guys in another thread solved it by downgrading to old version using USB BIOS Flashback that had Local FWUpdate enabled. I don't have Flashback in Z170-A, and EZFlash prevents downgrade to pre-3xxx versions.

    So that means that ASUS should release a new BIOS version with Local FWUpdate enabled, as MSI did. Or at least provide a tool to enable Local FWUpdate.

  9. #9
    ROG Enthusiast Array KSMerg PC Specs
    KSMerg PC Specs
    MotherboardASUS ROG Maximus IX Code
    ProcessorIntel Core i7-7700k
    Memory (part number)HiperX Predator HX433C16PB3K2/16
    Graphics Card #1ROG STRIX-GTX1080-A8G-GAMING
    MonitorAsus PG278Q
    Storage #1Samsung 970 PRO
    Storage #2950 PRO/960 PRO
    CPU CoolerNoctua NH-D15S
    CaseFractal Design Define C
    Power SupplyChieftec Nitro 2 (BPS-750C2)
    Keyboard Logitech G710+
    Mouse Logitech G402
    Headset/Speakers Microlab H11
    OS W10
    Network RouterAsus RT-AS87U

    Join Date
    Jul 2017
    Reputation
    10
    Posts
    32

    There is a method with closing 1 and 5 pins on the chip "Realtek" at the stage of loading

  10. #10
    New ROGer Array Broheim PC Specs
    Broheim PC Specs
    MotherboardASUS Z170-A
    Processori7-6700K

    Join Date
    Jan 2018
    Reputation
    10
    Posts
    10

    Quote Originally Posted by KSMerg View Post
    There is a method with closing 1 and 5 pins on the chip "Realtek" at the stage of loading
    Can you elaborate, please? Where is this chip, and what is this procedure supposed to accomplish? Or do you have a link so that I can read about it?

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •