Yes, I know setup gives good IFR, but that is not one of the problem modules, so I never looked at it much. Your tests seems like AMITSE might be main/only issue then, that is mostly text setup file. If you make the change there only, it breaks setup tab still in AMIBCP?

Changing only AMITSE does not work, all the files must be either removed or "corrected" (setup is one of them). The test I made was with the other files "corrected" (I change the sequence 00 48 00 49 00 49 to 00 48 00 49 00 00)

So which is it, that sequence or the one I mentioned removing the last three digits from? That sequence above is only 5 digits (Unicode), so shouldn't be an issue since it's not longer than 8 digits.

I think that things are a bit confused. Let me summarise what is known on the problem.

The ROM of all the Supermicro motherboards of the series H11-xxx cannot be opened with AMIBCP v 4.53 or higher, the error message being "Language name present in the ROM file exceeds 0x08 in lenght. Setup tab and BIOS String tab will not be shown."

Inspection of the ROM with UEFITool has shown that all the following files are somehow responsible for the error.

- Setup
- ServerMgmtSetup
- ReFlash
- EventLogsSetupPage
- HDDSmart
- FboGroupForm
- AMITSE

The sequence "00 48 00 49 00 49" is present in the first six files, while the sequence "F2 BC 65 CA E9 F9 BE 86 9E 1D 1C 61 91 FC 6F 09 A1 98 83 9E" is present only in AMITSE. All the sequences must be either removed or corrected (or the files removed) in order for AMIBCP to be able to open the ROM with "Setup configuration" and "BIOS String" avaible.

When the sequence in AMITSE is altered, no matter how (for instance by removing the last three digits), all the folders in "Setup configuration" are nameless. When the whole module AMITSE is removed from the ROM two of the folders in "Setup configuration" are normal, "AMD CBS" and "SATA Information", the other ones are however nameless. (The tests on AMITSE must however be done with the other six files "corrected", otherwise AMIBCP will not open the ROM.)

What is strange to me is that changing the last digits of the sequence in AMITSE seems to have a larger effect on "Setup configuration" than removing the entire AMITSE module.

I hope this help...

Thanks for your updated summary, I wasn't sure about the strings you mentioned, if it was only one now or both. Maybe AMITSE is using a checksum? If not, then maybe instead of removing those last three digits, test these changes
1. F2 BC 65 CA E9 F9 BE 86 9E 1D 1C 61 91 FC 6F 0F A1 98 83 9E
2. F2 BC 65 CA E9 F9 BE 86 FF 1D 1C 61 91 FC 6F 09 A1 98 83 9E
3. F2 BC 65 CA E9 F9 FF 86 9E 1D 1C 61 91 FC 6F 09 A1 98 83 9E

So the first change gives an error:"ROM image contains invalid packages. Setup tab and BIOS String tab will not be shown.", while the second and third changes give nameless folders

Damn! Seems like it's one of those bytes to me, but unsure what should be set. I think 00 in any of them will cause failure.

So you have been able to open and see named menu items with the 00 48 00 49 00 49 edit to setup, in some instance, or never? I wonder if blank names maybe due to the setup edit rather than the AMITSE change?
When you edit the 00 48 00 49 00 49 H.i.i in setup did you test both FF and 00?

Nope, I tried only 00, i.e. 00 48 00 49 00 49 > 00 48 00 49 00 00 . I will try with FF and let you know.

So replacing the last byte in 00 48 00 49 00 49 by FF or 00 gives the same result, i.e. nameless folders in "Setup configuration".

I meant 00 48 00 49 00 49 >> 00 00 00 00 00 00 or FF FF FF FF FF FF or 00 FF 00 FF 00 FF for all 7 instances

Sorry for the misunderstanding... Anyway, the result is the same, i.e empty folders.

Maybe it's the 86 byte in the AMITSE string that needs changed, try F6 or 06
Or after 9E try 1E or 1C

Or 09 near end, try 08

So the first two changes (86-> F6 and 86 -> 06) give empty folders. Changing 1D to 1C gives the error message "The ROM contains invalid packages..." while changing it to 1E give empty folders. Changing 09 to 08 also gives empty folders.

So finally I think that I have found what the problem was...

The modules that I identified as the "faulty" ones indeed contained an error, but the bytes series were not directly causing this error.

The first mistake was to work directly with "AMITSE" which is a compressed file. Thus, the faulty byte series was not matching something meaningfull but just compressed information. The solution was to work with the PE32 image which is not compressed. Using the PE32 image I found that removing the same bytes than in the other modules would solve the problem. Consequently all the files contained the same error, AMITSE was not different.

The,n I found that in all the modules, before the bytes "00 48 00 49 00 49", was another series of bytes "58 00 00 80 18 00 00 80 00 00 00 00" indicating the beginning of the ".rsrc" section of the PE. This section contains all the resources of the modules. Thus, chaging these bytes would not really solve the error but rather mess with the ".rsrc" section in such a way that it was not loaded anymore (or something else, I do not really know), indirectly avoiding the error. This explains why the ROM could be opnened but all the folders were nameless.

Finally, a deeper inspection of the ".rsrc" section allowed to find that there was a series of bytes at the end of the "string" part of the resource section that looked strange. The series was : "04 39 00 00 00 39" = ".9...9". It turns out that the byte "04" was the source of all this mess!!! Replacing it by 00 in all the modules eventually solved the error!

Now the ROM can be opened in AMIBCP with all the folders.

I do not really understand why the error message was pointing to a "language name" that would be "too long"... Do you have any idea?

Wow, very cool you finally found the problem! I am sure @Blissed will be happy too
Maybe that is the only way the program knew to describe the error? Or, in legible tool, or assembly, that is part of a messed up over 8 character name/function?

Now, I wonder if that is error they made, or on purpose to deter modifications