@PetrB - Replied to above in PM

Here, please test and let me know, chipset visible yet or not (maybe not, but this test need done before further edit in regards to chipset is done) Additionally, this will have the changes you mentioned at #13
Wait, first please test these two BIOS, let me know which, if either, shows chipset - then I do rest and further chipset test if needed
All edits here done ONLY with Hex editor, and UEFITool v25 (FYI) - http://s000.tinyupload.com/index.php?fil...265029319265257
If chipset is visible, grab me images of all contents when you have time, that way in a later edit I can add anything still missing

* Edit - @PetrB - OK, here is next round, please test in order as follows, once chipset appears stop, no further test needed (if it appears)
If it does not appear, another round of three similar to this will follow
1. Default
2. User
3. Super

Also, on one of these tests, please rename the BIOS file, not extension, so we can see if other than default name is OK
It makes life easier on everyone if BIOS can be named other than default during testing like this.
I usually use names to let me know which edit is what vs using folders, it's much easier that way.

http://s000.tinyupload.com/index.php?fil...255813219058000

* Edit 2 next round - https://ufile.io/j53oyas2

I've noticed something strange with all archives received from you.
The total size of the archive equals to single file compressed size.
(Total archive size is 8 877 585 bytes - just 235 bytes greater then single file compressed size).
The size is shown only for the 1st file, the other 2 files have "???" size.
But no decompression problem occurs.
Please take a look to the attached picture.

All normal when looking at 7zip file in winrar, explained in PM, nothing to worry about

Please find the dump of last mod.

2.
I've tried to go deep into "18 - error". I've made some findings. I am not sure that they are useful (may be findings are wrong, may be everybody knows about it, but no solution possible).

Anyway, I want to share those findings with you:
- I was using UEFITool v0.25 to replace "Setup" (899407D7-99FE-43D8-9A21-79EC328CAC21) section ("47 02" -> "46 02" changes only), (the 2nd one in SMC BIOS)
- after replacement and saving (rebuilding), the "Setup" section (899407D7-99FE-43D8-9A21-79EC328CAC21) looks same as before (same size, etc),
- also, the parent section (8C8CE578-8A3D-4F1C-9935-896185C32DD3) have same size as before,
- but "grand-parent" section (EE4E5898-3914-4259-9D6E-DC7BD79403CF) looks different!!! It's size have changed by 30KB!!!
- also, the "pad-file" sections (not-empty in the beginning) are changed too.
I think, that all "18 - error" troubles are happening because of the way how UEFITool rebuilds the volumes after any changes.
The "grand-parent" section (EE4E5898-3914-4259-9D6E-DC7BD79403CF) is compressed. So, when we update any sections inside, UEFITool updates the compressed "grand-parent" section.
I do believe that there is some difference in compression methods (between UEFITool and AMI or SMC compressors) as we are getting 30KB difference even in case if we changed only singe byte ("46 02" -> "47 02").
Also, it looks like the previose volume size (or some other values connected to volume size) are stored somewhere (may be in "pad-files") and any differencee between old and new value - leads to "18-error problem".

Is there any way to keep the all volume sizes unchanged after rebuilding? May be different tool? Or some manually added "zeros"?
If such solutions are possible, then we will overcome "18 - error" (not only in my platform - but in other platforms too).

I've attached a picture where size differences are shown in thread.
(black lines for same sizes, red lines for changed sizes).

Finally, I was able to find a correct way to work with my BIOS chip (using CH341A flashrom windows Run From CMD).
Then I've restored old BIOS (copied it from another board).
After that, I flashed a new original Supermicro BIOS (same version as before, but running in Administrator mode) - using Afuefix64.efi utility.
So, now most options are visible, but most needed options are still hidden.

Then I've made a backup copy (using a programmer) - "4.bin" file.
Then I've flashed it again using a programmer (to verify that I can do it correctly).
Then I was able to run the board with no problem (even no problems with MAC addresses - it looks they are stored not in BIOS but at the controllers).

So, now I am completely ready for BIOS mod.
Please find a BIOS image "4.bin" (copied with programmer) and new screenshots in thread.

@PetrB - So, you've erased the chip, then programmed in BIOS? If not, you may not have tested writing a BIOS to this chip with programmer, since the BIOS you mentioned writing was already in place during the above mentioned test.
If you want to be 100% sure before we move forward, issue the erase chip command first. Then write back your 4.bin, then we know for sure write is OK

Yes. I've erased everything first. We are 100% sure.

OK then, here's lets restart that single edit 46/47 test and confirm all is OK after you program back in.
Wait, I see you already have chipset visible in your BIOS images! Did you do that, or was that already visible in new BIOS they sent you?

All wanted options were found here:
- 8E38A88A-C267-4131-A8CD-C0BC80A24CB5
- A5E369C8-ABF9-4B43-B212-FF1BFD35666D
- 1B08A1DB-F91A-4FA1-A911-255C417F1CF7

Please see attachments in thread. All wanted options and their forms are listed inside (I've deleted everything else).

XFR visibility:

Could you please help me to replace microcode?
I was unable to do it myself.
My CPU is AMD EPYC 7H12, CPU ID is 00830F10
I need to remove uCode 8301034, and replace it with old 8301025.
My recent BIOS and 8301025 are attached.

@PetrB - https://ufile.io/b83897b5

In case you need to try other microcodes later - You can do this edit via straight hex edit on the BIOS as a whole, MC Extractor will show you location/offset of each microcode - https://github.com/platomav/MCExtractor
Or, you can extract the two different padding files that contain the microcodes with UEFITool instead, and hex edit those, then replace (use V25 for replace), either way = same file outcome