Yes @SoniX - I think maybe I corrected all checksums myself after edits, I can't remember, but that may be also why all times you checked when comparing are very close too.
I noticed checksum was wrong when dropping the hex edited file into UEFITool, then fixed other two as I went along. So, whatever gives checksum in UEFITool for that module could be invoked to get correct value post re-insertion, then correct checksum last.

Well, in any case, we know that the problem is in the UEFIReplace. At the moment, only one solution - to use MMTool.
Since it makes no sense to repair the old platfomu UEFITool, which made UEFIReplace.

v1.70 RC17 not working:

@Fischer
Attach BIOS file.

I just downloaded UBU 1.70 rc17 and copied patched MMTool v5.2.024 into its folder. Then I pasted the latest BIOS 1604 for a Asus Sabertooth 990FX (https://dlcdnets.asus.com/pub/ASUS/mb/So...X-ASUS-1604.zip) to UBU's folder and started it. I want to test the replacement of AMD microcodes, so I did try it and got the message "parseBios: one of volumes inside overlaps the end of data File replaced". This doesn't sound like everything is ok.
Here is a screenshot: https://imgur.com/2L8WhV5
What's wrong here?

Edit:
After saving the modded BIOS file, I opened it with UEFITool 0.25.1 and it says "parseBIOS: one of volumes inside overlaps the end of data". However, this also happens with the original BIOS file from Asus. Is this a problem?

Zitat von SoniX im Beitrag #4579

---

@Fischer
Attach BIOS file.

---

@Fernando:
Thank you, and sorry for posting on the wrong thread. :)

Zitat von Fischer im Beitrag #4578

---

v1.70 RC17 not working:

---

@SoniX - even with MMTool I think checksum has to be corrected afterwards (Which I got correct value by dropping after MMTool edit into UEFITool) - in case this info helps find solution with UBU via MMTool edit >> CS corrected after >> Then save file.

@Lost_N_BIOS
There is a solution.
1 - Extract as file - 'file.ffs'
2 - Change microcodes. - in 'file.ffs'
3 - Fixed CS - in 'file.ffs'
4 - Replace the file with MMTool - 'file.ffs' to BIOS file

3* Later add the correction CS.

Yes, I think that method will work fine, I am not sure if CS needs to be corrected last, or can be corrected before reinsert with MMTool (may not matter, since MMTool does not attempt to adjust)
What value/method is UEFITool using to get CS? I tried a few ways and never found exact same checksum, with and without header, many different CS values checked and none matched what UEFITool gave so I gave up looking and accepted that as correct

I have updated Asus Sabertooth 990FX/Gen3 R2.0 mainboard to the latest Spectre patched microcode, and all other updates on the list. Everything is fine....

@SoniX:
If I put the Bios "MAXIMUS-V-FORMULA-ASUS-1903.CAP" in the Main folder of UBU and click UBU.bat as Admin it is working
If I have no Bios in UBU Main Folder and click UBU.bat than I can select a File and than i get this Errors!

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

@Lost_N_BIOS
Checksums are considered easy. Are corrected, if it is, only once before the integration of the FFS into the BIOS file.