Your Windows app installs fine, then dies at launch on your ARM64 machine, and the only clue is a message about unsupported CPU instructions. That is often AVX. A Phoronix headline says Wine 11.22 introduces x86 AVX emulation on ARM64, so the obvious question is whether your app just got fixed.
Does Wine on ARM64 support AVX now?
According to the headline, Wine 11.22, the latest bi-weekly development release, introduces x86 AVX emulation on ARM64. That is the only claim confirmed so far. How the emulation works, which setups it covers, and how fast it runs are all unconfirmed.
Those details belong in the official Wine 11.22 release notes on winehq.org, so read them before changing anything. Until you have, treat "AVX works" as "AVX emulation exists in a development build". It doesn't tell you that your specific app will launch.
What is AVX, and why do some apps need it on ARM64?
AVX (Advanced Vector Extensions) is an x86 instruction set extension that processes wide chunks of data at once. Games, media tools, and number-crunching software use it for physics, video, and similar heavy loops. Many programs check the CPU at startup. If AVX is missing, they either fall back to an older code path (SSE) or refuse to run.
An ARM64 chip has no x86 instructions at all. It has its own vector instructions, such as NEON. To run an x86 Windows program, something has to translate x86 code into ARM64 code on the fly. On Linux that is usually an emulator such as FEX or Box64 working alongside Wine.
Here is the catch. If the translation layer reports "no AVX", apps that need it crash or quit. If it claims AVX without translating the instructions correctly, the crash just comes later. A real fix needs both the translation and an honest report of what the emulated CPU can do.
What does Wine 11.22 add, and what is not confirmed?
Confirmed by the headline: AVX emulation for x86 code on ARM64 arrived in the 11.22 development release. Everything below is a gap to fill from the official release notes, not to guess at.
- Where the emulation lives. The Phoronix headline doesn't say whether it sits in Wine itself or depends on an external emulator.
- Which ARM64 setups are covered. Snapdragon X laptops, Ampere servers, Raspberry Pi-class boards and Asahi Macs are all unverified.
- AVX2 and AVX-512. These are separate extensions that some software requires, and the headline doesn't mention them.
- Performance and known bugs. No numbers or limits are confirmed.
Inference: if you already run FEX or Box64, check their own documentation and release notes for AVX behavior. Whichever layer does the translation determines what your app sees, and a Wine change may not override it. Nothing confirms how the two interact. We cover related ground in see also: check which radeon driver your old gpu uses on linux.
Should you try 11.22 or wait for 12.0 stable?
Wine 11.22 is inching toward the start of Wine 12.0 stable release preparations, per Phoronix. Development releases ship every two weeks and can break things between versions. That is normal for the development branch, so treat 11.22 as a test build.
Inference, based on how development branches work: if one specific app is blocked by AVX and you don't mind tinkering, test 11.22 in an isolated setup. If you play or work on this machine daily, wait for 12.0 stable and a round of user reports.
| Use case | Try 11.22 now? | Why | |---|---|---| | Gaming, one title blocked by AVX | Yes, in a separate prefix | Cheap to test, easy to discard | | Gaming, library already works | Wait for 12.0 | A dev build can regress games that run today | | Productivity or work apps | Wait for 12.0 | Stability matters more than one new feature | | Testing, bug reports, packaging | Yes | Reports on dev builds help shape the stable release |
How do I check that an AVX failure is fixed, and roll back if it breaks?
Start with prerequisites. You need an ARM64 Linux install, a way to get Wine 11.22 without overwriting your current Wine (your distro's package, a separate build, or a container), and the release notes open in a tab. Nothing confirms that your distro ships 11.22 for ARM64, so check your package manager first. All commands below are untested. For more on this, see a closer look at enable hdr in mpv on wayland: config, checks, fixes.
First, record your baseline (untested):
uname -m
wine --version
grep -c -w avx /proc/cpuinfo
Expect aarch64, your current Wine version, and a count of 0, because native ARM64 CPUs don't list x86 flags. That zero is normal and isn't what's being fixed. The real test is whether the app starts.
Second, reproduce the failure with the old Wine and save the log (untested):
WINEPREFIX=$HOME/prefix-old WINEDEBUG=err+all wine yourapp.exe 2>&1 | tee old.log
Third, install 11.22 in a separate location and run the same app in a fresh prefix, never your main one (untested):
WINEPREFIX=$HOME/prefix-1122 WINEDEBUG=err+all wine yourapp.exe 2>&1 | tee new.log
Verification: the app reaches its main window, and the crash or "unsupported CPU" message from old.log is gone from new.log. Run it for a while. A late crash can mean a half-working AVX path.
Also read: related topic: gimp flatpak vs snap vs appimage: which updates fastest?
Rollback: delete the test prefix with rm -rf $HOME/prefix-1122, remove the 11.22 package or directory, and reinstall your previous version through your package manager. If you pinned a version, unpin it first. Your original prefix was never touched, so it should still work. That is an expectation, not a tested result.
Does AVX emulation mean every AVX app will run fast on ARM64?
No, and the headline doesn't claim that. Emulating wide vector instructions costs speed. Check the release notes for any performance statements, since none are confirmed here.
AVX is also only one possible blocker. An app can still fail over missing graphics features, anti-cheat, launcher problems, or other instruction sets like AVX2. If your app crashes on 11.22 for a different reason, that is a separate bug. Compare the logs rather than assuming the new feature failed.



