If you’re trying to run Omarchy on VMware Workstation, you might be experiencing some issues with the GUI after what appears to be a successful installation.
With the basic graphics option configured on the virtual machine, Omarchy will boot but then fall to a black screen right after entering the password. Enabling accelerated graphics gets the GUI to load, but then appears unresponsive, failing to launch any menus or applications.
As I was experimenting with my own setup, I found this super useful blog highlighting the same issues along with a working fix:
https://tillnet.se/index.php/2025/10/17/omarchy-on-vmware/
Download Omarchy:
https://omarchy.org/
VM Configuration
I will be using VMware Workstation 25H2 and the following VM configuration:
- Guest Operating System: Linux (Other Linux 6.x kernel 64-bit)
- Memory: 16 GB
- Processors: 8, All virtualizaton engine features unchecked
- Hard Disk: 60 GB
- CD/DVD: Omarchy.iso
- Network: Bridged
- Sound Card: Not connected
- Display: Accelerate 3D Graphics Checked, 8GB graphics memory
Installation
Boot the iso image like normal, following all of the prompts. After the installation is complete, the operating system will boot, prompt for the password, and then login into what seems to be an unresponsive GUI.
- Press CTRL + ALT + F3 to switch over to a virtual terminal and login using the same credentials created during the install process.
-
Elevate to a root session:
$ sudo su
-
Update the local repository databases:
# pacman -Sy
-
Install open-vm-tools and make sure it starts with the system:
# pacman -S open-vm-tools # systemctl enable vmtoolsd
-
Edit the envs.conf file:
# nvim ~username/.config/hypr/envs.conf
Add the following line and save:
env = LIBGL_ALWAYS_SOFTWARE, 1
- Edit the monitors.conf file:
# nvim ~username/.config/hypr/monitors.conf
Add/edit the following lines:
env = GDK_SCALE,1 monitor=,1900x1050@60,auto,1
Note: If the resolution is allowed to match the max of the monitor, it seems to cause issues with the VMware console. Hard setting it with -30H and -20W seems to work well.
-
Reboot:
# systemctl reboot
Everything should now be working as expected!