Hi.
I always used Wine to play Outer Wild, without the heroic launcher or steam to use proton.
Today, wine doesn’t work. I didn’t changed anything. It worked well on heroic, but I lost my saves for outer wild. Even if outer wild doesn’t need that much saves, I like to use the ship’s log that depend of the saves.
Can someone help me please ? 
For instance, here what happens when I do ‘wine uninstaller’ :
[nath@nath-b550gamingxv2 ~]$ wine uninstaller
wine: Unhandled privileged instruction at address 000000000001400D (thread 0074), starting debugger...
0094:err:ole:start_rpcss Failed to start RpcSs service
009c:err:ole:start_rpcss Failed to start RpcSs service
009c:err:ole:start_rpcss Failed to start RpcSs service
0084:fixme:dbghelp:elf_search_auxv can't find symbol in module
0084:fixme:dbghelp:elf_search_auxv can't find symbol in module
003c:err:service:process_send_command service protocol error - failed to read pipe r = 0 count = 0!
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"CTIIO" failed to start: 1053
0100:err:seh:NtRaiseException Unhandled exception code c0000409 flags 1 addr 0x7fffff314147
003c:err:service:process_send_command service protocol error - failed to read pipe r = 0 count = 0!
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"AmdTools64" failed to start: 1053
0140:err:hid:udev_bus_init UDEV monitor creation failed
0124:fixme:wineusb:query_id Unhandled ID query type 0x5.
wine: could not load kernel32.dll, status c0000135
[nath@nath-b550gamingxv2 ~]$
I recently did an antivirus scan with clamTK, could this be the cause of my concerns?
Maybe we could start with what wine package it is exactly?
pacman -Qs wine
Here’s the output of your command :
[nath@nath-b550gamingxv2 ~]$ pacman -Qs wine
local/wine 10.12-1
A compatibility layer for running Windows programs
local/winetricks 20250102-1
Script to install various redistributable runtime libraries in Wine.
[nath@nath-b550gamingxv2 ~]$
iirc arch wine also does split package with 32 and 64 bit and now they only use wow64 for both version. rebuilding your wine from the start might fix it.
I recently had a problem with wine not working. I replaced wine 10.12-1 with wine-stable from the AUR. The packages I have installed are wine-stable, winetricks, wine-stable-mono, and wine-gecko. Everything is working again now. I think it’s something to do with 32-bit libraries.
I assume that you’ve got an AMD system ?
In terms of gaming in general, there is a meta package arch-gaming-meta within the AUR that should cover almost all bases. I’m not using it on my install as I’m totally fine with proton-ge-custom-bin instead of wine, steam and lutris. Lutris offers their own game-specific database of receipts. And could be also used in combination with steam. For non-gaming purpose, I’m using bottles as well.
Is [multilib] even included in your pacman.conf ?
Other than that, check those :
Within this forum: Linux gaming Guide
Discovery: Gaming-101
Discovery: Steam, Lutris & Wine
Arch Wiki: Gaming
Arch Wiki: Wine
And how am I supposed to do that ? I tried :
sudo pacman -R wine
and
sudo pacman -S wine
but it doesn’t work…
Yep.
I have a ryzen 5 5600X with a rx 6750xt.
I never used this package from the aur before… But wine always worked fine in the past.
I tried to delete some shortcut from the gnome app menu, maybe I made some mistakes and it’s related to it ?
I think my multilib is up to date yep :
[nath@nath-b550gamingxv2 ~]$ sudo pacman -Sy
[sudo] Mot de passe de nath :
:: Synchronisation des bases de données de paquets…
endeavouros est à jour
core est à jour
extra 7,9 MiB 50,7 MiB/s 00:00 [------------------------------------------] 100%
multilib est à jour
[nath@nath-b550gamingxv2 ~]$
Has this been something you use often?
Generally we dont have much of a good reason to run -Sy alone and it can lead to partial-upgrades.
Are you fully up to date?
sudo pacman -Syu
what it mean is you remove all traces of old wine sudo pacman -Rns wine include wine folder at home directory. if this doesnt work try the AUR version or try downgrading your wine to the version where they didnt implement wow64 by default. I believe it is 10.7-1 and below (not tested though)
I update regularly with the sudo pacman -Syu command, there are no issues with that normally
Here’s what I did :
-I made a save of my outer wild datas, so I copy paste the “SteamSaves” folder into my desktop. It was located into the wineprefix here : AppData/LocalLow/Mobius Digital/Outer Wilds
-I ran this command : sudo pacman -Rns wine winetricks
-I deleted the .wine folder into my home
-I ran sudo pacman -S wine winetricks
-I tried to launch outer wild, and it works !
-I replaced the wrong outer wild save folder with the new one
Thanks you very much for your help 
Packages in the repositories are built already .. there is nothing to rebuild … uninstalling the wine package and installing it again wont change anything (excepting in extremely rare circumstances like if dependencies were manually removed without checks .. so a reinstall would get those dependencies again).
If you needed to delete your local configs then you could do that .. but if you were already fully up to date the uninstall/reinstall did nothing for you there (and if you were not and had been using -Sy up til that point you could have created a partial-upgrade).
what if this is the exception it needs and it works with OP. still you have doubt..
“If you are facing issues with 32 bit prefixes, please recreate these and reinstall the application.”
Refers to the (win) application you are installing into the prefix.
Not the wine package.
If you were up to date then the files provided by wine will be exactly the same before and after you do some sort of package uninstall and install again.
I dont have much doubt.
They deleted the .wine folder .. that was what was needed.
The uninstall and install again of the package changed nothing.
(Again excepting rare circumstances, like if the system had manually been forced into a partial-upgrade state - in which case it may be possible the files would be slightly different after the exchange. But that would have been similarly remedied by just syncing up to date and still not require an uninstall/reinstall.)
The extra notes suggesting manual consideration
is mentioned specifically because packages should not add, remove, or modify paths in $HOME.
Therefor paths such as ~/.wine are the users responsibility and they may need to configure or recreate it as needed.