Bottles, a graphical tool for managing Wine environments that lets users create isolated “bottles” for Windows software with separate runners, dependencies, settings, and launch options, has released version 64.0.
The main addition is ntsync support, a Wine-related synchronization mechanism that improves how Windows applications handle certain threading and synchronization workloads on Linux.
On the security side, Bottles 64.0 adds Eagle settings for threat scanning and crash detection, introduces malware and stealer-pattern detection for executables, and warns users before running flagged programs. The app can also offer an Eagle scan after a crash and show security findings in the analysis view.
Moreover, a new home card and dialog let users update components across bottles at once, reducing the need to manage updates bottle by bottle. Bottles 64.0 also adds a toggle to enable or disable launch arguments for individual programs.
For gaming and performance setups, Bottles now inherits MANGOHUD_CONFIG from the host environment by default. Plus, the release prevents the desktop session from going idle while a Windows app or game is running. The developers also addressed slow startup and UI freezes when many programs or library entries are present.
Regarding desktop integration, Bottles 64.0 fixes broken .desktop links when app names contain spaces, corrects KDE Wayland desktop entry creation, sanitizes bottle names in generated filenames, and escapes program names so symbols like ampersands render correctly. It also lowercases executable names for StartupWMClass.
The release improves executable handling by showing uppercase .EXE and .MSI files in the executable chooser. It also handles unknown locale codecs when decoding shortcuts and resolves document portal paths when adding program shortcuts.
Sandbox-related fixes cover Proton runners, gamescope, and process handling. Bottles 64.0 exposes the Proton runner path and runtime to the dedicated sandbox, writes the gamescope launch script to a shared temporary directory so the sandbox can execute it, and fixes stopping processes running inside a dedicated sandbox. It also disables the Steam Runtime when switching to a non-Proton runner.
Offline behavior has been cleaned up as well, with Bottles now notifying users when a bottle location is offline instead of hiding it, showing an offline banner, refreshing components when the connection returns, and populating installed runners and DLLs in preferences even when offline. The CLI no longer forces offline mode, allowing bottle creation to fetch components when needed.
Other fixes include avoiding Manager startup side effects during CLI launches, rejecting transient document portal paths for custom bottle directories, improving FVS2 repository initialization to avoid huge file counts, caching bottle templates without transient files, and preventing setup from hanging by timing out connectivity checks.
For additional details, see the changelog.
