Closed bug report

Self-update recreates a Desktop shortcut (Bridge.lnk) that the Hydrogen-driven install suppresses with /NODESKTOP

John Lauer · 2mo ago ·closed by John Lauer

Observed 2026-09-02 on two machines: after Adom Bridge updated itself (2.1.3 to 2.1.5/2.1.6), a Bridge.lnk appeared on the user's Desktop (created 17:36:52 on one box, 19:39:04 on the other). Hydrogen installs and updates ab with /NODESKTOP because users launch ab through Hydrogen, and Hydrogen's release sweep gates on 'no Bridge desktop icon'; the self-update path does not pass that flag, so every ab update re-adds the icon. Ask: the self-updater passes the same /NODESKTOP (or remembers the flag from the original install) so an ah-managed install never grows a desktop icon.

1 Reply

John Lauer · 2mo ago

Fixed in ab 2.1.8 (insiders; pkg published).

The self-updater (apply_staged) ran the NSIS with only /S, so every ab self-update re-created the Bridge desktop shortcut. It now OBSERVES the current desktop-icon state and passes /NODESKTOP when no Bridge icon is present, preserving that state instead of persisting a flag:

  • ah-managed install (icon suppressed) → no icon present → /NODESKTOP passed → stays suppressed. This is your case.
  • standalone user who has the icon → present → flag omitted → icon preserved.
  • standalone user who deleted it → not present → /NODESKTOP → stays gone (respects the choice).

desktop_icon_present checks the standard and OneDrive-redirected Desktop for Bridge.lnk / Adom Bridge.lnk. So an ah-managed box will not grow a desktop icon on the next ab update once it is on 2.1.8+. (Boxes currently below 2.1.8 will re-add it one more time on the update that brings them to 2.1.8, then never again; Hydrogen can delete that one stray icon in the same sweep if needed.)

John Lauer closed this · 2mo ago

Log in to reply.