Vortex won't install using a Windows 10 32-bit Wineprefix

[Lockdown]

Hello (This is going to be a long one, so sorry in advance), so I been trying to install Vortex (Properly) through Steamtinkerlaunch, I will describe what process I went through in as much details as I can remember
So, assuming a fresh install, I would install Steamtinkerlaunch (From now on I will refer to it as STL) through pacman (As it’s stated in STL’s github it is recommended to install it through the package manager), then click on the “Vortex” section, click install, then select Proton-GE as my custom proton, after waiting a bit, it will give me an error saying that “Vortex 1.8 and above is not compatible with your operating system. Windows 10 or newer is required to run correctly. Click “retry” for troubleshooting steps (opens in browser). Click “ignore” to continue anyway”
Now a couple of things I’d like to point out, first, I did try to just click ignore and yes, Vortex does launch, seemingly, the UI can get buggy and it doesn’t detect any of the game (Nor have I managed to manually make it detect any), second and the main reason I made this post, I could not, for the life of me, force it to use a Windows 10 32bit Wineprefix no matter what I did, I made a Wineprefix using Winetricks, using the terminal, made sure 500 times with winecfg and “grep arch ~/.local/share/wineprefixes/win32/system.reg” and made sure that “#arch=” had “win32” at the end, despite that, it still gives me the same error, and if I run the install process “steamtinkerlaunch vortex install” through the konsole to debug, it gives me a bunch of stuff when it gets to the “installing dotnet” part but the main error is “warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.”, I tried a lot of workarounds for this and nothing seemed to work until I decided to nuke the “Registry info” that was at “/home/lockdown/.config/steamtinkerlaunch/vortex/compatdata/pfx/system.reg:#arch=win64”, and then re-create a new prefix using "WINEARCH=win32 WINEPREFIX=~/.config/steamtinkerlaunch/vortex/compatdata/pfx wineboot
", then I configured it was 32 using grep, and then steamtinkerlaunch vortex install, THIS TIME, it didn’t give me the konsole error of me using a 64 bit, however when it’s done installing it gives me the 1.8 version popup menu saying I am not on Windows 10 (Despite checking through my wine cfg and even setting it to Windows 11 just in case), at this point I decide to just ask here in the forums, to just confirm if what I am doing is wrong to begin with or if it’s just the way it is.
Garuda-inxi:

System:
Kernel: 6.14.10-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=b8f55436-6379-4c35-b08e-eb4d2e1c60d3 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.3.5 tk: Qt v: N/A info: frameworks v: 6.14.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME B450M-A v: Rev X.0x
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 2006 date: 11/13/2019
CPU:
Info: model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 gen: 2
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701034
Topology: cpus: 1x dies: 1 clusters: 1 cores: 6 threads: 12 tpc: 2
smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB
desc: 6x512 KiB L3: 32 MiB desc: 2x16 MiB
Speed (MHz): avg: 3594 min/max: 2200/4208 boost: enabled scaling:
driver: acpi-cpufreq governor: performance cores: 1: 3594 2: 3594 3: 3594
4: 3594 5: 3594 6: 3594 7: 3594 8: 3594 9: 3594 10: 3594 11: 3594 12: 3594
bogomips: 86238
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU116 [GeForce GTX 1660 SUPER] vendor: PNY driver: nvidia
v: 575.57.08 alternate: nouveau,nvidia_drm non-free: 550-570.xx+
status: current (as of 2025-04; EOL~2026-12-xx) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-2022 pcie: gen: 2 speed: 5 GT/s
lanes: 16 link-max: gen: 3 speed: 8 GT/s ports: active: none off: HDMI-A-1
empty: DP-1,DVI-D-1 bus-ID: 08:00.0 chip-ID: 10de:21c4 class-ID: 0300
Display: x11 server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 101 s-size: 483x272mm (19.02x10.71")
s-diag: 554mm (21.82")
Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled model: Samsung S22F350
serial: <filter> built: 2020 res: mode: 1920x1080 hz: 60 scale: 100% (1)
dpi: 102 gamma: 1.2 size: 477x268mm (18.78x10.55") diag: 547mm (21.5")
ratio: 16:9 modes: max: 1920x1080 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 575.57.08
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1660
SUPER/PCIe/SSE2 memory: 5.86 GiB
API: Vulkan v: 1.4.313 layers: 9 device: 0 type: discrete-gpu name: NVIDIA
GeForce GTX 1660 SUPER driver: nvidia v: 575.57.08 device-ID: 10de:21c4
surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl, nvidia-settings,
nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: NVIDIA TU116 High Definition Audio vendor: PNY
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 08:00.1 chip-ID: 10de:1aeb class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 0a:00.4 chip-ID: 1022:1487 class-ID: 0403
API: ALSA v: k6.14.10-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.4.5 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK RTL8111H driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 07:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp7s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Info: services: NetworkManager,systemd-timesyncd
Drives:
Local Storage: total: 476.94 GiB used: 402.72 GiB (84.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 model: SemsoTai SSD 512GB size: 476.94 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD
serial: <filter> fw-rev: XKR scheme: GPT
Partition:
ID-1: / raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 402.72 GiB (84.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 616 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 402.72 GiB (84.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 402.72 GiB (84.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 402.72 GiB (84.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.27 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 12
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 65.5 C mobo: 46.5 C gpu: nvidia temp: 49 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 32%
Info:
Memory: total: 32 GiB available: 31.27 GiB used: 9.07 GiB (29.0%)
Processes: 426 Power: uptime: 1h 45m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.42 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: 1723 pm: pacman pkgs: 1713 libs: 495 tools: octopi,paru
pm: flatpak pkgs: 10 Compilers: clang: 19.1.7 gcc: 15.1.1 Shell: garuda-inxi
default: fish v: 4.0.2 running-in: konsole inxi: 3.3.38
Garuda (2.7.2-1):
System install date:     2025-04-18
Last full system update: 2025-06-08 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:

[Jeshu]

Hi fellow Garuda user.

Please install vortex through Lutris it works fine in a wine prefix, install the Lutris version. By pressing on the + sign top left of Lutris main window and searching the lutris data base fro vortex. Update Vortex once you got it up and running.

Alternatively you can download the Vortex installer from the web. And then run the installer by creating a new wine game with the Lutris installer.

i have had Vortex up and running for years. Works great!

You can use bottles or playonlinux too!

Best of luck

[Lockdown]

I will try that then, thank you for the tip but I have to ask, is the one with Lutris just better than STL’s and is STL’s Vortex just unable to work on Garuda? Because I am still confused at this, as to why it did not want to work at all.

[Lockdown]

I tried, it still gave the same 2 errors I mentioned in my post about needing windows 10 or newer and in the Vortex logs it showed the 64bit thing, when running Vortex the UI is still buggy, and when trying to launch a game like 7 Days to Die it doesn’t launch, giving me a “failed to run tool” saying the executable doesn’t exist when it clearly does.

[Jeshu]

You may have to set the the window configuration to windows 10, it may be on windows 7 as default. The way to do this is to click on your game in Lutris, and then on the left side bottom of your Lutris window

on the platform windows tab and select wine configuration. When it opens select windows 10 . After doing that select your game once more and right click on its icon. Select configuration and then select game options and set the prefix architecture to 32 bit. Also make sure that under game info it has wine selected as runner. Otherwise the above solutions wont work, or even show up for you.

[Lockdown]

I see, thank you for the help but one small issue, I can’t seem to access that before already having the install finish, what I mean is that, when I go into the + sign, then search for the 2016 Vortex mod manager, and then I select the second option, it will start installing right away and would lead to the two errors, is there a workaround or a way in Lutris to have Vortex’s installer exist in my games section and I can edit the prefix before starting its installation process?

[Jeshu]

Maybe read the Vortex issue web page for more information. Personally i download the installer and choose - the window installer option - to install Vortex. Then i configure wine rightly before i run the installer.

Cheers.

[elite]

You might want to follow GitHub - Nexus-Mods/NexusMods.App: Home of the development of the Nexus Mods App as its the future app they are making and its for linux you can test the appimage in releases if you want to see if it will work for you.