Failed to run Wine after update to 10.9

VLK · 2025-06-29 13:14:40

Hello everyone!

After updating Wine to 10.9, i can no longer launch it and getting an error. I deleted the .wine directory, but that didn't help. Today I tried updating the system from the testing repo to Wine 10.11, but the error is still there. Even when i running winecfg on a clean profile, i get the same error:

[test@VPCT ~]$ winecfg
wine: created the configuration directory '/home/test/.wine'
002c:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x6fffffc0daff
wine: could not load kernel32.dll, status c0000135

Thank you for any help.

P.S. Sorry for my english

Lone_Wolf · 2025-06-29 14:41:04

Repo wine on archlinux no longer supports 32-bit prefixes.

What is the output of

$ type winecfg
$ printenv WINEARCH

seth · 2025-06-29 14:48:12

Also the 3rd thread about this, https://bbs.archlinux.org/viewtopic.php?id=306627

VLK · 2025-06-29 14:53:36

Lone_Wolf wrote:

Repo wine on archlinux no longer supports 32-bit prefixes.
What is the output of
$ type winecfg
$ printenv WINEARCH

$ type winecfg
winecfg is hashed (/usr/bin/winecfg)
$ printenv WINEARCH
$

I have removed old .wine directory, but it didn't help. WINEARCH=win64 winecfg give the same error.

VLK · 2025-06-29 14:58:15

seth wrote:

Also the 3rd thread about this, https://bbs.archlinux.org/viewtopic.php?id=306627

I see, but there is no such errors. Downgrading to Wine 10.8 helped for now.

seth · 2025-06-29 15:15:16

Today I tried updating the system from the testing repo to Wine 10.11

Are you still running testing?
Did you activate *all* testing repos and update your system or did you only install wine from extra-testing?

Did you downgrade to 8.0-1 or 8.0-2 ?

Edit: maybe also post the complete environment

printenv

Last edited by seth (2025-06-29 15:16:11)

VLK · 2025-06-29 15:29:49

seth wrote:

Today I tried updating the system from the testing repo to Wine 10.11
Are you still running testing?
Did you activate *all* testing repos and update your system or did you only install wine from extra-testing?
Did you downgrade to 8.0-1 or 8.0-2 ?

I activated all test repositories and commented them out after the update. Downgraded to Wine 10.8-2, I'll wait for now, but I'll think about AUR wine32.

sudo pacman -U https://archive.archlinux.org/packages/w/wine/wine-10.8-2-x86_64.pkg.tar.zst

Of course, I wonder why my Wine 10.9 gave me such errors and how to avoid them in the future.

seth · 2025-06-29 15:35:39

https://wiki.archlinux.org/title/Offici … positories
You need to clean up after using the testing repos.

0.8-2 already has WOW64… https://gitlab.archlinux.org/archlinux/ … de4377ff22

VLK · 2025-06-29 15:43:20

seth wrote:

Today I tried updating the system from the testing repo to Wine 10.11
Edit: maybe also post the complete environment
printenv

SHELL=/bin/bash
SESSION_MANAGER=local/VPCT:@/tmp/.ICE-unix/1264,unix/VPCT:/tmp/.ICE-unix/1264
COLORTERM=truecolor
XDG_MENU_PREFIX=gnome-
LC_ADDRESS=ru_UA.UTF-8
LC_NAME=ru_UA.UTF-8
MEMORY_PRESSURE_WRITE=c29tZSAyMDAwMDAgMjAwMDAwMAA=
DESKTOP_SESSION=gnome
LC_MONETARY=ru_UA.UTF-8
EDITOR=nano
PWD=/home/vlk
LOGNAME=vlk
XDG_SESSION_DESKTOP=gnome
QT_QPA_PLATFORMTHEME=qt5ct:qt6ct
XDG_SESSION_TYPE=wayland
SYSTEMD_EXEC_PID=1282
XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.NJ2C92
MOTD_SHOWN=pam
GDM_LANG=en_US.UTF-8
HOME=/home/vlk
USERNAME=vlk
LC_PAPER=ru_UA.UTF-8
LANG=en_US.UTF-8
XDG_CURRENT_DESKTOP=GNOME
MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@wayland.service/memory.pressure
VTE_VERSION=8003
WAYLAND_DISPLAY=wayland-0
GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/8160c8b4_22b2_40bc_8d12_f9414f290e12
GNOME_SETUP_DISPLAY=:1
QT_WAYLAND_DECORATION=adwaita
XDG_SESSION_CLASS=user
TERM=xterm-256color
LC_IDENTIFICATION=ru_UA.UTF-8
USER=vlk
GNOME_TERMINAL_SERVICE=:1.83
DISPLAY=:0
SHLVL=1
LC_TELEPHONE=ru_UA.UTF-8
LC_MEASUREMENT=ru_UA.UTF-8
XDG_RUNTIME_DIR=/run/user/1000
DEBUGINFOD_URLS=https://debuginfod.archlinux.org 
LC_TIME=ru_UA.UTF-8
BROWSER=firefox
PATH=/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
GDMSESSION=gnome
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
MAIL=/var/spool/mail/vlk
LC_NUMERIC=ru_UA.UTF-8
_=/usr/bin/printenv

VLK · 2025-06-29 15:46:13

seth wrote:

https://wiki.archlinux.org/title/Offici … positories
You need to clean up after using the testing repos.
0.8-2 already has WOW64… https://gitlab.archlinux.org/archlinux/ … de4377ff22

Thank you for advice and information!

seth · 2025-06-29 15:52:38

The environment is unsuspicious.

https://bugs.winehq.org/show_bug.cgi?id=51596
https://bugs.freebsd.org/bugzilla/show_ … ?id=280000

lscpu

VLK · 2025-06-29 19:44:37

seth wrote:

The environment is unsuspicious.
https://bugs.winehq.org/show_bug.cgi?id=51596
https://bugs.freebsd.org/bugzilla/show_ … ?id=280000
lscpu

Architecture:                            x86_64
CPU op-mode(s):                          32-bit, 64-bit
Address sizes:                           42 bits physical, 48 bits virtual
Byte Order:                              Little Endian
CPU(s):                                  4
On-line CPU(s) list:                     0-3
Vendor ID:                               GenuineIntel
Model name:                              Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz
CPU family:                              6
Model:                                   23
Thread(s) per core:                      1
Core(s) per socket:                      4
Socket(s):                               1
Stepping:                                10
BogoMIPS:                                5683,47
Flags:                                   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ht syscall nx lm constant_tsc arch_perfmon pebs bts nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni ssse3 cx16 sse4_1 x2apic tsc_deadline_timer xsave hypervisor lahf_lm pti tsc_adjust dtherm
Hypervisor vendor:                       VMware
Virtualization type:                     full
L1d cache:                               128 KiB (4 instances)
L1i cache:                               128 KiB (4 instances)
L2 cache:                                6 MiB (1 instance)
NUMA node(s):                            1
NUMA node0 CPU(s):                       0-3
Vulnerability Gather data sampling:      Not affected
Vulnerability Indirect target selection: Mitigation; Aligned branch/return thunks
Vulnerability Itlb multihit:             KVM: Mitigation: VMX unsupported
Vulnerability L1tf:                      Mitigation; PTE Inversion
Vulnerability Mds:                       Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown
Vulnerability Meltdown:                  Mitigation; PTI
Vulnerability Mmio stale data:           Unknown: No mitigations
Vulnerability Reg file data sampling:    Not affected
Vulnerability Retbleed:                  Not affected
Vulnerability Spec rstack overflow:      Not affected
Vulnerability Spec store bypass:         Vulnerable
Vulnerability Spectre v1:                Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:                Mitigation; Retpolines; STIBP disabled; RSB filling; PBRSB-eIBRS Not affected; BHI Retpoline
Vulnerability Srbds:                     Not affected
Vulnerability Tsx async abort:           Not affected

Maybe try this builds later https://github.com/Kron4ek/Wine-Builds

Upd: Could VMWare be the problem? Everything was fine up until now. I can't install Arch on real hardware yet.

Last edited by VLK (2025-06-29 19:46:59)

seth · 2025-06-29 20:23:41

Upd: Could VMWare be the problem?

The listed bugs run into this because of CPU-related optimizations, so if this is anything to go by: "yes"
However,

Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz

this is indeed a Q9550 from 2008?
It's more likely to be the cause than the virtualization then.

julianmb · 2025-07-01 05:27:57

Having the same problem on an intel b960, a 2011 cpu, using a clean prefix. As others stated, downgrading to wine 10.8-2 works for now.

seth · 2025-07-01 06:58:43

This is on bare metal? Or vmware as well?
lscpu?
According to google™ it lacks Turbo Boost, HyperThreading, VT-x, VT-d, Trusted Execution, AES - makes me wonder whether wine depends on VT-x

VLK · 2025-07-01 07:41:33

seth wrote:

Upd: Could VMWare be the problem?
The listed bugs run into this because of CPU-related optimizations, so if this is anything to go by: "yes"
However,
Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz
this is indeed a Q9550 from 2008?
It's more likely to be the cause than the virtualization then.

I think you're right. It's a pity, but now I have to use such a computer. The links I found confirm this. Hope it will be fixed.

https://winehq.com/mailman3/hyperkitty/ … G67N5THF7/ (search: CPU)
https://bugs.winehq.org/show_bug.cgi?id=58335
https://forum.manjaro.org/t/wine-not-wo … e/179175/7

Last edited by VLK (2025-07-01 07:49:12)

seth · 2025-07-01 07:58:17

https://bugs.winehq.org/show_bug.cgi?id=58335#c45 has VT-x - the suspicion in ITT is the lack of AVX, ie. it's broken on everything < SandyBridge
Afaiu -mno-avx still exists, so AVX is optional and this is likely a bug in wine where some code unconditionally utilizes it.

julianmb · 2025-07-01 10:00:10

seth wrote:

This is on bare metal? Or vmware as well?
lscpu?
According to google™ it lacks Turbo Boost, HyperThreading, VT-x, VT-d, Trusted Execution, AES - makes me wonder whether wine depends on VT-x

This is on bare metal, this computer doesnt have vtx or any virtualization hardware:

lscpu:

Arquitectura:                            x86_64
  modo(s) de operación de las CPUs:      32-bit, 64-bit
  Tamaños de las direcciones:            36 bits physical, 48 bits virtual
  Orden de los bytes:                    Little Endian
CPU(s):                                  2
  Lista de la(s) CPU(s) en línea:        0,1
ID de fabricante:                        GenuineIntel
  Nombre del modelo:                     Intel(R) Pentium(R) CPU B960 @ 2.20GHz
    Familia de CPU:                      6
    Modelo:                              42
    Hilo(s) de procesamiento por núcleo: 1
    Núcleo(s) por «socket»:              2
    «Socket(s)»:                         1
    Revisión:                            7
    CPU(s) factor de escala MHz:         81%
    CPU MHz máx.:                        2200,0000
    CPU MHz mín.:                        800,0000
    BogoMIPS:                            4390,05
    Indicadores:                         fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall n
                                         x rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monit
                                         or ds_cpl est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave lahf_lm epb ssbd ibrs ibpb st
                                         ibp xsaveopt dtherm arat pln pts md_clear flush_l1d
Cachés (suma de todas):                  
  L1d:                                   64 KiB (2 instancias)
  L1i:                                   64 KiB (2 instancias)
  L2:                                    512 KiB (2 instancias)
  L3:                                    2 MiB (1 instancia)
NUMA:                                    
  Modo(s) NUMA:                          1
  CPU(s) del nodo NUMA 0:                0,1
Vulnerabilidades:                        
  Gather data sampling:                  Not affected
  Ghostwrite:                            Not affected
  Indirect target selection:             Not affected
  Itlb multihit:                         KVM: Mitigation: VMX unsupported
  L1tf:                                  Mitigation; PTE Inversion
  Mds:                                   Vulnerable; SMT disabled
  Meltdown:                              Vulnerable
  Mmio stale data:                       Unknown: No mitigations
  Old microcode:                         Not affected
  Reg file data sampling:                Not affected
  Retbleed:                              Not affected
  Spec rstack overflow:                  Not affected
  Spec store bypass:                     Vulnerable
  Spectre v1:                            Vulnerable: __user pointer sanitization and usercopy barriers only; no swapgs barriers
  Spectre v2:                            Vulnerable; IBPB: disabled; STIBP: disabled; PBRSB-eIBRS: Not affected; BHI: Not affected
  Srbds:                                 Not affected
  Tsx async abort:                       Not affected

seth · 2025-07-01 12:07:05

Nor AVX - pretty sure that is the cause here - either this is a bug or wine will have to announce to hard depend on AVX going forward.
But the upstream bug very much looks like an intention to fix this.

Arch Linux

#1 2025-06-29 13:14:40

Failed to run Wine after update to 10.9

#2 2025-06-29 14:41:04

Re: Failed to run Wine after update to 10.9

#3 2025-06-29 14:48:12

Re: Failed to run Wine after update to 10.9

#4 2025-06-29 14:53:36

Re: Failed to run Wine after update to 10.9

#5 2025-06-29 14:58:15

Re: Failed to run Wine after update to 10.9

#6 2025-06-29 15:15:16

Re: Failed to run Wine after update to 10.9

#7 2025-06-29 15:29:49

Re: Failed to run Wine after update to 10.9

#8 2025-06-29 15:35:39

Re: Failed to run Wine after update to 10.9

#9 2025-06-29 15:43:20

Re: Failed to run Wine after update to 10.9

#10 2025-06-29 15:46:13

Re: Failed to run Wine after update to 10.9

#11 2025-06-29 15:52:38

Re: Failed to run Wine after update to 10.9

#12 2025-06-29 19:44:37

Re: Failed to run Wine after update to 10.9

#13 2025-06-29 20:23:41

Re: Failed to run Wine after update to 10.9

#14 2025-07-01 05:27:57

Re: Failed to run Wine after update to 10.9

#15 2025-07-01 06:58:43

Re: Failed to run Wine after update to 10.9

#16 2025-07-01 07:41:33

Re: Failed to run Wine after update to 10.9

#17 2025-07-01 07:58:17

Re: Failed to run Wine after update to 10.9

#18 2025-07-01 10:00:10

Re: Failed to run Wine after update to 10.9

#19 2025-07-01 12:07:05

Re: Failed to run Wine after update to 10.9

Board footer