https://gitlab.winehq.org/wine/wine/-/releases/wine-10.4
Improvements to PDB support in DbgHelp.
More Vulkan video decoder support in WineD3D.
Accessibility support in the SysLink control.
More progress on the Bluetooth driver.
Various bug fixes.
10.2
What's new in this release:
Bundled vkd3d upgraded to version 1.15. Support for setting thread priorities. New Wow64 mode can be enabled dynamically. More progress on the Bluetooth driver. Various bug fixes.
https://gitlab.winehq.org/wine/wine/-/releases/wine-10.2
Existing wine directories (WINEPREFIX) may not work after updating. Creating a new WINEPREFIX may be required.
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2025-8f3e54228bPlease login to add feedback.
| 0 | 1 | Test Case wine apps |
This update has been submitted for testing by mooninite.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
Works great! LGTM! =)
This update can be pushed to stable now if the maintainer wishes
$ winecfg wine: failed to load /usr/lib/wine/i386-windows/ntdll.dll error 4000000e 0024:err:environ:run_wineboot failed to start wineboot 1 0024:fixme:winediag:loader_init wine-staging 10.2 is a testing version containing experimental patches. 0024:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. wine: failed to load /usr/lib/wine/i386-windows/ntdll.dll error 4000000e wine: failed to load /usr/lib/wine/i386-windows/ntdll.dll error 4000000e 0024:err:win:get_desktop_window failed to start explorer 1 wine: failed to load /usr/lib/wine/i386-windows/ntdll.dll error 4000000e 0024:err:start:fatal_error FormatMessage failed
No problem after downgrading to 10.1
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Same issue as nucleo above
No issue after downgrading to 10.1 as well
It appears that upgrades of existing WINEPREFIX directories will not be fully compatible with 10.2. If someone wants to raise this with upstream please feel free, but I have not seen them care about compatibility. Also, the changes with wine-preloader and WOW64 now expect to default to the 64-bit wine binary on 64-bit hosts. Before it defaulted to the 32-bit wine binary. I will update the wine package to change the default, but to get 10.2-1 working you can run "alternatives --config wine" and change to the wine64 command. Some apps may run but you will still see some errors on existing WINEPREFIX directories. A fresh WINEPREFIX should work.
Wine 10.2 tries to be "smart" on 64-bit hosts. In order to run native 32-bit wine on a 64-bit host you must now explicitly define WINEARCH=win32. Wine now defaults to 64-bit wine without WINEARCH defined on 32-bit wine binaries. 10.1 and older defaulted to 32-bit wine with 32-bit binaries on 64-bit hosts.
Disregard my comment about WINEARCH. You need to set wineserver to the 32-bit binary. This can be done via "alternatives --config wineserver" and set it to wineserver32.
mooninite edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by mooninite.
So now it is impossible to run 32-bit and 64-bit exe from the same wine prefix at the same time?
This update has been pushed to testing.
Someone opened bug report for Ubuntu 24.04 LTS with the same issue on Wine bug tracker, we should do the same
https://bugs.winehq.org/show_bug.cgi?id=57859
@nucleo, no, you can run 32-bit apps within a 64-bit prefix as before. Upstream changed their loading architecture.
The 10.2-2 update will have the correct default settings, but it does not handle upgrades of existing systems. In order to do that I will have to force people on 64-bit systems to point to 64-bit wine and release a 10.2-3 update. If they want 32-bit wine they will have to override it after the update. It's not ideal but I think more people on 64-bit hosts would use WOW64 rather than 32-bit only.
I tried your 10.2-2 update and nothing will launch, but downgrading works.
These changes may be relevant/helpful: https://gitlab.archlinux.org/archlinux/packaging/packages/wine/-/commit/f7515923fefd0888aed7999e9a1d0f800b52e6c7
I'll try to take a closer look if that wouldn't help :/
Neither
WINEPREFIX=$(mktemp -d) wine mp3tagv328-x64-setup.exenorWINEPREFIX=$(mktemp -d) wine64 mp3tagv328-x64-setup.exestarts properly with this update. This new behavior is so bad that I believe something must be broken here...mooninite edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by mooninite.
@mooninite: Is there anything we need to do to have existing wine prefixes working with 10.2 builds?
I was trying to follow your instructions regarding "alternatives -config" but no luck.
Creating a new wineprefix is no option for me
Thx in advance
This update has been pushed to testing.
Hmm, I did try to backport 05315ce3da4d6f04232611fb5dd6ffbd77f87ce7 on top of wine-10.2-3.fc41, with no luck, and basically anything ending with:
wine: failed to load L"\??\C:\windows\syswow64\ntdll.dll" error c0000135
seems like this helps?
@luk1337: I checked this update thread again after some time hoping for a miracle... and here it is. You deserve a medal.
YES, it helped!
No need to recreate wine prefix etc., everything is running fine as before with existing wine prefix.
This update can be pushed to stable now if the maintainer wishes
Is it possible to add these symlinks to packages?
With wine-10.2-3.fc41 I can run winecfg and 64-bit exe but running 32-bit failed
Only after creating symlinks both 64-bit and 32-bit exe are running.
Bug upstream is reported as fixed now (in 10.3) so I created a scratch build for 41 https://koji.fedoraproject.org/koji/taskinfo?taskID=130607942 and it seems to be working. Haven't tested 42 yet, but it's being built here https://koji.fedoraproject.org/koji/taskinfo?taskID=130609419
mooninite edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by mooninite.
This update has been pushed to testing.
With wine-10.4-1.fc41 the same result, only 64-bit can run.
Sensitive apps are reporting that Windows Debugger is active with this version (10.4) and refusing to start:
"A debugger has been found running in your system please unload it from memory and restart your program "
No such issue with Wine 10.1 or 10.2
https://bugs.winehq.org/show_bug.cgi?id=57950
This update can be pushed to stable now if the maintainer wishes
mooninite edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by mooninite.
mooninite edited this update.
This update has been pushed to testing.
wine-10.4-2.fc41 adds symlinks and works for me both for 32-bit and 64-bit exe
This update can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by mooninite.
This update has been pushed to stable.