Fixed in master.

Thanks for your report.
I think that your patch is too generous to run HMAC even if fips_mode is not enabled; Simply, we can stop calling integrity check when fips_mode is not active.

I could reproduce the problem (by chance) now, because I started a VM I didn't use for a while:

This is caused by the encoding of file in windows. If we directly redirect the stdout to file, windows encodes the file as CRLF+UCSE LE BOM but linux encodes it as LF+UTF-8. To make the file work, I just need to run dos2unix to convert the encoding. Hope it help someone having similar issue.

yikes. Sorry for that one,..

Fixed. Needs to go into the next gpg4win release.

I use BBG-SWD (my own tool to flash MCU) for transparency of the process. It's up to you to choice a tool for initial flashing.
Just in case, here are resources to be reproducible.

Ah okay, that was Windows were we have a couple of warnings anyway. Must have missed that one.

Aiiih, what happend to the sentinel attribute? I need to check.

Original issue (of pinentry-curses, which should be killed by CTRL-C) is related to T2011: gnupg should notify cancellation of its operation to gpg-agent to kill pinentry, I suppose. It is fixed in master and testing.
I don't know about the second one with pinentry-tty.

Fixed in master.

Gnuk implements the feature, and newer GnuPG shows a dialog to request pushing the ack button.

Your problem is apparently not an issue of upstream development of GnuPG; It is your setup script (agent.sh?) which specifies /dev/shm/SOMETHING.
Standard GnuPG never does that. We have no idea about use of /dev/shm/SOMETHING.

No. Pinentry is always 32 bits for us.

Could it be possible that it's a 32/64 bit issue?

Is this with the /MINIMAL flag?

Some of my terminology: I call "case", "shell", and "board".

Strange, even if they are missing in the Gpg4win insttall dir they should be picked up from GnuPG which is added to PATH.

Libdns is not our own code and our intention was to keep it in sync with upstream. However, after some initial success the upstream author lost interest. We now consider to rework the code to remove a bit of the more creative use of C99 and maybe even get rid of some of the used C99 features (gnupg is mainly C90 with some exceptions).

I don't think code page is the problem per se though.

0.10.0

Which version of gpa is that?

Please try "gpg --quick-gen-key" which takes the user-id on the command line - that uses a different code path.