Zitat von karakarga im Beitrag #3747

---

"Invalid FFS File"

---

  -s, --checksum        Indicates to calculate file checksum.
 

Therefore, all who encounter this problem need to fix all strings:

%udk%\GenFFS -t EFI_FV_FILETYPE_RAW -g %cguid% %mc1% %mc2% %mpdt% -o tmp\mCode.ffs
 

add the '-s' switch

%udk%\GenFFS -s -t EFI_FV_FILETYPE_RAW -g %cguid% %mc1% %mc2% %mpdt% -o tmp\mCode.ffs
 

Add:
Fixed in UBU 1.70 a15/1.69.16

I made the following observation with UBU v1.16.15 Update 2:
Updated the bios for ASRock Z68Extreme3 Gen3 with latest microcode for Ivy/Sandy Bridge (2D/1F).
After flashing bios shows microcode revision 0.
The microcode isn't recognized by bios

UBU itself shows that the microcode was updated (using latest microcode -> yes).
Anyone tested this on Z68 or Z77 platforms yet?

@mictlan:
Please see my post for a Z77 Platform : post #3742, everything went fine and it shows the right microcode revision 1f in UefiBios.

EDIT by Fernando: Unneeded fully quoted post replaced by directly addressing to the author (to save space)

@Sonix
I have run mmtool 5.0.0.7 click on load file, loaded the bios file (I have used "Windows Bios Utility Aptio 4" then click on AFUWINGUI.exe twice Save the bios file from notebook and Open) I have pressed CPU Patch button.

Now the problem is: It only allowed me to "Extract a Patched Data" the upper "Insert a Patch Data" and lower "Delete a Patch Data" options were grayed! I can not choosen them. Therefore mmtool 5.0.0.7 was rejecting the bios file that I want to manually insert.

Then I tried mmtool version 4.50.0.23 it allowed me to first "Insert a Patch Data" I have inserted:
cpu206A7_plat12_ver0000002D_2018-02-07_PRD_1BDB79EA and
cpu306A9_plat12_ver0000001F_2018-02-07_PRD_3023E347, (I have extracted those 2 files when modifying MSI Z77A-GD65's bios before.)

I have choosen "Delete a Patch Data" and deleted 2 other old Ivy Bridge 1C and Sandy Bridge 29 microcodes.
Saved and again with "Windows Bios Utility Aptio 4" tool run AFUWINGUI.exe choosed "Save" tab with ticking option "Do not Check ROM ID" it flashed the bios file to my Sony Vaio VPCF21Z1E.

As a result, InSpectre_r7 now tells:
System is Meltdown protected: Yes
System is Spectre protected: Yes
Performance: SLOWER (Yes I know it!)
CPUID: 206A7

And HWiNFO v5.74-3363 informs:
μCU: 2D for my Intel Core i7-2860QM processor.

I have written down step by step for others to understand. At this example, the problem is "mmtool 5.0.0.7" won't allowed me for "Insert a Patch Data" and "Delete a Patch Data" to tick!

I think: "Invalid FFS File" error is related with mmtool 5.0.0.7 running UBU_v1.69.15.2_incl-Update2
But, this summer, I am sure that, I have used "mmtool 5.0.0.7" making a similar modification. Why it currently rejects the task? Strange....

EDIT by Fernando: Unneeded blank lines removed (to save space)

"Invalid FFS file" error fixed with version "UBU_v1.69.16_without-MMTool", thank you....

Zitat von N6O7 im Beitrag #3753

---

@mictlan:
Please see my post for a Z77 Platform : post #3742, everything went fine and it shows the right microcode revision 1f in UefiBios.

---

@mictlan

See my previous post #3743.

In short, my findings were the same.

Zitat von N6O7 im Beitrag #3742

---

Now i'm waiting Microsoft to patch "mcupdate_GenuineIntel.dll" because it's still the 2015 .dll with microcode 1C listed inside, so it does not match it anymore.

---

@RvdH,

yes indeed, it does now match the bios update in the registry settings.



Wish MS still update System OS those older processors as they did for Skylake with the KB4090007.

Zitat von N6O7 im Beitrag #3758

---

Wish MS still update System OS those older processors as they did for Skylake with the KB4090007.

---

@tistou77
Since i have a Windows 7 x64 pro, I do not think i can install KB4090007 made for Windows 10 v1709.

Aa, you have Windows 7, ok
And for Windows 10 is better or not ?

Why not...One could try as it will not harm the system OS anyway, just update the .dll

Zitat von ygbsm im Beitrag #3756

---

See my previous post #3743.

---

Yup, been trying to change my micro-code(to the first one, want to try and see if I can OC this thing, but same occurs with any other version of micro-code), getting invalid size errors and UBU is removing all the micro-codes and only leaving two, both on the address of Broadwell micro-code.

UBU_v1.69.15.1 and MMTool 5.00.00.7.

See the before, after and using the m option:






If there is any extra info needed to debug this, I'm glad to provide it.

@RvdH @N6O7 @tistou77
I saw your conversation regarding the Microsoft "kb" updates for Spectre; if you did not already know, keep in mind that those updates are not needed if you have already updated the microcodes of your BIOS. See this article for more discussion.

@SoniX
I did not know that! Interesting. It is strange how the right mcode was called when there were that many before; however, I'm satisfied enough to have found a workable solution (User Select). I believe that should suffice for others with similar platforms as well - yet if you would like to take a closer look, just let me know and I'll be happy to provide you before/after images of my BIOS. My guess is you have your hands full already. Thanks again for all your help!

@senso
Try using UBU_v1.69.16. If that doesn't work, try using option "M - User Select" mode and picking the specific mcode .bin file you want (located in UBU subdirectories). This worked for me on my Z68 board as per my post #3743.