Wine not working following 2025-06-23 update

I would like to chime in here as I am facing the same issue. In my case this is a clean Manjaro installation (in which I completely broke the Windows dualboot but that is another problem).

After I installed Manjaro, I also installed Wine and winetricks. Running winecfg from the command line results in the same you posted.

wine: created the configuration directory '/home/user/.wine'
002c:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x6fffffc0daff
wine: could not load kernel32.dll, status c0000135

I have tried different prefixes but to no avail. The only thing that triggered me in this post is that you said you have an old CPU. That is the same in my case although it was running Windows 10 Home just fine.

Here is the output of inxi.

inxi -Fazy
System:
  Kernel: 6.12.34-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
    root=UUID=3a3fbacc-6cc7-49d0-9e22-75e8582812ef rw quiet splash
    udev.log_priority=3
  Desktop: KDE Plasma v: 6.3.5 tk: Qt v: N/A info: frameworks v: 6.15.0
    wm: kwin_x11 with: krunner vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: Gigabyte model: H81M-S2PH v: x.x
    serial: <superuser required> uuid: <superuser required>
    BIOS: American Megatrends v: F2 date: 08/05/2013
CPU:
  Info: model: Intel Pentium G3420 bits: 64 type: MCP arch: Haswell level: v2
    built: 2013-15 process: Intel 22nm family: 6 model-id: 0x3C (60) stepping: 3
    microcode: 0x28
  Topology: cpus: 1x dies: 1 clusters: 2 cores: 2 smt: <unsupported> cache:
    L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
    L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 2822 min/max: 800/3200 scaling: driver: intel_cpufreq
    governor: schedutil cores: 1: 2822 2: 2822 bogomips: 12774
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: disabled; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
    vendor: Gigabyte driver: i915 v: kernel arch: Gen-7.5 process: Intel 22nm
    built: 2013 ports: active: HDMI-A-1 empty: VGA-1 bus-ID: 00:02.0
    chip-ID: 8086:0402 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_x11 driver: X: loaded: modesetting alternate: fbdev,vesa
    dri: crocus gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.00x11.22")
    s-diag: 1055mm (41.54") monitors: <missing: xrandr>
  Monitor-1: HDMI-A-1 model: Philips PHL 499P9 serial: <filter> built: 2020
    res: 3840x1080 dpi: 82 gamma: 1.2 size: 1193x336mm (46.97x13.23")
    diag: 1239mm (48.8") modes: max: 3840x1080 min: 720x400
  API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus
    device: 1 drv: swrast gbm: drv: crocus surfaceless: drv: crocus x11:
    drv: crocus inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.1.4-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics (HSW GT1)
    device-ID: 8086:0402 memory: 1.46 GiB unified: yes
  API: Vulkan v: 1.4.313 layers: N/A device: 0 type: integrated-gpu
    name: Intel HD Graphics (HSW GT1) driver: mesa intel v: 25.1.4-arch1.1
    device-ID: 8086:0402 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo,xprop
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
    driver: snd_hda_intel v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c
    class-ID: 0403
  Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20
    class-ID: 0403
  API: ALSA v: k6.12.34-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.5 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Info: services: NetworkManager,systemd-timesyncd
Drives:
  Local Storage: total: 1.36 TiB used: 33.7 GiB (2.4%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10EZEX-08M2NA0
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: 1A01 scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 1B6Q scheme: MBR
Partition:
  ID-1: / raw-size: 313.58 GiB size: 307.59 GiB (98.09%) used: 33.7 GiB (11.0%)
    fs: ext4 dev: /dev/sdb3 maj-min: 8:19
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 66.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 8 GiB available: 7.65 GiB used: 5.93 GiB (77.6%)
  Processes: 185 Power: uptime: 15m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 3.04 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Packages: pm: pacman pkgs: 1356 libs: 399 tools: pamac pm: flatpak pkgs: 0
    Compilers: gcc: 15.1.1 Shell: Zsh v: 5.9 running-in: konsole inxi: 3.3.38

Is Wine not usable on this system perhaps?

Post found about that error message:

https://www.reddit.com/r/wine_gaming/comments/zacbyr/wine_completely_broken_wine_could_not_load/
https://medium.com/@rupesharma203/wine-could-not-load-kernel32-dll-status-c0000135-fc3c11ffa216
https://bbs.archlinux.org/viewtopic.php?id=299491
https://forum.winehq.org/viewtopic.php?t=36856

Hi Phil,

Thank you for your reply. I should have included those links in my post as I have seen and tried them all. None of them helped, as whenever I get to the point to run wine, it instantly returns the kernel32.dll error.

Well, some apps might not work with WOW64, as I mentioned earlier: Wine not working following 2025-06-23 update - #19 by philm More info here: WOW64 mode does not seem to work on anything - WineHQ Forums

Good idea, I tried it with another account that I use as a guest account and where there was no .wine folder, and the behavior is exactly the same.
For the record, on another machine with an I3, the new version of wine works perfectly…

I am also running an E5800 processor and having the identical problem you have. I followed your suggestion to downgrade wine to 10.7.1 which temporarily resolves the issue.

Three weeks since the initial post and further comment from the PO. The topic seems abandoned.
@solypse - If you have new information or have found a workaround in the meantime and would like the topic re-opened, please ask one of the Moderation staff (via PM).