Wine 11 runs Windows apps in Linux and macOS better than ever
- Reference: 1768479995
- News link: https://www.theregister.co.uk/2026/01/15/wine_11_arrives_faster_and/
- Source link:
The Wine project delivered [1]Wine 11.0 Tuesday, very slightly less than one year after we [2]covered the release of Wine 10 .
Wine lets you run 16-bit, 32-bit, and 64-bit Windows x86 binaries on modern Unix and Unix-like OSes. This release eliminates the separation between 32-bit and 64-bit commands: it handles running 32-bit Windows binaries on 64-bit OSes internally.
[3]
Wine 11 on Ubuntu Questing, seamlessly running a mixture of 32-bit and 64-bit Windows apps - Click to enlarge
On Linux, this version supports the kernel's [4]NT synchronization primitive , or ntsync for short. This was [5]introduced in kernel 6.14 in March 2025, and it adds Windows-NT-compatible synchronization primitives to the Linux kernel, in addition to its native [6]futex() system call .
Linux's own methods work perfectly fine for native apps, but the Windows NT kernel has three different types of sync calls. Emulating those in userspace software is perfectly possible, but it's not very fast, so the new /dev/ntsync device offers fast, in-kernel NT-compatible calls, as [7]Linux Weekly News explained in detail in February 2024. It will still run on older kernels, just a little more slowly.
[8]
NTSync represents a fairly unusual sort of addition to the Linux kernel, as it brings no benefit to native Linux programs – it just improves the performance of Windows binaries running via Wine. As we [9]described back in 2023 , Valve's SteamOS is noticeably driving both the performance and compatibility of Windows programs on Linux in recent years. (Valve [10]released SteamOS 3.7.19 last week, and [11]new SteamOS hardware is coming "in early 2026".)
[12]
[13]
Natively, Wine is an x86 program itself, but it can run on non-x86 processors too. On Arm64 Linux, it can use [14]FEX-Emu for x86-to-Arm translation. A separate project called [15]Hangover combines Wine and FEX-Emu into one to let you install and run x86 Windows programs on Arm64 Linux. (It can also run Windows Arm64 binaries on x86-64 Linux, if you should want that for some strange reason.)
As we [16]mentioned when RHEL 9.2 came out , on Arm64 systems, changing the memory management page size is a compile-time option for the Linux kernel: you can't alter it on the fly. On Arm64, Wine 11 can work around this by simulating different page sizes.
[17]
On Macs, Wine 11 is an x86-64 program, but it runs on Apple Silicon Macs using [18]Rosetta 2 , meaning that it takes advantage of Apple's own highly-optimized x86-64 to Arm64 translation.
As of Wine 11, there are no longer separate wine32 and wine64 commands: there's just one wine command, and it works out what's needed for itself. Wine 11 no longer uses 32-bit support libraries. That means that on OSes which still offer 32-bit libraries, like most mainstream Linuxes ( [19]including Fedora , at least for now) Wine 11 is smaller than before – but it also means that it works on OSes that have removed 32-bit library support. This is nothing new for macOS, but it's helpful for distros such as [20]openSUSE Leap 16 which have dropped the old binary format.
As in the previous version, Wine 11 will output natively over Wayland if it's available, but now it can handle the clipboard on Wayland, too. It still works with X11, though, and now natively handles things like switching into full-screen mode. Direct3D support has been improved, and Wine 11 can use native Vulkan video decoding of H.264 video. There's improved handling of SCSI, scanning, joysticks and gamepads, including force-feedback, plus lots more less-apparent changes.
[21]
Wine 11 downloads are available [22]for Linux and [23]Apple macOS now, and although the [24]FreeBSD port is still on version 10 for the time being, the new version should make its way there too.
[25]Three ways to run Windows apps on a Linux box
[26]What if Linux ran Windows… and meant it? Meet Loss32
[27]What the Linux desktop really needs to challenge Windows
[28]How and why Linux has thrived after three decades in Kernelland
We tried the official version 11.0 wine-stable packages on the latest Ubuntu 25.10 under GNOME using Wayland. It worked fine, and we were able to install and run the 32-bit Microsoft Word Viewer and Microsoft Excel viewer from the [29]Legacy Update download center . We also grabbed the latest 64-bit version of [30]our favorite image viewer IrfanView , and it installed and ran first time.
We did notice that the WineHQ packages installed into /opt/wine-stable and didn't add symlinks to /usr/bin or insert itself into the shell's path. We had to do that by hand, then apps launched seamlessly.
If this sounds like too much tech-nerdery, that is perfectly fine. As The Register has done repeatedly [31]since at least 2002 , we recommend Codeweavers' excellent [32]Crossover tool as an easier and more compatible alternative. We can't really talk about the gaming experience, but we'd suggest starting by [33]installing Steam .
Wine makes this significant tech wizardry seem quite routine and easy these days. It's not perfect – for instance, we don't yet know of a way to install apps from the Microsoft Store – but it's very impressive. Although it took 15 years to get to version 1.0, the project now releases new major versions annually and the focus is moving from basic compatibility to integration and performance. It's real, it's ready, it works, and it's free – and of course, you don't need a Windows license. ®
Get our [34]Tech Resources
[1] https://gitlab.winehq.org/wine/wine/-/releases/wine-11.0
[2] https://www.theregister.com/2025/01/24/wine_turns_10/
[3] https://regmedia.co.uk/2026/01/14/wine-11.jpg
[4] https://docs.kernel.org/userspace-api/ntsync.html
[5] https://www.theregister.com/2025/03/25/linux_6_14_day_late/
[6] https://man7.org/linux/man-pages/man2/futex.2.html
[7] https://lwn.net/Articles/961884/
[8] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aWlxmVep7AKPD7pP5gdJ_QAAAA0&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[9] https://www.theregister.com/2023/09/27/osseu_steam_os_3/
[10] https://steamcommunity.com/games/1675200/announcements/detail/500594947381002242
[11] https://www.theregister.com/2025/11/14/valve_steam_kit/
[12] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aWlxmVep7AKPD7pP5gdJ_QAAAA0&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[13] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aWlxmVep7AKPD7pP5gdJ_QAAAA0&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[14] https://fex-emu.com/
[15] https://github.com/AndreRH/hangover
[16] https://www.theregister.com/2023/05/19/rhel_92/
[17] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aWlxmVep7AKPD7pP5gdJ_QAAAA0&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[18] https://support.apple.com/en-us/102527
[19] https://www.theregister.com/2025/07/01/fedora_43_i686_32bit/
[20] https://www.theregister.com/2025/08/07/opensuse_leap_16_reaches_rc/
[21] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aWlxmVep7AKPD7pP5gdJ_QAAAA0&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[22] https://gitlab.winehq.org/wine/wine/-/wikis/Download
[23] https://gitlab.winehq.org/wine/wine/-/wikis/MacOS
[24] https://www.freshports.org/emulators/wine/
[25] https://www.theregister.com/2025/05/28/three_ways_to_win_on_lin/
[26] https://www.theregister.com/2026/01/06/loss32_crazy_or_inspired/
[27] https://www.theregister.com/2025/12/22/what_linux_desktop_really_needs/
[28] https://www.theregister.com/2025/09/18/three_decades_in_of_linux/
[29] https://www.theregister.com/2025/12/11/legacy_update_update/
[30] https://www.theregister.com/2025/12/25/go_foss_keep_your_os/
[31] https://www.theregister.com/2002/04/16/running_msoffice_on_linux/
[32] https://www.codeweavers.com/crossover
[33] https://repo.steampowered.com/steam/
[34] https://whitepapers.theregister.com/
Came here to ask just that. Running Word smoothly in Wine is what would make using a Linux distro on my day-to-day desktop viable for me. (And don't tell me to run LibreOffice – I like it well enough, but even 99.97% compatibility wouldn't be enough for my use case – sadly it just has to be Word or my clients will have problems sooner rather than later [formatting, comments, tracked changes, etc.].)
You have the option to run Office through the web, (with monthly subscription and an active Internet connection so they can harvest your rich creamy data.)
For a local install, get LibreOffice. Private, free and can save in Office file formats.
If running actual Word / Excel is a must, then Win 11 / 12 / 13 / 14 ad nauseum is your life until your final logoff and you are stuck in the MS hamster wheel.
The web versions of Office are shit compared to the installed ones, and the files need to be saved to Microsoft's cloudy storage.
It's really bizarre the way the Linux faithful seem to almost take offence that anyone might need to run MS Office, and downvote anyone pointing this out. Will they ever come to understand that not everyone lives in their bubble and business realities dictate what software some people need to run?
And Libre Office is not an adequate substitute if sharing complex documents / spreadsheets - there are too many circumstances where full compatibility cannot be guaranteed. The post to which the one above was responding even specifically pointed this out but was clearly ignored.
What?
microsoft, and maybe your clients, are the problem here, not linux or its fanboys.
"The post to which the one above was responding even specifically pointed this out but was clearly ignored."
It wasn't ignored, the reply stated that you're stuck on the ms hamster wheel.
The free software people aren't going to all this trouble to create ms compatibility, then stopping 1 inch short of the end just to be cunts. That last 1 inch is clearly very difficult / impossible. Whose fault do you think that is?
How much have you paid for linux? I have my frustrations with linux, but I've paid nothing for any of it, so I just have to live with it as it is, and occasionally let off a bit of steam here.
Re: What?
The free software people aren't going to all this trouble to create ms compatibility, then stopping 1 inch short of the end just to be
It is not simply a matter of compatibility. Equation editing is not compatible between MS Word and LibreOffice, for whatever reason, but is also far, far better in Word, not least because you can enter LaTeX. Of course LaTeX itself is better still.
LibreOffice is more compatible with Word, than Word 365 is compatible with Word.
From bitter experience ... trying to edit documents with equations in them on both LibreOffice and MS Office Just Does Not Work. And Office 365 doesn't offer equation editing at all. For that reason alone I had to get a Windows laptop from $FORMER_WORKPLACE alas.
Any company running "Excel databases" dreads updating to modern versions of Office anyway.
Using excel as a database seems even more of a weird way to have done something when MS Office business editions (even the small business one) came with Access, which despite being....well.....sub optimal was still an actual database and not a spreadsheet being misused.
I'm reminded of this (obligatory) XKCD webcomic
https://xkcd.com/763/
Access seems to be pretty much abandonware at this point though.
Gaming is the Key
If WINE can run games seamlessly, then most other Windows applications will work as well, because gaming represents the most complex and demanding side of Windows computing. PC gaming is uniquely challenging on Linux since the ecosystem was built around Windows from the ground up: DirectX is Windows-only and must be translated through compatibility layers, many multiplayer titles rely on Windows-first anti-cheat systems that block or ignore Linux entirely, and GPU drivers—especially for new hardware and features—are typically optimized for Windows first, with Linux support arriving later or with compromises.
Nail gaming on Linux and the rest falls into line (barring active measures to block you from the OS vendors, of course.)
Re: Gaming is the Key
I swapped over maybe six months ago to Bazzite.
I haven't run into any Steam games that have outright failed yet...but to be fair I have not gone through my whole library to test each. Some are pretty intensive and work just like they did on Windows 10 (or better as I used to have to shut of real time scanning from Defender to prevent stuttering)
I run Heroic for my Epic games library and all of those work so far but once again I have not ground through the library to check them all.
I run the EA App through Bottles and it works fine for the old games I actually own on there including an old BF game.
Blizzard is supposed to work in Bottles but I have not had luck with that, so I installed their app under Steam and it works great for all my games.
If your game runs Vulkan I find it will run way better than DX11 or 12.
Kernel level anti-cheat has no place on any computer I own, though others don't care so that is definitely a nope for functionality on Linux.
Office productivity etc. is still a gap for sure.
I don't run MS Office anymore and have lived with the online versions for my customers which is navigable but not as full featured as local clients like you mentioned. I would hazard they should work under Bottles or one of the other translators?
DaVinci Resolve is one I hear mentioned a lot, they had a Linux version but there are issues with the licensed formats, encoders etc. and the Windows version will not emulate yet.
Adobe has a quite a few products are also problematic (at least from what I hear)
The only current workarounds for those is a VM or moving to a similarish Linux based app. which means re-learning from scratch something you have been doing your whole career in some cases.
Anyway, for me its fine but there are definitely a lot of gaps from just walking away from your Windows install.
In my experience: Windows chews RAM, Linux chews CPU.
I honestly thought I would miss Windows a lot more since I have been using it for a very very long time.
In fact I still have my Windows 10 partition "just in case", but I have resisted so far and will for a while since I don't want to spend half my day patching it haha.
TLDR - Works for a lot of games barring ones with kernel anti-cheat. Works ok for basic office productivity, with MS Office online being a work around. Works not so well for big vendor creative applications. Its not as bad as I thought it would be.
Crossover seems to be able to run Office 2016, at least:
https://www.omgubuntu.co.uk/2025/08/crossover-25-1-0-released-office-gaming-fixes
https://www.codeweavers.com/crossover#linux
IrfanView was the very first application I ran under WINE, back in 1999(?)
I remember only being able to run Notepad in very old versions of Wine without problems, we have come a long way.
"but still doesn't use the Microsoft store"
That part of the subheading should begin with "and" as it's a pro, not a con.
Microsoft's response?
I imagine Microsoft has kept a wary eye on Wine since Wine's inception.
Presumably, try as they might, Microsoft's lawyers cannot devise credible arguments that Wine infringes Microsoft 'rights' under copyright, patent, or trademark law; that despite the USA being the global hub for rentier economics. Even if they could sustain an argument in court, the enforcement of a restrictive ruling globally would be nigh on impossible. However, at present, Wine offers a negligible threat to Microsoft's hegemony in the business and educational markets.
Recent versions of Wine have become more simple to deploy, and they produce timely and trustworthy output. Seamlessly, they enable the use of many gargantuan (bloated?) software suites. Given the number of trustworthy suppliers of unfettered software, buccaneers have plenty to fill gaps in Linux provision. Also, even should a Windows program be stuffed with 'nasties', prudent Linux users easily circumvent them.
As for 'Microsoft Store', who needs it when unofficial sources for such components as are deemed worth having abound?
Re: Microsoft's response?
If MS really, really wanted it could engineer apps like Office to fail miserably when they detect wine running.
but so far, they don't and long may that remain. They (MS) seem to be hell bent on adding AI to everything even if it does not need it.
The more 'Donald Trump Fingers' that can be given to MS the better in my mind.
Re: Microsoft's response?
You cannot run any recent versions of MS Office under Wine, so far as I am aware (with the caveat that I've not tested with the most recent version of Wine)..
Re: Microsoft's response?
Last time I looked, it couldn't run anything later than Office 2003. It seems to have improved slightly since then, but nevertheless, you will be better off running LibreOffice than any of the versions of MS Office that Wine can cope with, even if LibreOffice can't replace the latest versions of MS Office.
Re: Microsoft's response?
I would assume that Microsoft's response is that "Office™ isn't done until Wine doesn't run (it)".
[1]In some of my code, I've checked to see if if it was running under Wine so that it could behave differently. Usually, as in the linked example, it's because there's some bits or bobs of the Win32 API that don't work identically in Wine and "real" Windows. I'm sure that if the threat from Wine was sufficiently serious, Microsoft could fairly trivially modify their applications to break when not run on Genuine Windows®.
(I am a serious fanboy for Wine. It's saved me the effort of porting several programs to Linux or OS/X or *BSD. At most, I had to tweak them -- as above -- to duck around some limitation in Wine. And note that the above example references Wines 1.7.18 and 7.0.1; I would be surprised if many of those limitations still existed in Wine 11.)
[1] https://github.com/Bill-Gray/PDCursesMod/blob/master/wingui/pdcscrn.c#L1206
Re: Microsoft's response?
> Presumably, try as they might, Microsoft's lawyers cannot devise credible arguments that Wine infringes Microsoft 'rights' under copyright, patent, or trademark law; that despite the USA being the global hub for rentier economics
No, but they could probably try to argue that Wine allows for running programs that enable people to look at pictures of "women and children naked".
Might be enough!
Re: Microsoft's response?
Grok allows people to look at pictures of "women and children naked"...
Re: Microsoft's response?
> Presumably, try as they might, Microsoft's lawyers cannot devise credible arguments that Wine infringes Microsoft 'rights' under copyright, patent, or trademark law;
Agreed.
But then if you look at the history, WINE is a 32-bit FOSS recreation of SUN WABI:
https://en.wikipedia.org/wiki/Wabi_(software)
https://web.archive.org/web/19990824175632/http://sun.com/solaris/wabi/%3B$sessionid$510WNTIAAV2X3AMUVFZE45UBSSUXEUDO
Caldera gave me an eval copy of WABI for Linux and it ran Office 4.3 on Caldera OpenLinux very well.
https://everythinglinux.org/wabi/index.html
Screenshots etc:
https://virtuallyfun.com/2020/11/11/fun-with-caldera-wabi/
Sun proposed formally standardising and publishing the Win16 API:
https://dl.acm.org/doi/10.1145/234999.235003
It nearly happened.
Since MS-DOS was written as an independent implementation of the published DR CP/M API, it is a scary precedent for MS...
Mine updated yesterday
Only tested on Notepad++ so far
Re: Mine updated yesterday
So did mine, and thus far I've only tested it on Calvin Tucker's Redneck: Farm Animals Racing Tournament, which worked flawlessly
Re: Mine updated yesterday
Why do I find the name of that game so intriguing?
Hardware Support?
The primary requirement for Windows that I have to deal with is niche USB hardware. The manufacturer provides suitable USB device drivers, and their interface software uses the AccessDB file format (this makes it fairly simple to talk to from other software).
Does WINE support driving USB devices?
Does it support the AccessDB underpinnings (OLEDB/ODBC)?
Re: Hardware Support?
True dat. I keep a Virtualbox Win10 image for setting up USB audio devices since 'class compliant' is a generous term...but also need an old XP laptop as that's that last time Firewire drivers were released for the ProFire 2626!
Irony
WINE is getting better all the time. Ironically, it will probably achieve perfection around the same time the Windows monopoly finally collapses and we don't need it anymore.
Re: Irony
Wine Is No longer Essential?
Wine 11.0 Tuesday
WTF is that?
Re: Wine 11.0 Tuesday
> Wine 11.0 Tuesday
> WTF is that?
You excerpted a sentence fragment. In full it says:
«
The Wine project delivered Wine 11.0 Tuesday
»
That means "the WINE Project delivered version 11.0 on Tuesday."
What I originally wrote was:
«
The Wine project delivered Wine 11.0 yesterday (as we write)
»
... but it didn't run until Thursday. So, it got edited, and ended up a little less clear.
Re: Wine 11.0 Tuesday
In the rewrite it also gained, dare I say, an Americanism.
“Delivered [X] Tuesday” versus the (to me, at least) British construction, “delivered [x] on Tuesday”.
Re: Wine 11.0 Tuesday
Why does this esteemed organ waste time and money editing perfectly good text into nonsense? Even if it must be changed to the day (not that it would make any difference within a few days), [1]American English allows for "on" for clarity before days and dates .
[1] https://www.quickanddirtytips.com/articles/do-you-use-on-with-days-and-dates/
If you really need MS Office, you should probably pay for a license and a licensed copy of Windows. If you prefer Linux then you can probably run your legit Windows on a VM.
Do MS Office fan boys see any compatibility issues between Mac and Windows versions? I seem to recall some compatibility niggles when I had no choice but to use MS Office.
For my use cases, the Office web versions, Google Docs and Libra office serve me well.
WINE is great for Adobe Digital Editions and a few other niche apps that are useful to me
"If you really need MS Office, you should probably pay for a license and a licensed copy of Windows."
I think for many it would be extra issues that Windows presents that would be the sticking point: the slurping, the intrusions of AI, the system breaking updates....
So don't use Office then. Tell your clients why you are taking that position.
> If you really need MS Office, you should probably pay for a license and a licensed copy of Windows.
Why?
The superficial unconsidered answer is "apps run better on the real OS and so it's better to run it if you can" but that falls down on deeper inspection.
There's no _legal_ requirement -- run them on whatever you can -- and if WINE works well enough, it offers 3 main categories of advantages:
[1] It integrates better: apps can see the Linux filesystem, Linux apps can access Windows files (e.g. you can open email attachments or downloads, and directly attach and send files from Windows apps); cut and paste works in both directions.
[2] There is no need for VMs, isolation, setting up comms and integration between emulated virtual environment and host; apps run at full native resolution on the native display, etc.
[3] There is no separate Windows OS in need of licensing, updates, virus protection, and other continued maintenance.
Triple win.
I use both methods, but if a given app works under WINE, that's the preferable method. It starts quicker, runs quicker, it uses _much_ less RAM and disk, and it integrates better.
I've recently been forced to use Word and Excel on a Mac (the web versions wouldn't cut it) and they're still dodgy - there's definitely minor compatibility niggles. Almost certainly deliberate by MS. They're scum, their nefarious tactics over the last 30 years make what VW did with the diesel-defeat scandal look like child's play.
Do MS Office fan boys see any compatibility issues between Mac and Windows versions? I seem to recall some compatibility niggles when I had no choice but to use MS Office.
If you have any serious questions, I suggest that you not use the gratuitous insult.
Powerquery on Excel isn't anything like as feature-complete on Mac as it is on Windows.
I know that a lot of companies still see Linux as too small a market on the desktop to warrant a native Linux port of their apps. But it would be nice if they could at least test and tweak their Windows builds to work under WINE and well as Windows. As although im no dev im sure it wouldn't be a massive amount of work to do, especially if your an large corporation with a large dev team.
Microsoft on the other hand wants to keep their cash cow of office running primarily on Windows. As if 365 ran flawlessly under WINE then the Office compatibility tie in that keeps a lot of businesses running Windows maybe broken. As businesses could save on the cost of a Windows license by just installing Linux with WINE and then use Office without having to pay for a Windows license, which is going to directly hit Microsoft profits.
Windows taking L pills with Wine.
The Linux boys are improving day by day, while the Windows boys are failling left and right.
Gaming has SteamOS, Wine looks very capable, and I am running out of reasons to even consider a Windows 11 setup. If I have to abandon my Windows 10, I am so jumping into the Wine tanker. As long as gaming works (GTA and the sort are known for being ill-tempered with kernel anti-cheat tools) I will gladly abandon the nonsense Windows has become.
FreeBSD
Wine 11 is actually available on FreeBSD. It's just that the package (port) is called wine-devel.
FreeBSD has several such packages, like drm-latest-kmod (drm 6.9 instead of 6.6), mesa-devel (mesa 26 instead of 24.3 or some such), wine-geko-devel and some others.
This way, an user can have stable or a relatively more up to date OS.
Can it run recent versions of Office though? That is what would make it useful for many people, but previous versions have never been able to (I have tried!). It's the Office click-to-run installer, which has been around since Office 2016 and the only installation method since 2019, which was the problem.