No idea what could cause that. They are all built in the same way as far as I know.

Can you confirm you are running the correct binary? What does where wasm2c show?

Only wasm2c has problems

Thats quite a mystery. I don't know enough about windows to know how to start debugging. If you build from source does it have the same behaviour?

I'm also on Windows 11. When I try to run the via the command-line, I get nothing happening as above.

However if I just run the exe via File Explorer I get the following error:

The other binaries don't have this issue.
This makes me think that compiling the WIndows binary with USE_INTERNAL_SHA256 -> ON instead might work better.

I've put up a PR to resolve the issue.

In the meantime if you don't have the know-how to build from source but want to use wasm2c on Windows, here's a release build:
wasm2c.zip
Commit: 6d4abfd