You are not logged in.

#1 2025-07-08 08:33:46

angelnext
Member
From: Spain
Registered: 2023-08-06
Posts: 21

[SOLVED] Wine seems to be completely broken.

To my understanding Wine on Arch had a breaking change recently and this made my Wine completely unusable. Apps don't run (both 32bit and 64bit), and winecfg shows this output:

002c:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x6fffffc0db7f
wine: could not load kernel32.dll, status c0000135

wine 10.11-1
linux 6.15.5.arch1-1

Last edited by angelnext (2025-07-10 12:31:16)


If it's not broken, fix it.

Offline

#2 2025-07-08 10:39:14

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 13,962

Re: [SOLVED] Wine seems to be completely broken.

Since archlinux wine 10.8-2 package win32 prefixes are no longer supported.

The vast majority of win32 applications run fine in a win64 prefix though .

Does creating a new wineprefix work ?

env WINEPREFIX=~/.customprefix wineboot -u

Last edited by Lone_Wolf (2025-07-08 10:39:36)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#3 2025-07-08 10:45:03

jaero
Member
From: Bratislava, Slovakia
Registered: 2025-07-08
Posts: 1
Website

Re: [SOLVED] Wine seems to be completely broken.

Trying to resolve this for three days now. I have a small 1U game server and after updating wine got the same error, even with the same address, so it looks like it's not dependent on real library loading. I did not have wine on that server before, so I'm sure it's not solvable by the "clean prefix" solution presented on forums, based on last years WOW64 changes.
Just tried wine on my main computer after updating and result is the same, even on "real" processor and hardware and not crippled one smile

Offline

#4 2025-07-08 11:22:11

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 13,962

Re: [SOLVED] Wine seems to be completely broken.

The purpose of the command I posted is to verify basic functionality of the local wine installation.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#5 2025-07-08 16:48:29

angelnext
Member
From: Spain
Registered: 2023-08-06
Posts: 21

Re: [SOLVED] Wine seems to be completely broken.

Thx for the reply,  running Wine with a new prefix does not solve the problem, it still has the same error message, I've tried deleting default prefix and letting wine recreate it again to no solution.


If it's not broken, fix it.

Offline

#6 2025-07-09 10:53:49

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 13,962

Re: [SOLVED] Wine seems to be completely broken.

Please post the output of pacman -Qikk wine .

In case it says "0 altered files" :

create a fresh user for testing and perform minimal configuration.
can that user create a new wineprefix succesfully ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#7 2025-07-09 19:39:58

angelnext
Member
From: Spain
Registered: 2023-08-06
Posts: 21

Re: [SOLVED] Wine seems to be completely broken.

Hey, sorry for the late response, been very busy

Output of pacman -Qikk wine says:
wine: 3933 total files, 0 altered files

And creating a new user with minimal configuration has the same output as doing it on my personal user.


If it's not broken, fix it.

Offline

#8 2025-07-09 21:15:24

chaosmos
Member
Registered: 2025-07-09
Posts: 4

Re: [SOLVED] Wine seems to be completely broken.

Hey. Same situation here. I did everything described above with exactly the same results. Then I made a fresh install on a spare drive with exactly the same results. Then created a non-admin user on that new installation and performed everything again  - no results. Wine was working fine up until WoW64.
I just thought I'd let you know.


"The primary endgoal of wayland is to divide and stall progress of non-corpo desktops. And it's absolutely working."

Offline

#9 2025-07-09 23:00:36

angelnext
Member
From: Spain
Registered: 2023-08-06
Posts: 21

Re: [SOLVED] Wine seems to be completely broken.

Thx for the info, it's nice knowing I'm not the only person with this problem. Hope I find a solution sooner than later.


If it's not broken, fix it.

Offline

#10 2025-07-09 23:35:46

toz
Member
Registered: 2011-10-28
Posts: 508

Re: [SOLVED] Wine seems to be completely broken.

Maybe this bug? Fix to come in next update.

Offline

#11 2025-07-09 23:53:09

angelnext
Member
From: Spain
Registered: 2023-08-06
Posts: 21

Re: [SOLVED] Wine seems to be completely broken.

tried using the WINEDEBUG=+heap for winecfg to rebuild my wine profile and it just got stuck, it froze and i couldnt exit it in any way except by closing my terminal. It did show me the wine popup saying configuration is being updated, but that doesnt help cause when trying to run anything with wine it just gets stuck in that exact same way.

If this info helps I tried downgrading to wine 10.8-2 and that one works perfectly. But having to downgrade is only a temporary solution in my books, I'd like to reach the root of the problem and be able to use newer versions.

Last edited by angelnext (2025-07-10 00:26:54)


If it's not broken, fix it.

Offline

#12 2025-07-10 05:58:15

SimonJ
Member
From: Alicante, Spain
Registered: 2021-05-11
Posts: 264
Website

Re: [SOLVED] Wine seems to be completely broken.

Just to add, if you search there are already threads about this, some solved with wine-stable instead of wine. Others are holding the wine package hoping for a fix.

warning: wine: ignoring package upgrade (10.8-1 => 10.11-1)

Rlu: 222126

Offline

#13 2025-07-10 09:00:51

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 13,962

Re: [SOLVED] Wine seems to be completely broken.

If this info helps I tried downgrading to wine 10.8-2 and that one works perfectly.

Are you sure 10.8-2 works ?
If so, the change to wow64 / removal of win32 is not the cause as 10.8-2 is the first archlinux version that had that.

For clarity : Is wine 10.9-1 the first version that has this issue ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#14 2025-07-10 11:03:18

angelnext
Member
From: Spain
Registered: 2023-08-06
Posts: 21

Re: [SOLVED] Wine seems to be completely broken.

Yes, 10.8-2 works perfectly, even I was surprised considering this version already introduced WoW64 experimental mode, but when i try to upgrade to wine 10.9-1 it breaks in the same way as newer Wine versions


If it's not broken, fix it.

Offline

#15 2025-07-10 11:12:20

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 13,962

Re: [SOLVED] Wine seems to be completely broken.

That matches https://bbs.archlinux.org/viewtopic.php?id=306635 and the BR linkied by toz in #10 .

Please post the output of lscpu .

Last edited by Lone_Wolf (2025-07-10 11:13:54)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#16 2025-07-10 11:18:12

angelnext
Member
From: Spain
Registered: 2023-08-06
Posts: 21

Re: [SOLVED] Wine seems to be completely broken.

Architecture:                x86_64
  CPU op-mode(s):            32-bit, 64-bit
  Address sizes:             39 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) Pentium(R) Gold G6400T CPU @ 3.40GHz
    CPU family:              6
    Model:                   165
    Thread(s) per core:      2
    Core(s) per socket:      2
    Socket(s):               1
    Stepping:                3
    CPU(s) scaling MHz:      100%
    CPU max MHz:             3400.0000
    CPU min MHz:             800.0000
    BogoMIPS:                6799.81
    Flags:                   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xt
                             opology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave rdrand lahf_lm abm 3dnowp
                             refetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust smep erms invpcid mpx rdseed smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves 
                             dtherm arat pln pts hwp hwp_notify hwp_act_window hwp_epp vnmi md_clear flush_l1d arch_capabilities
Virtualization features:     
  Virtualization:            VT-x
Caches (sum of all):         
  L1d:                       64 KiB (2 instances)
  L1i:                       64 KiB (2 instances)
  L2:                        512 KiB (2 instances)
  L3:                        4 MiB (1 instance)
NUMA:                        
  NUMA node(s):              1
  NUMA node0 CPU(s):         0-3
Vulnerabilities:             
  Gather data sampling:      Not affected
  Ghostwrite:                Not affected
  Indirect target selection: Mitigation; Aligned branch/return thunks
  Itlb multihit:             KVM: Mitigation: Split huge pages
  L1tf:                      Not affected
  Mds:                       Not affected
  Meltdown:                  Not affected
  Mmio stale data:           Mitigation; Clear CPU buffers; SMT vulnerable
  Reg file data sampling:    Not affected
  Retbleed:                  Mitigation; Enhanced IBRS
  Spec rstack overflow:      Not affected
  Spec store bypass:         Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1:                Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:                Mitigation; Enhanced / Automatic IBRS; IBPB conditional; PBRSB-eIBRS SW sequence; BHI SW loop, KVM SW loop
  Srbds:                     Mitigation; Microcode
  Tsx async abort:           Not affected

And the CPU specifications, in case they're needed
https://www.intel.com/content/www/us/en … tions.html

Last edited by angelnext (2025-07-10 11:24:34)


If it's not broken, fix it.

Offline

#17 2025-07-10 12:13:53

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 13,962

Re: [SOLVED] Wine seems to be completely broken.

Yup, no avx support .

A fix has been merged to wine trunk and will be in the next release (10.12) .

If you want to test the fix before the release , you can build https://aur.archlinux.org/packages/wine-git which includes it.




(rhetorical question)
The first intel processor with avx was released in  2011, why would intel launch a proc without it in 2020 ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#18 2025-07-10 12:30:49

angelnext
Member
From: Spain
Registered: 2023-08-06
Posts: 21

Re: [SOLVED] Wine seems to be completely broken.

Thanks for the help! Would have never imagined my processor would be the culprit of the issue. I'm marking this as solved for now since it's a known bug.


If it's not broken, fix it.

Offline

#19 2025-07-10 13:16:04

Scimmia
Fellow
Registered: 2012-09-01
Posts: 12,892

Re: [SOLVED] Wine seems to be completely broken.

Lone_Wolf wrote:

(rhetorical question)
The first intel processor with avx was released in  2011, why would intel launch a proc without it in 2020 ?

Intel has a long history of doing things like this with low-end processors.

Offline

#20 2025-07-13 09:34:11

angelnext
Member
From: Spain
Registered: 2023-08-06
Posts: 21

Re: [SOLVED] Wine seems to be completely broken.

Wine 10.12 has released, I don't have access to my computer yet, can anybody confirm that it works for them when it didn't before?


If it's not broken, fix it.

Offline

#21 2025-07-13 11:58:45

voldemort
Member
Registered: 2025-07-10
Posts: 7

Re: [SOLVED] Wine seems to be completely broken.

angelnext wrote:

Wine 10.12 has released, I don't have access to my computer yet, can anybody confirm that it works for them when it didn't before?

Nope, I have updated but it still doesn't work

Offline

#22 2025-07-13 12:01:21

Scimmia
Fellow
Registered: 2012-09-01
Posts: 12,892

Re: [SOLVED] Wine seems to be completely broken.

voldemort wrote:
angelnext wrote:

Wine 10.12 has released, I don't have access to my computer yet, can anybody confirm that it works for them when it didn't before?

Nope, I have updated but it still doesn't work

And you had this exact issue on a CPU without AVX?

Offline

#23 2025-07-15 12:25:16

voldemort
Member
Registered: 2025-07-10
Posts: 7

Re: [SOLVED] Wine seems to be completely broken.

Scimmia wrote:
voldemort wrote:
angelnext wrote:

Wine 10.12 has released, I don't have access to my computer yet, can anybody confirm that it works for them when it didn't before?

Nope, I have updated but it still doesn't work

And you had this exact issue on a CPU without AVX?

Yep i have an Intel Pentium B960 CPU im pretty sure it doesnt have avx

Offline

#24 2025-07-15 17:44:41

chaosmos
Member
Registered: 2025-07-09
Posts: 4

Re: [SOLVED] Wine seems to be completely broken.

Can confirm, it does not work. Also no AVX support on that affected machine. 10.8.2. works (although with some problems - most probably unrelated).


"The primary endgoal of wayland is to divide and stall progress of non-corpo desktops. And it's absolutely working."

Offline

#25 2025-07-15 22:33:55

angelnext
Member
From: Spain
Registered: 2023-08-06
Posts: 21

Re: [SOLVED] Wine seems to be completely broken.

Hmmm, interesting, it does seem to work for me after updating to wine 10.12, maybe there's another factor causing issues? Is it the same kernel32.dll error or is it a different error?


If it's not broken, fix it.

Offline

Board footer

Powered by FluxBB