While you're here, please consider supporting GamingOnLinux on:
Reward Tiers:
Patreon. Plain Donations: 
PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers:
Patreon. Plain Donations: PayPal.This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- Oh dear - ARC Raiders was logging your private Discord chats [updated]
- California law to require operating systems to check your age
- Ubuntu and Fedora devs comment on California's new Digital Age Assurance Act
- Here's the most played Steam Deck games for February 2026
- SteamInputDB is a new site to help you find Steam Input configurations for your gamepads
- > See more over 30 days here
How to setup OpenMW for modern Morrowind on Linux / SteamOS and Steam Deck
How to install Hollow Knight: Silksong mods on Linux, SteamOS and Steam DeckRecently Updated
Linux Distribution: Ubuntu 20.04 LTS
Desktop Environment: GNOME
Graphics Card: GeForce MX250
GPU Driver Version: 460.39
Have you checked for system updates?: Yes
You can note your issue below here
I am unable to run Windows "installers" using WINE (right-click "installer" file-->Open with WINE Windows Program Loader")... When I try to do so, I see an animated spinning icon for about fifteen (15) seconds, then nothing.
I did not have this problem until I accidentally installed "GOG Galaxy" for a particular game (and people actually want this garbage for Linux?)(I had downloaded the wrong "installer" and the one I did download installed "GOG Galaxy" first, before unsuccessfully attempting to install said game).
I have been working on this all day, and had no luck trying to fix it... I have completely "purged" / re-installed WINE multiple times, I have rebooted my system repeatedly, I have manually searched for files that appear to be related to WINE and then deleted them (emptying my "trash" in the process"), again whilst rebooting in between - no change.
So now I'm out of ideas... Any help would be appreciated.
Last edited by Cyba.Cowboy on 2 Apr 2021 at 6:27 am UTC
I had this problem as well and in KDE you have to make EXE associations to open with WINE FIRST on the list.
Last edited by wolfyrion on 2 Apr 2021 at 7:39 am UTC
You could test if this is the same problem by running one of these installers with wine64 instead of wine. If that works, either add a custom desktop launcher to your ~/.local/share/applications/ (you can base it on /usr/share/applications/wine.desktop), launch your installers from the command line, or simply revert to the previous Wine release for the time being.
No idea if launching with wine64 has any downsides. I don't use Wine very often.
Is it just the file association or is Wine broken in general? Does it work if you run "wine setup.exe" from a terminal?
I used this command and everything immediately ran fine / as expected:
wine 'setup_horizon_zero_dawntm_complete_edition_6278995_(64bit)_(44600).exe'When I removed said game, I also needed to do so via Terminal...
wine 'unins000.exe'This would suggest I am wrong, and it is in fact a file association issue, right? How do I fix that?
Last edited by Cyba.Cowboy on 2 Apr 2021 at 10:06 pm UTC
xdg-mime query filetype setup.exeWhich should return a mimetype, you can make another query for:
xdg-mime query default application/x-ms-dos-executableThis will most likely provide a .desktop file. Said file most likely lives in either /usr/share/applications/ or ~/.local/share/applications/ . I'm guessing the most likely culprit is in your home dir.
These are just regular text files, open it and see what the Exec field is set to.
Interesting, I have never seen those commands before. Always interesting to learn something new!
Their issue appears to be similar - though there are minor differences (for example, they're seeing error messages, which I am not)... Strangely, the bug is listed as being "resolved" over on the WINE Bugzilla.
Perhaps because - if my understanding of that "bug" is correct - this is actually a design flaw, due to a change in the way in which WINE now handles directory structures / file-paths (again, if my understanding is correct, WINE now uses Microsoft Windows directory structures / file-paths exclusively and does not recognize 'nix directory structures / file-paths)?