Fix omarchy-windows-vm launch starting the container and never opening an RDP window
Confirmed on this machine, omarchy 4.0.2-1: /usr/share/omarchy/bin/omarchy-windows-vm is a symlink to /usr/bin/omarchy-windows-vm owned by omarchy 4.0.2-1, line 915 is the anchored wait docker logs --since "$started_at" "$CONTAINER" 2>&1 | grep -qi "windows started successfully", and lines 1441 to 1446 write $HOME/.config/windows/krb5.conf with dns_lookup_kdc = false and dns_lookup_realm = false and export KRB5_CONFIG. The version claim holds: I fetched bin/omarchy-windows-vm at the v4.0.0, v4.0.1, v4.0.2, v4.0.3 and quattro refs, and v4.0.0 has neither docker logs --since nor KRB5_CONFIG while every later ref has both. v4.0.2, v4.0.3 and quattro are byte-identical to the installed file, md5 b7827f13056a0e1132add721f71b66ec, so nothing about this changed in the 2026-09-08 release. I read omacom/omarchy#6882 in full with comments, and it supports the cause exactly, including the nine stale log matches, the roughly 30 second guest boot, the skipped wait on the already-running path, the ATHENA.MIT.EDU Kerberos hang measured at never versus 36 seconds, and davetist's credential-mismatch case. omacom/omarchy#6882 is closed as completed and omacom/omarchy#9515 is open with no comments, matching the record. Three things were wrong and I rewrote the fix. First, the manual workaround is broken as written: a plain omarchy-windows-vm launch whose RDP attempt fails runs docker-compose -f "$COMPOSE_FILE" down (line 351 of the v4.0.0 script, line 1464 onward in the installed one), which removes the container, so the following docker inspect returns nothing, $started is empty, and the until loop polls a container that no longer exists. The first launch has to pass --keep-alive. Second, the workaround stopped at the log line, which issue 9515 shows is about 9 seconds short of RDP being reachable, so I added the in-container guest port probe that issue 6882 recommends and the warning that probing 127.0.0.1:3389 on the host is useless because docker-proxy accepts regardless. Third, the credential advice was version-wrong: on 4.0.0 there is no ~/.config/windows/credentials at all and the launcher greps the compose file (lines 276 to 278 of the v4.0.0 script), while on 4.0.1 and later the private file wins and compose is only a readable fallback (lines 1399 to 1406 installed), so "the two must agree" is the wrong check in both cases and the rewrite labels each branch. I also named omacom/omarchy#5202, confirmed open, because it is what turns a too-early connection into a destroyed VM. Not exercised: Docker and a dockurr/windows container are not set up on this workstation, so I could not run omarchy-windows-vm launch, reproduce the stale-log match, time a guest boot, or test the dnsmasq lease and nc -z probe, which come from issue 6882's suggested fix rather than from a run here.
Symptom
omarchy-windows-vm launch starts the Docker container and exits without drawing a window. From the desktop entry, which runs with Terminal=false, nothing appears at all and no error is visible. Reported on Omarchy 4.0.0-1 with Docker 29.7.2, freerdp 2:3.30.0-2 and dockurr/windows v5.16.
It happens on a container that has been used before and not removed:
$ docker inspect omarchy-windows --format '{{.Created}} {{.State.StartedAt}}'
2026-08-13T14:49:54Z 2026-08-14T18:07:11Z
$ docker logs omarchy-windows 2>&1 | grep -ci "windows started successfully"
9
Cause
The readiness wait grepped the whole container log. docker logs keeps output across docker stop and docker start and is cleared only when the container is removed, so any container that has booted Windows once already contains a Windows started successfully line. The loop matched on its first iteration and xfreerdp3 ran about a second after docker compose up -d, while the guest was still in firmware. On the reporter's machine the guest needs about 30 seconds to reach that line, so the client fired roughly 29 seconds too early.
A second path had nothing to do with stale logs: when the container was already running the readiness wait was skipped outright, and dockurr/windows restarts the guest inside a running container whenever Windows reboots or shuts down.
Two other causes produce the same "container starts, nothing happens" symptom and are worth ruling out. FreeRDP 3 tries Kerberos before NTLM, and Arch's krb5 ships the upstream MIT sample /etc/krb5.conf with default_realm = ATHENA.MIT.EDU, so with no working internet each attempt blocked about 23 seconds and xfreerdp3 sat in CLOSE-WAIT drawing nothing. A contributor measured a stock config never connecting offline against 36 seconds with a realm-less one. And a second reporter's case was neither: their Compose credentials and ~/.config/windows/credentials had diverged and an auth-only check returned STATUS_LOGON_FAILURE.
Fix
**Update.** Both the readiness wait and the Kerberos hang are fixed in the shipped script from 4.0.1 onward. The v4.0.0 tag carries neither and v4.0.1 and later carry both.
omarchy update
Confirmed in the installed script on omarchy 4.0.2-1: the wait anchors the log scan to the container's current start time and now runs whether or not the container was already up, and the launcher writes its own realm-less Kerberos config and points KRB5_CONFIG at it before calling xfreerdp3:
grep -n 'docker logs --since' /usr/share/omarchy/bin/omarchy-windows-vm
grep -n 'KRB5_CONFIG' /usr/share/omarchy/bin/omarchy-windows-vm
**If you cannot update yet**, wait for the guest yourself rather than trusting the launcher, using the container's current start time so stale lines cannot match. Pass --keep-alive, because a plain launch runs docker-compose down as soon as xfreerdp3 exits, and that removes the container and leaves you nothing to inspect or poll:
omarchy-windows-vm launch --keep-alive # run it from a terminal, so freerdp's error is visible
started=$(docker inspect omarchy-windows --format '{{.State.StartedAt}}')
until docker logs --since "$started" omarchy-windows 2>&1 | grep -qi 'windows started successfully'; do sleep 2; done
guest=$(docker exec omarchy-windows awk '{print $3}' /var/lib/misc/dnsmasq.leases | head -1)
until docker exec omarchy-windows nc -z "$guest" 3389; do sleep 2; done
omarchy-windows-vm launch --keep-alive # the container is already up, so this connects straight away
The second loop matters because the log line means QEMU booted the guest, not that Windows is accepting RDP. Probe the guest from inside the container as above rather than 127.0.0.1:3389 on the host: docker-proxy accepts that connection whether or not the guest is listening.
**If the guest is up and the window still does not appear**, check the credentials rather than the timing. On 4.0.1 and later the launcher reads ~/.config/windows/credentials first and falls back to the compose file only when that file is readable, so the one that has to match the account inside Windows is ~/.config/windows/credentials. On 4.0.0 there is no such file and the launcher greps USERNAME and PASSWORD straight out of ~/.config/windows/docker-compose.yml. Either way a mismatch shows as STATUS_LOGON_FAILURE in the terminal output.
One residual defect is still open upstream and is not fixed in the newest release. omacom/omarchy#9515 reports the fixed wait returning about 9 seconds before the guest accepts RDP, so a launch can still connect too early, and omacom/omarchy#5202, also open, then tears the VM down when that client exits, which makes the next attempt another cold start. Launching with --keep-alive avoids the teardown so you can retry against a warm guest:
omarchy-windows-vm launch --keep-alive
Verify
grep -n 'docker logs --since' /usr/share/omarchy/bin/omarchy-windows-vm # the anchored wait is present
omarchy-windows-vm launch # from a terminal, an RDP window opens
Sources
- https://github.com/omacom/omarchy/issues/6882
- https://github.com/omacom/omarchy/issues/9515
- https://github.com/omacom/omarchy/issues/5202
- https://github.com/omacom/omarchy/blob/v4.0.0/bin/omarchy-windows-vm
- https://github.com/omacom/omarchy/blob/v4.0.1/bin/omarchy-windows-vm
- https://github.com/omacom/omarchy/blob/v4.0.3/bin/omarchy-windows-vm