Summary
lume create <name> --os macos --ipsw latest --unattended tahoe fails on macOS 26.4.1 because the tahoe preset clicks a Set Up Later button on the Apple Account / "Sign In to Your Apple Account" screen, but Apple renamed that button (very likely to Skip) in current Tahoe Setup Assistant. The same string appears a second time on the Screen Time screen.
The IPSW download and macOS installer both succeed. Failure is in the post-install Setup Assistant click-automation phase.
Repro
Host: macOS 26.4.1, Apple Silicon
lume: 0.3.9 (latest released, installed via official install.sh)
lume create test --os macos --ipsw latest --unattended tahoe
Failure log (relevant excerpt)
[INFO] macOS installation finished
[INFO] VM created successfully name=test
[INFO] Starting unattended Setup Assistant automation name=test
...
[INFO] Executing boot command command=wait for 'Email or Phone Number' (timeout: 120s) index=64/167
[INFO] Text found on screen text=Email or Phone Number
[INFO] Executing boot command command=delay 1.0s index=65/167
[INFO] Executing boot command command=click 'Set Up Later' index=66/167
[ERROR] Unattended setup failed error=Text 'Set Up Later' not found on screen after 0 seconds
[INFO] Cleaning up VM after failed unattended setup name=test
[ERROR] Error: Text 'Set Up Later' not found on screen after 0 seconds
Failed to create VM error=Text 'Set Up Later' not found on screen after 0 seconds
Where the broken text lives
libs/lume/src/Resources/unattended-presets/tahoe.yml:
- Line 111 — Apple Account / Sign In screen:
- "<wait 'Email or Phone Number'>"
- "<delay 1>"
- "<click 'Set Up Later'>"
- Line 161 — Screen Time screen:
- "<wait 'Screen Time'>"
- "<delay 1>"
- "<click 'Set Up Later'>"
Proposed fix
Apple's pattern in macOS 14+ has been to label the optional-skip action as Skip rather than Set Up Later on most Setup Assistant screens. Replacing both occurrences with Skip is likely a one-line fix per call site. Visual confirmation against the current macOS 26.4.1 IPSW would lock it in — happy to do that and submit a PR if a maintainer prefers, but flagging the issue first since the YAML is short and the change might be obvious to someone with Tahoe already open.
Side effect of failure
When unattended setup fails, lume cleans up by deleting disk.img but leaves the VM directory with config.json and nvram.bin behind. The remnant doesn't show up in lume ls (no disk = invisible), but persists on disk and is also unreachable via lume delete <name> (returns "Virtual machine not found"). Possibly worth a separate cleanup-on-failure check; let me know if you'd like that filed separately.
Related
Environment
- macOS 26.4.1 (host)
- Apple Silicon
- lume 0.3.9 (released March 27, 2026 per
lume-v0.3.9 tag)
- IPSW: latest auto-fetched (
UniversalMac_26.4.1_25E253_Restore.ipsw)
Summary
lume create <name> --os macos --ipsw latest --unattended tahoefails on macOS 26.4.1 because thetahoepreset clicks aSet Up Laterbutton on the Apple Account / "Sign In to Your Apple Account" screen, but Apple renamed that button (very likely toSkip) in current Tahoe Setup Assistant. The same string appears a second time on the Screen Time screen.The IPSW download and macOS installer both succeed. Failure is in the post-install Setup Assistant click-automation phase.
Repro
Host: macOS 26.4.1, Apple Silicon
lume: 0.3.9 (latest released, installed via official install.sh)
Failure log (relevant excerpt)
Where the broken text lives
libs/lume/src/Resources/unattended-presets/tahoe.yml:Proposed fix
Apple's pattern in macOS 14+ has been to label the optional-skip action as
Skiprather thanSet Up Lateron most Setup Assistant screens. Replacing both occurrences withSkipis likely a one-line fix per call site. Visual confirmation against the current macOS 26.4.1 IPSW would lock it in — happy to do that and submit a PR if a maintainer prefers, but flagging the issue first since the YAML is short and the change might be obvious to someone with Tahoe already open.Side effect of failure
When unattended setup fails, lume cleans up by deleting
disk.imgbut leaves the VM directory withconfig.jsonandnvram.binbehind. The remnant doesn't show up inlume ls(no disk = invisible), but persists on disk and is also unreachable vialume delete <name>(returns "Virtual machine not found"). Possibly worth a separate cleanup-on-failure check; let me know if you'd like that filed separately.Related
Environment
lume-v0.3.9tag)UniversalMac_26.4.1_25E253_Restore.ipsw)