Setup stopped at Building your workspace, the Linux computer your AIs work in

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

Closed general

Gary Allen · 15d ago ·closed by John Lauer

Filed from Hydrogen Desktop 1.0.545 on GORC (setup card).

Device: Microsoft Corporation Microsoft Surface Laptop, 7th Edition (AMD64, 15.6 GB RAM, Snapdragon(R) X 12-core X1E80100 @ 3.40 GHz). Microsoft Windows 11 Home 25H2 build 26200. WSL: WSL version: 3.0.1.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:

21:22:07.779 [run_all_wsl] DONE 'ensure-workspace' in 76.7s (failed)
21:22:07.791 [run_all_wsl] HALT: step 'ensure-workspace' failed after 1 attempts; not advancing to later steps
21:22:07.793 [run_all_wsl] persisted setup-state.txt = in-progress (GET /setup/state matches the cascade)
21:22:07.793 [run_all_wsl] TIMING total 76.7s over 1 steps; slowest: ensure-workspace 76.7s
21:22:07.795 [cascade] setup released the editor (opportunistic healers re-armed)
21:22:07.799 [run_all_wsl] install-approval window closed, normal prompting restored
21:22:07.800 [taskbar] cascade ended with a failure, leaving the red progress bar up
21:22:07.800 [wsl-startup] auto-run run_all_wsl finished: Ok("{\"completed\":0,\"failed\":1,\"failures\":[{\"error\":\"=== Ensure workspace runtime (WSL2 Ubuntu) ===\\n=== Ensure WSL2 subsystem is responsive (auto-recovers if wedged) ===\\n  $ wsl --status\\n    | Default Distribution: Ubuntu-24.04\\n    | Default Version: 2\\n  ✓ `wsl --status` ok (0s)\\n  ✓ WSL2 subsystem is responsive\\nChecking WSL2 prerequisites (wsl --status)...\\n  ✓ WSL2 is installed and ready\\n=== Ensure WSL2 subsystem is responsive (auto-recovers if wedged) ===\\n  $ wsl --status\\n    | Default Distribution: Ubuntu-24.04\\n    | Default Version: 2\\n  ✓ `wsl --status` ok (0s)\\n  ✓ WSL2 subsystem is responsive\\nDistro 'Adom-Workspace' not registered, importing the golden image.\\n  → fetching the pre-baked workspace image (≈585 MB)…\\n  ✓ golden image already downloaded (775 MB cached, SHA256 OK), skipping the download\\n  ✓ integrity already verified during the cache check (SHA256 OK)\\n  → wsl --import Adom-Workspace (this can take a moment)...\\n    … extracting rootfs into the workspace VHD, 12 MB written, 3s elapsed…\\n    … extracting rootfs into the workspace VHD, 44 MB written, 6s elapsed…\\n    … extracting rootfs into the workspace VHD, 204 MB written, 9s elapsed…\\n    … extracting rootfs into the workspace VHD, 780 MB written, 12s elapsed…\\n    … extracting rootfs into the workspace VHD, 1452 MB written, 15s elapsed…\\n    … extracting rootfs into the workspace VHD, 2188 MB written, 18s elapsed…\\n    … extracting rootfs into the workspace VHD, 2476 MB written, 21s elapsed…\\n  ✓ imported the v31-full image (775 MB SHA-verified tarball; this is FIXED every run). Workspace VHD: ~2476 MB on disk. This one VARIES run-to-run on purpose: ext4.vhdx is a live, dynamically-growing volume (ext4 overhead + WSL allocation + boot/disk activity), so it's disk usage, not a fixed image total. (21s)\\n  ⚠ import attempt 1/4 failed: import reported success but the distro is not exec-able\\n  → clearing any stale / half-registered 'Adom-Workspace' entry before retrying (scoped wsl --unregister; Docker-safe; no-op if none)…\\n  ✓ cleared a stale workspace entry (or there was none), the next import has a clean name\\n  … probing the WSL subsystem (`wsl --status`), will retry import the moment it's responsive…\\n  … cleared a partial import directory left by the previous attempt\\n    … extracting rootfs into the workspace VHD, 44 MB written, 3s elapsed…\\n    … extracting rootfs into the workspace VHD, 204 MB written, 6s elapsed…\\n    … extracting rootfs into the workspace VHD, 844 MB written, 9s elapsed…\\n    … extracting rootfs into the workspace VHD, 1452 MB written, 12s elapsed…\\n    … extracting rootfs into the workspace VHD, 2444 MB written, 15s elapsed…\\n  ✓ imported the v31-full image (775 MB SHA-verified tarball; this is FIXED every run). Workspace VHD: ~2476 MB on disk. This one VARIES run-to-run on purpose: ext4.vhdx is a live, dynamically-growing volume (ext4 overhead + WSL allocation + boot/disk activity), so it's disk usage, not a fixed image total. (17s)\\n  ⚠ import attempt 2/4 failed: import reported success but the distro is not exec-able\\n  … probing the WSL subsystem (`wsl --status`), will retry import the moment it's responsive…\\n  ✓ imported the v31-full image (775 MB SHA-verified tarball; this is FIXED every run). Workspace VHD: ~2476 MB on disk. This one VARIES run-to-run on purpose: ext4.vhdx is a live, dynamically-growing volume (ext4 overhead + WSL allocation + boot/disk activity), so it's disk usage, not a fixed image total. (0s)\\n  ⚠ import attempt 3/4 failed: wsl [\\\"--import\\\", \\\"Adom-Workspace\\\", \\\"C:\\\\\\\\Users\\\\\\\\garyc\\\\\\\\AppData\\\\\\\\Local\\\\\\\\Adom\\\\\\\\HydrogenDesktop\\\\\\\\wsl\\\\\\\\Adom-Workspace\\\", \\\"C:\\\\\\\\Users\\\\\\\\garyc\\\\\\\\AppData\\\\\\\\Local\\\\\\\\Adom\\\\\\\\HydrogenDesktop\\\\\\\\cache\\\\\\\\adom-golden.tar.gz\\\", \\\"--version\\\", \\\"2\\\"] exited with Some(-1): A distribution with the supplied name already exists. Use --name to choose a different name.\\n  ⚠ import still failing, terminating Adom-Workspace before the last attempt (other distros untouched)…\\n  … probing the WSL subsystem (`wsl --status`), will retry import the moment it's responsive…\\n  ✓ imported the v31-full image (775 MB SHA-verified tarball; this is FIXED every run). Workspace VHD: ~2476 MB on disk. This one VARIES run-to-run on purpose: ext4.vhdx is a live, dynamically-growing volume (ext4 overhead + WSL allocation + boot/disk activity), so it's disk usage, not a fixed image total. (0s)\\n  ⚠ import attempt 4/4 failed: wsl [\\\"--import\\\", \\\"Adom-Workspace\\\", \\\"C:\\\\\\\\Users\\\\\\\\garyc\\\\\\\\AppData\\\\\\\\Local\\\\\\\\Adom\\\\\\\\HydrogenDesktop\\\\\\\\wsl\\\\\\\\Adom-Workspace\\\", \\\"C:\\\\\\\\Users\\\\\\\\garyc\\\\\\\\AppData\\\\\\\\Local\\\\\\\\Adom\\\\\\\\HydrogenDesktop\\\\\\\\cache\\\\\\\\adom-golden.tar.gz\\\", \\\"--version\\\", \\\"2\\\"] exited with Some(-1): A distribution with the supplied name already exists. Use --name to choose a different name.\\n  ✗ import failed: wsl --import failed after 4 attempts: wsl [\\\"--import\\\", \\\"Adom-Workspace\\\", \\\"C:\\\\\\\\Users\\\\\\\\garyc\\\\\\\\AppData\\\\\\\\Local\\\\\\\\Adom\\\\\\\\HydrogenDesktop\\\\\\\\wsl\\\\\\\\Adom-Workspace\\\", \\\"C:\\\\\\\\Users\\\\\\\\garyc\\\\\\\\AppData\\\\\\\\Local\\\\\\\\Adom\\\\\\\\HydrogenDesktop\\\\\\\\cache\\\\\\\\adom-golden.tar.gz\\\", \\\"--version\\\", \\\"2\\\"] exited with Some(-1): A distribution with the supplied name already exists. Use --name to choose a different name.\\r\\nError code: Wsl/Service/RegisterDistro/ERROR_ALREADY_EXISTS\\r\\nIf this error was unexpected, please consider searching for existing issues or filing a new issue at https://github.com/microsoft/WSL/issues.\\n  ✗ workspace setup attempt failed (will retry if attempts remain): wsl --import failed after 4 attempts: wsl [\\\"--import\\\", \\\"Adom-Workspace\\\", \\\"C:\\\\\\\\Users\\\\\\\\garyc\\\\\\\\AppData\\\\\\\\Local\\\\\\\\Adom\\\\\\\\HydrogenDesktop\\\\\\\\wsl\\\\\\\\Adom-Workspace\\\", \\\"C:\\\\\\\\Users\\\\\\\\garyc\\\\\\\\AppData\\\\\\\\Local\\\\\\\\Adom\\\\\\\\HydrogenDesktop\\\\\\\\cache\\\\\\\\adom-golden.tar.gz\\\", \\\"--version\\\", \\\"2\\\"] exited with Some(-1): A distribution with the supplied name already exists. Use --name to choose a different name.\\r\\nError code: Wsl/Service/RegisterDistro/ERROR_ALREADY_EXISTS\\r\\nIf this error was unexpected, please consider searching for existing issues or filing a new issue at https://github.com/microsoft/WSL/issues.\",\"step\":\"ensure-workspace\"}],\"ok\":false,\"timings\":[{\"id\":\"ensure-workspace\",\"ms\":76714,\"ok\":false}],\"total\":8,\"total_ms\":76729}")
21:22:07.800 [wsl-startup] post-cascade: started code-server update poller
21:22:08.104 [telemetry] setup_step ensure-workspace fail: HTTP 200
21:22:13.288 [heartbeat] alive 100s
21:22:23.289 [heartbeat] alive 110s
21:22:33.290 [heartbeat] alive 120s
21:22:43.290 [heartbeat] alive 130s
21:22:53.294 [heartbeat] alive 140s
21:23:03.296 [heartbeat] alive 150s
21:23:03.992 [ad-supervisor] AB health probe failed (1/3 consecutive) - debouncing, no respawn yet
21:23:11.502 [wsl] ["-d", "Adom-Workspace", "-u", "adom", "--", "setsid", "bash", "-lc", "/usr/lib/code-server/bin/code-server --version 2>/dev/null | grep -oE '[0-9]+(\\.[0-9]+)+' | head -1"] failed on the management plane (wsl ["-d", "Adom-Workspace", "-u", "adom", "--", "setsid", "bash", "-l); retry 1/3 in 2 s
21:23:13.296 [heartbeat] alive 160s
21:23:14.045 [wsl] ["-d", "Adom-Workspace", "-u", "adom", "--", "setsid", "bash", "-lc", "/usr/lib/code-server/bin/code-server --version 2>/dev/null | grep -oE '[0-9]+(\\.[0-9]+)+' | head -1"] failed on the management plane (wsl ["-d", "Adom-Workspace", "-u", "adom", "--", "setsid", "bash", "-l); retry 2/3 in 5 s
21:23:19.411 [wsl] ["-d", "Adom-Workspace", "-u", "adom", "--", "setsid", "bash", "-lc", "/usr/lib/code-server/bin/code-server --version 2>/dev/null | grep -oE '[0-9]+(\\.[0-9]+)+' | head -1"] failed on the management plane (wsl ["-d", "Adom-Workspace", "-u", "adom", "--", "setsid", "bash", "-l); retry 3/3 in 15 s
21:23:23.298 [heartbeat] alive 170s
21:23:33.299 [heartbeat] alive 180s
21:23:34.779 [wsl-gate] 'wsl -d (management plane)' timed out: holding every workspace command for 60s instead of stacking more (trip #2)
21:23:34.830 [extensions] could not read the installed set (workspace not ready?); skipping the check
21:23:43.300 [heartbeat] alive 190s
21:23:53.300 [heartbeat] alive 200s
21:23:58.389 [first-run] focus_signin_window: we have not opened a sign-in for this intent, so there is nothing to raise
21:23:58.502 [auth] Auth intent created, URL: https://hydrogen.adom.inc/auth/intent?token=[redacted]
21:23:58.502 [auth-ttl] adom intent created claimed_ttl=904s expires_at=2026-10-08T04:39:03Z
21:23:58.503 [auth] backend poll armed for 934s (intent ttl 904s)
21:23:58.508 [browser] open-in-profile: https://hydrogen.adom.inc/auth/intent?token=[redacted] in default:Default fresh=true
21:23:58.508 [caption] auth narration suppressed (assisted sign-in OFF): Opening the Adom sign-in in your default browser (Default)…
21:23:58.829 [browser] raised the opened window hwnd=786546 for the user -> true
21:23:58.830 [approve] assisted sign-in OFF, Adom auto-approve loop NOT armed; the user clicks Approve themselves
21:23:58.831 [browser] recorded consent window hwnd=786546 (direct open), so it can be raised and closed later
21:24:02.896 [auth] Intent authenticated, session token saved (+ replay copy)
21:24:02.896 [auth] Bringing HD to the foreground after Adom auth completion…
21:24:02.978 [auth] workspace not running, login token propagates on next start
21:24:03.095 [updater] signed-in user changed, checking now so the fleet ping carries who this is

4 Replies

John Lauer · 14d ago

Thanks for filing this, Gary, and sorry it cost you the time. The logs made the cause clear.

What happened: your Surface Laptop 7 has a Snapdragon X, which is an ARM processor. Hydrogen's Linux workspace (the "computer your AIs work in") is currently built only for Intel and AMD processors. On an ARM PC, Windows can import that workspace, but it can't run any of the programs inside it. That's the "imported, but not exec-able" line in your log, four times over. Nothing on your PC is broken, and there's nothing you could have done differently: Hydrogen just doesn't run on ARM PCs yet.

What we fixed:

Hydrogen was supposed to notice an ARM PC and say so up front, but Windows tells Hydrogen it's on an Intel/AMD machine (it runs Hydrogen through emulation), so that check never fired. The next build reads the real processor type, and setup stops right away with "Hydrogen doesn't run on ARM PCs yet" instead of trying four imports.
The import retries also had a bug that made attempts 3 and 4 fail with "a distribution with the supplied name already exists". That's fixed too.

What's next: you're the second person on a Snapdragon laptop to hit this, so we're looking at real ARM support: an ARM version of the workspace, with our tools either running natively or translated. We're setting up an ARM test machine now. I'll post here when there's something you can try.

John Lauer · 9d ago

Update, Gary: Hydrogen now supports ARM PCs. Since 1.0.580 it detects a Snapdragon (or any ARM) PC correctly and downloads an ARM64 build of the workspace instead of the Intel/AMD one.

We checked the detection and the ARM64 download on a Windows 11 ARM machine (1.0.597). We could not finish the run there because that test machine cannot run WSL2 at all, so your Surface Laptop 7 would be the first real ARM PC through the whole setup. If you're up for it, download the latest Hydrogen from the Hydrogen page (1.0.601) and run it; setup picks up where it stopped. Whatever happens, a reply here with what the screen says helps us a lot.

Gary Allen · 9d ago

Thank you for the response and clarification. I download again to test.

John Lauer · 3d ago

Gary, your Surface Laptop finished setup on Hydrogen 1.0.644 (October 18), and its workspace has reported healthy since, so I'm closing this. Your PC is the first Snapdragon machine to get all the way through, which tells us the ARM64 workspace works on real hardware. Thank you for running it again.

If anything stops or looks wrong, open a new issue from Hydrogen's Report button (it attaches the logs) or reply here.