Wine 11.18 pushes deeper into kernel-driver support
Wine's latest development release is fixing regressions of its own making while pushing further into Windows kernel drivers.
Wine 11.18 is now available. The bi-weekly development release landed on September 18, 2026, delivering roughly 380 commits from 38 contributors and folding in 21 bug fixes.
Keep in mind that development builds like this rarely make the news. They're the grind between stable snapshots, incremental fixes that mostly vanish into the changelog. This one's no exception. There's a through-line worth following, though: Wine is expanding how it handles actual Windows kernel-mode drivers.
Building out ntoskrnl.exe
Wine has long been stronger at running user-mode Windows apps than loading real kernel-mode drivers. This cycle leans hard into that gap.
The headline thread is ntoskrnl.exe, the core Windows kernel component. Connor McAdams drove 10 commits focused on PnP (Plug-and-Play) device trees: install dates, unique instance IDs, and container IDs for both root and child devices. Etaash Mathamsetty and Nello De Gregoris stacked a cluster of exports and token-object support on top.
Elizabeth Figura made the biggest splash elsewhere. Her 28 commits massively grew mountmgr, the module that talks to storage controllers, adding a long list of CD/DVD and disk ioctls plus a D3D11 DiscardResource fix.
Wine's release notes list three headline themes: more ntoskrnl support for kernel drivers, a wide range of code-correctness fixes, and compatibility bumps for standard C headers. For what it's worth, the second of those is the quiet bulk of the release.
A rework that broke its own startup
Not everything in 11.18 is about what got added. Some of it is about what broke.
Alexandre Julliard, the project's long-time lead, shipped a 28-commit rework of how Wine maps the main executable and lays out process and thread structures. It's an ambitious change to code that runs before almost anything else does. The result: startup regressions for some applications.
So 11.18 also cleaned up its own mess. Bugs #60327, #60331, and #60337 all trace back to the TEB and main-image changes, with the arm64ec build caught in the crossfire too. That's a fair amount of self-inflicted damage to correct for in a single cycle.
It's a reminder that low-level startup code is about as fragile as any code gets. Get it wrong and everything below it fails. Julliard's follow-up commits to store the module handle globally and stop forcing a 32-bit image into high memory read as straight-up damage control.
Roughly half of the 380 commits are correctness fixes, and that hardening shows up in recognizable places. Hans Leidekker spent 30 commits on MSI, adding NULL checks, use-after-free cleanup, and underflow guards. Matteo Bruni dedicated 30 commits to validating mesh, skin-weight, and TGA sizes in d3dx9. Rémi Bernon led the whole pack with 48 commits, mostly OpenGL context management.
These aren't glamorous, but they're what keeps a codebase built over three decades from quietly falling apart as modern apps push against it.
And the payoff shows up in real games. The 21 fixed bugs include Assassin's Creed Rogue texture glitches, Star Wars: Knights of the Old Republic overlay corruption, The Bard's Tale IV hanging on MP4 playback, and Adobe Creative Cloud and Express installers that previously crashed on unimplemented functions.
At this point, the bi-weekly rhythm is almost background noise. You'll see 11.19 turn up before the ink on this dries. Development and stable lines run on parallel tracks, so the stable build still sits at Wine 11.0 from January while 11.18 quietly feeds whatever comes next.
Head here to the official release notes. Expect the next development release in about two weeks.
