Windows VM Fails To Launch #14088

Activity

1. camdencarr84-jpg

   added

   bugSomething isn't workingSomething isn't working

   on Oct 2, 2026
2. jandrusk commented on Oct 6, 2026

   

   jandrusk

   on Oct 6, 2026

   More actions

   Thanks for reporting. "It worked once, now it won't launch" lines up with a few known Windows VM relaunch bugs, so a bit more detail would show which one this is:

   1. omarchy version (and channel: you mentioned RC)
   2. The exact output of omarchy-windows-vm launch from a terminal, start to finish
   3. ls -ld ~/Windows ~/.windows 2>/dev/null (setgid / mode on the shared folder)
   4. sudo docker ps -a --filter name=omarchy-windows and sudo docker logs --tail 50 omarchy-windows

   Likely candidates: #14196 / #11879 (setgid on the shared mount fails the 700 mode check on every launch after the first), #14119 (a false "Failed to start" when the VM is already running), and #9874 (mount-safety scan timeout on large disks).
3. camdencarr84-jpg commented on Oct 6, 2026

   

   camdencarr84-jpg

   on Oct 6, 2026

   Author

   More actions

   ~ ❯ omarchy version
   4.0.0.r6689.gb421b1b-1
   I used a patch for the script, so uh I'll run omarchy update for the next command

   ~ ❯ ls -ld ~/Windows ~/.windows 2>/dev/null
   Permissions Size User Date Modified Name
   drwx------ - camalam 2 Oct 12:10  /home/camalam/.windows
   drwxrwsrwx - camalam 6 Oct 11:32  /home/camalam/Windows

   ~ ❯

   ~ ❯ sudo docker ps -a --filter name=omarchy-windows
   [sudo] password for camalam:
   CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
   050f4498e356 dockurr/windows "/usr/bin/tini -s /r…" About a minute ago Up About a minute 127.0.0.1:3389->3389/tcp, 127.0.0.1:8006->8006/tcp, 127.0.0.1:3389->3389/udp omarchy-windows

   ~ ❯

   ~ ❯ sudo docker logs --tail 50 omarchy-windows
   ❯ Starting Windows for Docker v6.05...
   ❯ For support visit https://github.com/dockur/windows
   ❯ CPU: Intel Core i5 8365U | RAM: 6/16 GB | DISK: 67 GB (btrfs) | KERNEL: 7.2.7-arch1-1

   ❯ Warning: you are using the BTRFS filesystem for /storage, this might introduce issues with Windows Setup!

   ❯ Host: 172.18.0.2/16 (050f4498e356)
   ❯ Guest: 172.30.0.2 (Windows) | Mode: NAT | MAC: 02:33:2D:C4:A0:0F

   ❯ Warning: Your configured RAM_SIZE of 8 GB is too high for the 6.8 GB of free memory available, it will automatically be adjusted to a lower amount.
   ❯ Allocated 5.4 GB of RAM for Windows.
   ❯ Booting Windows using QEMU v11.1.0...

   BdsDxe: loading Boot0005 "Windows Boot Manager" from HD(1,GPT,B3BD9F6E-D438-4123-8E41-7E393DAA6653,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi
   BdsDxe: starting Boot0005 "Windows Boot Manager" from HD(1,GPT,B3BD9F6E-D438-4123-8E41-7E393DAA6653,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi

   ❯ Windows started successfully, visit http://127.0.0.1:8006/ to view the screen...

   ~ ❯
   the memory warning is because I have a bunch of stuff open and only 16gb ram.
4. jandrusk commented on Oct 7, 2026

   

   jandrusk

   on Oct 7, 2026

   More actions

   Thanks, that output is helpful. ~/Windows is drwxrwsrwx, i.e. setgid and world-writable. That's the #14196 / #11879 case: launch checks for an exact 700, so the setgid bit makes every launch after the first fail.

   Your build (4.0.0.r6689.gb421b1b, 09-29) predates #12323 (merged 10-04), which clears setgid when the directories are prepared. That only runs at install, though, so an existing directory keeps the bit. To fix it in place:

   chmod u=rwx,go=,a-s ~/Windows ~/.windows

   (A plain chmod 700 keeps the setgid bit on a directory, so the a-s matters.) Then try omarchy-windows-vm launch again without your script patch. If that works, this can be closed as a duplicate of #14196. If it doesn't, please paste the full launch output.
5. camdencarr84-jpg commented on Oct 8, 2026

   

   camdencarr84-jpg

   on Oct 8, 2026

   Author

   More actions

   The container starts. And the window opens! Closed as duplicate!
6. camdencarr84-jpg

   closed this as completedon Oct 8, 2026