Software 44769 Published by

Bottles 66.9 has been released as a focused hotfix that bundles xz and dconf into the experimental cpak containerized runtime while fixing regressions in custom bottle folders and game process termination. The update caps an aggressive 15-day sprint that saw the team ship ten versions, building directly on the feature-heavy 66.0 release which introduced native UMU integration and Adaptive Launch. By making the new containerized runtime self-contained and smoothing out long-standing Wine friction points, the 66.x cycle aims to finally make running Windows software on Linux a seamless desktop experience.



Bottles 66.9 lands with cpak runtime fixes, capping a 10-version sprint in two weeks

The Linux Windows-compatibility layer ships five targeted patches as part of its most aggressive release cycle yet.

Bottles 66.9 is here. Lead developer Mirko Brombin dropped the update on August 26, and it does exactly what you'd expect from a hotfix in a sprint this aggressive. The release packs five targeted patches that keep the new cpak containerized runtime self-contained and smooth out a handful of regressions. It also marks the end of a blistering 15-day window that saw the project ship ten versions between August 11 and August 26.

That kind of velocity is rare for any software project, let alone a Flatpak-based compatibility layer. The team isn't just throwing code at the wall. Each version in the 66.x cycle tackled a specific friction point, starting with the major 66.0 drop. The project describes that initial release as one that "cuts out Wine friction with native UMU and Adaptive Launch." 66.9 is the final stitch in that quilt.

Screenshot_from_2026_02_16_13_28_00

What actually shipped in 66.9

Every patch in this release comes from Brombin. The headline changes focus on the cpak runtime: xz and dconf are now bundled directly into the container. If you've ever tried to run a Windows app that relies on compressed archives or GNOME settings storage, you'll appreciate why that matters. The container can finally read its own config without hunting the host system.

Next are the user experience fixes. Custom bottle folders in the file manager now open reliably after a regression crept in. Profile path aliases stick to relative paths instead of getting forcibly converted to absolute ones, which breaks portable setups. And if you've ever clicked stop on a stuck game only to watch the process linger in the background, that's fixed too.

The 66.x sprint and what it means

The broader 66.x cycle is where the real story lives. Version 66.0 brought native UMU integration, which kills the need to juggle Lutris or Heroic just to run Steam titles through Wine. ProtoSoda became the default runtime for those launches. Adaptive Launch automatically picks native over Wine when possible. NVIDIA compute libraries landed to finally give Linux creatives CUDA access without dual-booting. The experimental cpak format also arrived alongside the traditional Flathub distribution.

If you're running Bottles on Flatpak right now, 66.9 is a safe upgrade. The package sits at roughly 168 MiB, x86_64 only, and installs directly from Flathub. Keep in mind that the cpak runtime is still experimental, so you might run into edge cases if you're testing containerized installs. The bundled xz and dconf should cover the vast majority of cases, though.

It's a focused hotfix that quietly makes the cpak runtime actually viable for daily use. The 66.x sprint as a whole is the real win here. Ten major iterations in half a month, each chipping away at a specific Wine friction point. The long wait for a frictionless Windows-on-Linux experience on the desktop is clearly over.

Head here to grab Bottles 66.9 on Flathub. You can also check the store listing on cpak.it. The source code is available on GitHub.