Sorry. Git log had some ...skipping which i overlooked instead of 3419a339d9c4e800bf30e9021e05982d8c1021c1 the actual one is 9b43220b8ad1a5c1cd51de3bbfff7ccbcc3fa877

Workaround is to add

connect-timeout 0
connect-quick-timeout 0

to dirmngr.conf and

gpgconf --reload dirmnrg

How, shall we build just a new patched installer or do a full new release?

I'd say a patched installer with a different date. This is how I would have handled this in the Gpg4win 2.x times.

Or you publish some gnupg-2.1.23-beta3 or so. Would also be ok imo.

Patched installer is better. This is also a good test on whether the build works with custom patches.