0.2.43 can't be installed: no manifest points at it, and AdomBridge.dll is still unsigned

by adom

Adom Bridge for Altium Designer: a resident DelphiScript agent gives the AI eval, the 1,100-command process launcher, all 8 EDA surfaces with screenshots, compile/ERC, DRC, OutJob outputs, native SchLib/PcbLib authoring with STEP 3D bodies, and dialog handling by PID.

Overview Files Skills Discover Packages Releases Dependencies Issues Breadcrumbs Pull Requests Activity

Closed general

John Lauer · 22d ago ·closed by Colby Knox

I tried to install the signed 0.2.43 on a test PC (arav-rog) through Adom Bridge and couldn't, for two reasons.

1. No manifest points at 0.2.43, so nothing can install or update to it. The release is on the page (0.2.43, 2026-09-29 15:07), and the last commit is "0.2.43 (STAGED, signed)". But both manifests Adom Bridge reads still point at 0.2.39:

public: api/v1/pages/altium-bridge/files/adom-bridge-altium-manifest.json has version 0.2.39, url .../0.2.39/adom-bridge-altium-v0.2.39.zip
insiders: api/v1/pages/insiders/files/altium-bridge/version.json has version 0.2.39 too

Adom Bridge only installs and updates a bridge through its manifest (bridge_install {manifestUrl}, the 4-hour auto-sync, refresh_bridges), so right now every box stays on 0.2.39 or 0.2.40 and never sees 0.2.43. It looks like the step in the release that writes the insiders manifest hasn't run.

2. AdomBridge.dll in the 0.2.43 zip is still unsigned. I downloaded adom-bridge-altium-v0.2.43.zip (sha256 matches the release) and checked every PE file with Get-AuthenticodeSignature:

Valid      timestamped  altium-bridge.exe                    CN="Adom Industries, Inc."
NotSigned               extension/AdomBridge/AdomBridge.dll

Smart App Control checks DLLs a program loads as well as the exe it starts (that's what #219 on adom-bridge showed: "we can't confirm who published ... that the app tried to load"). So on a PC where it's on, Altium could refuse the plugin even though the bridge exe starts fine. Please sign the DLL too. Since 0.2.43 is already published, that means a new version.

For reference, the fleet today:

	AdomLapper	ConfRoomROG	arav-rog
altium installed	0.2.39, exe + dll unsigned	0.2.40, exe + dll unsigned	broken: only `altium-bridge.exe` from 9/21, no `bridge.json`, so Adom Bridge doesn't list it

Once a signed build (exe and dll) is on the insiders manifest, I'll install it cleanly on arav-rog, replacing the broken install, and confirm every file reads Valid on all three boxes. Post here when it's staged.

3 Replies

Colby Knox · 22d ago

Both fixed in 0.2.44, staged now.

2. The DLL is signed. You were right, and the release script now signs every PE file the zip ships, not just exes, and refuses to package any that is unsigned. Checked on the published zip and again after installing it through Adom Bridge on Colby-ROG2:

Valid      timestamped  altium-bridge.exe                    CN="Adom Industries, Inc."
Valid      timestamped  extension\AdomBridge\AdomBridge.dll  CN="Adom Industries, Inc."

zip sha256: e4e7b0e3872e... (release 0.2.44)
altium-bridge.exe sha256: be79a55f2f2a3016229a92c6a855f40b0c535823f09a8ed113bc48586a9677b6
AdomBridge.dll sha256: cd26991e27cdec309f59efaf418b2b5cfe871e4e87644d019e9df077dafe0a7a

1. How to install it. No manifest moved for 0.2.43 on purpose: it carries the 0.2.42 code, which still owes your licensed test run, and moving altium-bridge/version.json would auto-update every insider box to untested code. So 0.2.44 has an install-only pin on the insiders page, the same approach you used for 0.2.41:

bridge_install {"manifestUrl": "https://wiki.adom.inc/api/v1/pages/insiders/files/altium-bridge/pin.json", "force": true}
bridge_kill {"name": "altium", "confirm": true}

force: true replaces whatever is there, so it should also clear arav-rog's broken install (the lone 9/21 exe with no bridge.json). I ran exactly this on Colby-ROG2: 0.2.44 installed, respawned, and both files read Valid as above.

Once the battery is green on arav-rog, I'll move the insiders manifest to 0.2.44 and close #11-#13. If you'd rather have the insiders manifest moved now instead of using the pin, say so here.

John Lauer · 21d ago

0.2.44 checks out on arav-rog:

Installed from the pin (insiders/files/altium-bridge/pin.json) and replaced the broken install. bridge_list shows altium 0.2.44, running.
Signatures: 2 of 2 PE files are Valid and timestamped, altium-bridge.exe and extension/AdomBridge/AdomBridge.dll, both "Adom Industries, Inc."
It starts and answers: altium_status returns bridgeVersion 0.2.44, engine rust, and finds Altium Designer 26 installed (not running). The log shows bridge 0.2.44 listening on 127.0.0.1:53039 right after Adom Bridge spawned it.

One caveat: arav-rog has Smart App Control off, like all our machines, so this proves the files are signed and the bridge runs, not what a SAC-on PC does with them. I didn't launch Altium itself, so the DLL hasn't been loaded into X2.exe here.

From my side it's fine to move the insiders manifest to 0.2.44.

Colby Knox · 21d ago

Thanks for checking it on arav-rog. Done: the insiders manifest now serves 0.2.44 (signed exe + dll), so boxes on the insiders tier pick it up on their normal update. Public stays on 0.2.39. The temporary pin.json is removed.

Both points in this issue are resolved, so closing. Your caveat stands and I've recorded it in the insiders release log: nothing has loaded the DLL into X2.exe with Smart App Control on yet, and the 0.2.42 behavior changes (bounded altium_panel, demo error fields) still need a run with Altium open. Those stay tracked in #11-#13.