Setup.bin Manager doesn't set two apparently-required bits when making a new Setup.bin, so target PC won't load it

[interfect]

I have a Lenovo ThinkCentre M700 Tiny with Intel ME Firmware 11.0.2.1003. I am trying to set it up with MeshCommander v0.9.6.

When I build a Setup.bin from scratch in MeshCommander with these settings:

Intel® AMT Setup.bin file version 4.0.
Records will not be consumed.
Records: 1, Consumed: 0

Record #1. This record is: Valid, Scrambled
Current MEBx Password: admin
New MEBx Password: cJ6c@ud%<EEh (note that the full password does not show in the screenshot due to the < character)
Manageability Feature Selection: Intel AMT
SOL/IDER Redirection Configuration: SOL+IDER - User/Pass Enabled
DHCP: Enabled
Shared/Dedicated FQDN: Shared
Remote Desktop (KVM) State: Enabled
Opt-in User Consent Option: Disabled
Opt-in Remote IT Consent Policy: Enabled
Manual Setup and Configuration: Manual

Then I get the Setup-broken.bin in my attached ZIP file. When I put this on a flash drive as Setup.bin, plug it into my PC, and boot it, I am not prompted by the management engine to apply it.

If instead I start by downloading the Setup.bin from @rgl's intel-amt-notes repo, and reconfiguring it to have those settings, I get the file Setup-working.bin in my attached ZIP file. As far as MeshCommander can tell, these files are identical. But when I put that file on a flash drive as Setup.bin, plug it into my PC, and boot it, I am prompted to apply it!

I dumped both files as hex dumps with xxd, and I diffed them:

$ diff dump-working.txt dump-broken.txt
2,3c2,3
< 00000010: 0100 2e00 0000 0000 0400 0100 0100 0000  ................
< 00000020: 0000 0000 0100 0000 0100 0200 0000 0000  ................
---
> 00000010: 0000 2e00 0000 0000 0400 0100 0100 0000  ................
> 00000020: 0000 0000 0000 0000 0100 0200 0000 0000  ................

It looks like the only difference is that the working file has two 0x01 byte values where the broken file has null bytes: at offset 0x10 and at offset 0x24. One or both of these bits apparently needs to be set for the file to be recognized by my hardware.

Is there a bug in MeshCommander that makes it not set these bits? Or is there some hidden thing I have to click in the UI to get the program to set these bits?

Here's the offending files:
Missing Bits.zip

[si458]

Intel amt stuff isn't being worked on anymore. I'm afraid, so support is very limited

Have u tried using the unscrambled option rather than the scrambled?

[interfect]

At one point I did try unscrambled, and it didn't work either, but I'm not sure if unscrambling the particular file I submitted would make it start working.