Closed general

Setup stopped at Setup didn't finish

Justin Zimmerman · 11d ago ·closed by John Lauer

Filed from Hydrogen Desktop 1.0.666 on JDSTHIRDEYE (setup card).

What the setup card said: Something went wrong part way through. Run setup again: it picks up where it stopped. If it stops here again, report it and we will look at the log.

Device: CyberPowerPC GamingPC (AMD64, 31.8 GB RAM, Intel(R) Core(TM) i5-14400F). Microsoft Windows 11 Home 25H2 build 26200. WSL: WSL version: 3.0.3.0.

Attachments: hydrogen-desktop-tail.log (last 300 KB of the app log), diagnostics.json (health, setup state, WSL status, the Doctor checks, build info, device), setup-steps-wsl.json (setup step log), setup-timing-wsl.json (setup step log).

Last 40 log lines:

11:12:03.634 [heartbeat] alive 1740s
11:12:05.066 [telemetry] heartbeat ensure-workspace : HTTP 521
11:12:13.635 [heartbeat] alive 1750s
11:12:17.596 [keeper] holding Adom-Workspace open (wsl.exe pid Some(9772)) so WSL does not shut it down as idle
11:12:23.635 [heartbeat] alive 1760s
11:12:33.636 [heartbeat] alive 1770s
11:12:43.636 [heartbeat] alive 1780s
11:12:53.637 [heartbeat] alive 1790s
11:13:03.349 [samples] remote prompt list updated (14 entries)
11:13:03.637 [heartbeat] alive 1800s
11:13:04.554 [telemetry] heartbeat ensure-workspace : HTTP 521
11:13:13.638 [heartbeat] alive 1810s
11:13:23.638 [heartbeat] alive 1820s
11:13:33.639 [heartbeat] alive 1830s
11:13:43.639 [heartbeat] alive 1840s
11:13:49.613 [first-run] focus_signin_window: we have not opened a sign-in for this intent, so there is nothing to raise
11:13:50.000 [auth] Auth intent created, URL: https://hydrogen.adom.inc/auth/intent?token=[redacted]&install_id=9c35a6dc-5a90-4be0-82ce-ba9f7bc42daa
11:13:50.000 [auth-ttl] adom intent created claimed_ttl=3598s expires_at=2026-10-30T19:13:49Z
11:13:50.000 [auth] backend poll armed for 1830s (intent ttl 3598s)
11:13:50.004 [browser] open-in-profile: https://hydrogen.adom.inc/auth/intent?token=[redacted]&install_id=9c3 in default:Default fresh=true
11:13:50.004 [caption] auth narration suppressed (assisted sign-in OFF): Opening the Adom sign-in in your default browser (Default)…
11:13:50.169 [telemetry] signin_screen: HTTP 502
11:13:50.375 [browser] raised the opened window hwnd=1641252 for the user -> true
11:13:50.375 [approve] assisted sign-in OFF, Adom auto-approve loop NOT armed; the user clicks Approve themselves
11:13:50.376 [browser] recorded consent window hwnd=1641252 (direct open), so it can be raised and closed later
11:13:53.639 [heartbeat] alive 1850s
11:14:03.640 [heartbeat] alive 1860s
11:14:05.345 [telemetry] heartbeat ensure-workspace : HTTP 200
11:14:13.641 [heartbeat] alive 1870s
11:14:23.641 [heartbeat] alive 1880s
11:14:33.642 [heartbeat] alive 1890s
11:14:43.643 [heartbeat] alive 1900s
11:14:53.643 [heartbeat] alive 1910s
11:15:03.644 [heartbeat] alive 1920s
11:15:04.655 [telemetry] heartbeat ensure-workspace : HTTP 200
11:15:13.644 [heartbeat] alive 1930s
11:15:17.971 [auth] Intent authenticated, session token saved (+ replay copy)
11:15:17.971 [auth] Bringing HD to the foreground after Adom auth completion…
11:15:18.262 [cmd] $ wsl -d Adom-Workspace -u root -- <write /home/adom/.adom/api-key + /run/adom/api-key + /etc/tmpfiles.d/adom-api-key.conf>
11:15:18.332 [updater] signed-in user changed, checking now so the fleet ping carries who this is

5 Replies

Justin Zimmerman · 11d ago

any luck

Justin Zimmerman · 11d ago

Update on Issue #157:

I followed Hydrogen's recommended recovery procedure and successfully unregistered Adom-Workspace using PowerShell.

I then completely closed Hydrogen and Adom Bridge and launched Hydrogen again.

The fresh installation downloaded the 775 MB workspace image and appeared to progress farther, but eventually failed again with exactly the same error: "Couldn't build the workspace image."

Windows 11 and WSL 2 have both been verified working.

Please review the latest setup logs and identify the specific failing step. A complete workspace reset did not resolve the issue.

Colby Knox · 10d ago

Thanks for the detailed logs, Justin. The workspace itself was fine: Linux started and the editor was running inside it, but Windows could not connect to it over WSL's mirrored networking, so setup stopped. The "Couldn't build the workspace image" message was wrong for this failure and sent you to unregister and re-download for nothing, sorry about that. We're fixing both: the message, and setup will switch to WSL's standard (NAT) networking on its own when mirrored can't connect.

It looks like setup finished on your last launch, about 25 minutes after your message. Is Hydrogen working for you now? And did you change anything before that run (for example networkingMode in .wslconfig, or a VPN or firewall)? That tells us which part fixed it.

Justin Zimmerman · 10d ago

Update: Switching WSL networking from mirrored to NAT resolved the Hydrogen installation/startup problem on my Windows PC.

After changing the WSL networking setting to networkingMode=nat and restarting WSL/Hydrogen, I confirmed:

  • Hydrogen opens and runs.
  • Codex is signed in and can inspect project files.
  • Adom Bridge shows connected.
  • Windows files are accessible through /mnt/c/Users/.
  • I successfully copied an existing KiCad project into /home/adom/project/ and opened the copy in Hydrogen.

NAT is a working workaround on this machine. This does not establish why mirrored networking failed, but the installation should account for systems where NAT works and mirrored networking does not.

John Lauer · 9d ago

Justin, the fix for this is now public in Hydrogen 1.0.701. Your Hydrogen updates on its own.

What changed: when Windows cannot reach the workspace over mirrored networking, setup now switches to NAT networking once and carries on, and the card says it is a network problem instead of "Couldn't build the workspace image". So nobody gets sent to unregister and re-download a good workspace again. You can switch between mirrored and NAT any time in Settings, Workspace networking.

Since NAT is working for you, there is nothing you need to do. Everything else in this release: What's new in 1.0.701. Closing this; reply here if anything comes back.

John Lauer closed this · 9d ago

Log in to reply.