I found bios, which crashes mCodeFIT.exe when trying to create FFS with microcodes.

Asrock Q1900M bios version 1.90, UBU_v1.70.b3-DEV

https://www.asrock.com/mb/Intel/Q1900M/#BIOS

@Jest I think it's because the path to the microcode files is too long; try to put UBU at C:\ (or D:\ whatever) in order to have short path lengths.

Well, i tried E:\UBU_v1.70 but mCodeFIT.exe still chrashes, but its working correct with Asrock Fatal1ty Z270 K6 bios.

@Fernando

"...you got the "wrong" info about the UBU version." I didn't said wrong. I realized it just true. It is not b2 obviously.... Said, a little mistake!

Zitat von Jest im Beitrag #4021

---

I found bios, which crashes mCodeFIT.exe when trying to create FFS with microcodes.
Asrock Q1900M bios version 1.90

---

25/5000
Very unprofessional

Zitat von Fernando im Beitrag #4025

---

Zitat von karakarga im Beitrag #4024

---

I didn't said wrong. I realized it just true. It is not b2 obviously.... Said, a little mistake!

---

To avoid such mistakes I will stop offering self-updated UBU tool versions in the future.

---

@soupiraille

Not having a similar motherboard is hard to say anything. Try again.

Try to update with MMTool. In version 1.70b5 it can be done, you just have to remove "rem".

to

Hi,

Just wanted to report that the latest Ubu on the developer's site version v1.69_17_2 will wipe out the FIT table on some bios's like the Z170-WS board when updating LAN or GOP modules.
I did not update the cpu microcodes as I do those manually and yet the FIT table got cleared. Apologize if this has be mentioned before and I am not aware.

Thank you

Edit: Was using a bad newer version of MMTool. Sorry.

Yes. This problem is known.
_FIT_ spoils or destroys the 5th version of MMTool. Basically, this happens in BIOS on the Aptio V platform and if _FIT_ is located in volumes without header.
Also MMTool v5.2 spoils or deletes _FIT_ if only microcode updates are performed.
For Aptio 4, this problem is not critical.

In the version of UBU 1.70 this problem is solved by reserving _FIT_ with the subsequent restoration and do not used MMTiool, to update the files, for Aptio V.

Hello SoniX and to the others who have developed the BIOS Updater utility,

What an amazing coincidence that you all released beta 5 of the updater today. This weekend, I decided to see if I could find a way to create updated BIOS files for my MSI Z87 and Z97 motherboards. My goal was to create the latest December 2017 pre-Spectre BIOS updates, and then to also create the latest April 2018 BIOS updates which have the latest version 2 Intel microcode which protects against Spectre. To do so, I had to copy Intel microcode files from UBU version 1.69 into the latest UBU version 1.70, and then modify the MCUpdate.txt file to only point to the specific latest microcode files which I wanted to update. I am about to do the whole thing again since today you all just released version 1.70 beta 5. With beta 3, I was seeing error messages that the DOS signature is invalid when I was updating my BIOS files. Needless to say, I did not attempt to flash these new BIOS files.

Microsoft, in their desire to force all Windows 7 and 8.1 users to upgrade to Windows 10, is only implementing OS Spectre microcode updates in Windows 10. For all Windows 7 and 8.1 users, those users must rely on their OEM motherboard manufacturers to publish new BIOS updates for their motherboards. Needless to say, most motherboard manufacturers have chosen to publish BIOS updates for motherboards which were initially released to retail within the last 3 years. I have been through rounds with MSI tech support to get BIOS updates to protect against Spectre for my MSI Z87 and Z97 motherboards. They say that they will provide a BIOS update for my Z97 motherboard, yet not for my Z87 motherboard. I even agreed to test any BIOS updates which MSI is working on. Their reply was exactly this: "Fine." I haven't heard anything from MSI for quite a while. I most likely am done with MSI in the future, mostly due to the cold responses from MSI's tech support people. It is what it is.

Are the "DOS signature is invalid" messages now fixed in beta 5, or is this an error message which I can simply ignore if it still occurs when I use beta 5?

By the way, the UBU_dev.bat file is quite impressive in its coding. The only thing which I might suggest is adding, upon exit, what I call a "stupid pet trick" which will hold the Command Prompt window open so that users can easily copy and save the history of all actions which the user performed while using the BIOS Updater tool.

Best regards,

--GTP

@Sonix,
Some screenshots to update Sabertooth X99 v3801 BIOS with last '3D' µCode. I think all is OK:


However, I found a problem with Intel Network option:


EDIT by Fernando: Insertion of the pictures corrected (they were only attached, not inserted)