Thanks, this is a real problem, and it isn't limited to your machine.
What the popup means. "Part of this app has been blocked ... we can't confirm who published adom-pup-bridge.exe" is Windows Smart App Control. It refuses to run a program that is not code-signed. adom-pup-bridge.exe is the pup bridge's own program, which Adom Bridge starts for you, and it is currently unsigned. So are the KiCad, Fusion, Altium and Codex bridge exes: I checked two of our machines today and every bridge exe reads "NotSigned". We never saw this because Smart App Control is off on our machines. A fresh Windows 11 install turns it on.
What is affected. While Smart App Control is on, the pup bridge cannot run on your PC, so browser automation through pup does not work there. The same will happen to any other exe bridge the first time it is started. Adom Bridge itself is signed and keeps working.
What changed in Adom Bridge 2.1.160 (insiders now): Adom Bridge recognises this block and stops retrying. Before this it kept retrying, and every attempt could show you that popup again. A command that needs the blocked bridge now answers blocked_by_windows_app_control, naming the file and Smart App Control's state, and bridge_list shows the same. As soon as a signed version of the bridge arrives through a normal update, Adom Bridge starts it again with no action from you.
The real fix is for each bridge's publisher to ship signed builds. I've raised it with the team, and I'll post here when there's a signed pup build.
Please don't turn Smart App Control off to work around this. On many Windows 11 versions it cannot be switched back on afterwards without reinstalling Windows, and it's a real protection worth keeping.
If you can, tell me what Windows Security > App & browser control > Smart App Control shows on your PC: On, Evaluation or Off.