• View downloads
• View release notes

• View downloads
• View release notes

• View downloads

nginx-1.29.4 mainline version has been released, featuring HTTP/2 to backend and Encrypted ClientHello support.

1. Fix the boot issue for openSUSE 16.0 (#3379)
2. Experimental support for btrfs file system. (#3438 #3431 #3077 #2093).
   a) Only support NO RAID mode (single mode).
   b) ISO file can NOT be compressed.
   Please refer About btrfs for details.
3. Fix the issue that persistence plugin does not work for latest Arch Linux (#3407)
4. Fix VentoyPlugson WebUI display bugs. (#3252)

==================================================================
Wana boot and install OS through network (PXE)? Welcome to my new project iVentoy.

About iVentoy https://www.iventoy.com/
iVentoy is an enhanced version of the PXE server.
Extremely easy to use
Many advanced features
x86 Legacy BIOS, IA32 UEFI, x86_64 UEFI and ARM64 UEFI mode supported
110+ common types of OS supported (Windows/WinPE/Linux/VMware)
......

SHA-256

1fef1e804d4d963c1cff7a6dca7758be503a08b101fc8440d85270acd0767493  ventoy-1.1.09-linux.tar.gz
4bcafc308a8be5bd944255641e63cc3cbb78aaa62de388bc6eb59e5b77dd20f3  ventoy-1.1.09-livecd.iso
ff531a78d60c604cee67d56d02102a1147e647d0fb8fb8516f77712d05d5b99d  ventoy-1.1.09-windows.zip

 The Extended Stable channel has been updated to 142.0.7499.235 for Windows and Mac which will roll out over the coming days/weeks.

Bugfixes and minor changes:

• FTP: Fix a crash processing the ABOR command
• MSW: silent installations now automatically back up configuration files in cases where the interactive installer would prompt the user to do so.

The Stable channel has been updated to 143.0.7499.109/.110 for Windows/Mac  and 143.0.7499.109 for Linux, which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log.

Security Fixes and Rewards

Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.

This update includes 3 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.

[N/A][466192044] High CVE-2025-14174: Out of bounds memory access in ANGLE. Reported by Apple Security Engineering and Architecture (SEAR) and Google Threat Analysis Group on 2025-12-05

[$2000][460599518] Medium CVE-2025-14372: Use after free in Password Manager. Reported by Weipeng Jiang (@Krace) of VRI on 2025-11-14

[$2000][461532432] Medium CVE-2025-14373: Inappropriate implementation in Toolbar. Reported by Khalil Zhani on 2025-11-18

Google is aware that an exploit for CVE-2025-14174 exists in the wild.

We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.

Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.

Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Important

We recommend running CasparCG 2.5 on CPUs which support AVX2. Officially Chrome claims to require AVX2, and it is required for some of our in-progress HDR support.
Intel CPUs based on Haswell or later support this, which were first released to consumers in 2013, or 2014 for servers.

Starting with CasparCG 2.6, this will become a requirement.

Make sure to install the latest MSVC runtime, the compiler update requires a newer version than 2.4 https://aka.ms/vc14/vc_redist.x64.exe

Core

Improvements

• Initial support for HDR. This is limited to a subset of producers and consumers at this stage.
• Build for Windows with VS2022
• Rework linux builds to produce ubuntu deb files
• Update ffmpeg to 7.0
• Reimplement mixer transforms, to handle routes correctly
• Support more pixel formats from ffmpeg, to preserve colour accuracy better
• Support running on headless linux
• Transitions: Additional behaviours

Fixes

• Build with boost 1.85/1.86/1.87/1.88
• Build with ffmpeg 7.1
• Only produce mixed frames on channels which have consumers
• Routed channels not compositing correctly when channel used a MIXER KEY
• Handle audio for fractional framerates properly
• Gracefully exit on SIGINT and SIGTERM

Producers

Improvements

• FFmpeg: Support loading with a scaling-mode, to configure how clips get fit into the channel
• FFmpeg: Support more pixel formats without cpu conversion
• FFmpeg: Enable alpha for webm videos
• Image: Support loading with a scaling-mode, to configure how images get fit into the channel
• Image: Replace freeimage with ffmpeg
• HTML: Update CEF to 142
• HTML: Support audio

Fixes

• Route: Use full field rate when performing i->p channel route
• HTML: Gracefully handle page load errors
• HTML: Always set cache path

Consumers

Improvements

• Screen: Set size and position from AMCP
• Screen: Improve performance
• Image: Propagate AMCP parameters from PRINT command
• FFmpeg: Remove unnecessary forced conversion to YUVA422
• Decklink: Support explicit yuv output (requires AVX2)
• Decklink: Allow selecting device by hardware persistent id

Fixes

• FFmpeg: Correctly handle PTS on frame drop

Full Changelog: v2.4.3-stable...v2.5.0-stable

📦 Downloads available at

• https://user.bitfocus.io/download

💵 Donate to the project at

• open collective https://opencollective.com/companion

Companion v4.2.0 - Release Notes

This is a slightly smaller release than usual, focussing more on smaller improvements.

End of support for macOS 11

This version of Companion requires macOS 12 or later

Rebuilt Documentation

The Companion User Guide has been rewritten to use a new rendering system.

This allows us to host a new publicly available version of the documentation online which is versioned per release, as well as building it in a simplified form within Companion

The new tools allow us to do more with the documentation and will make it easier for us to keep up to date too!

Improved Expression Editor

The expression editor input field has been rebuilt, making it easier to use with functionality you would expect from a code editor. This includes functions and keyword suggestions, and better handling of multi-line expressions.

And more

• The old xkeys $(internal:tbar) and similar variables have been removed, and they should now be bound to custom variables in the config of each surface (#3716)
• Require macos 12
• Convert docs to docusaurus (#3741)
• Rebuild emulator pincode locking
• Add options to to restrict page access (#3736)
• Enhanced expressions:
  • Improved expression editor (#3713)
  • More formatting for timestamp (#3668)
  • Handle negative value in msToTimestamp (#3651)
  • Support local variables in step expressions #3762
  • Expressions better handle undefined. add getVariable method #3451 (#3715)
• Refined connection management:
  • Reworked connection config layout #3559 (#3569)
  • Rework changing connection versions, to remove need to disable module first
  • Add delete button to connection edit panel
  • Allow changing connection enabled state from config panel
  • Indicate connections missing modules in sidebar
• Surface improvements:
  • Merge surface remote and discover pages (#3677)
  • Support resolve speed editor #3525
  • Support more variants of Mirabox 293S
  • Support for Mirabox Streamdock N3 (#3686)
  • Add repeating button-presses to contour-shuttle shuttle ring (#3492)
  • Improve vec-footpedal surface implementation
  • Support complex surface layouts over satellite api (#3611)
  • Support swipe to change page on Stream Deck + (#3721)
  • Support touch strip variables for Loupedeck Live (#3790)
• Draw button 'error' state as a red warning triangle (#3675)
• Remove deprecated bank field from tcp bank_bg_change message #2779
• Include timestamps and source in module debug logs
• Add version number variables #3714
• Rework update check api, improving reliability

🐞 BUG FIXES

• ember+ api issues with some clients
• limit env vars passed to modules
• improve error handling for module executeAction
• "Sentry DSN not located" error in launcher (#3758)
• Align the display name of surface_set_position with the UI terminology (#3761)
• Avoid flooding modules with large objects, batch entity updates to resolve issues with large configs
• preserve original types of custom variable values from osc and ember+ apis
• improve version number handling for release vs beta builds
• Page up button/Page down button don't set page-history (#3683)
• Reduce frequency of pincode lock state logging (#3792)
• Loupedeck Live pincode lock layout

Full Changelog: v4.1.6...v4.2.0

⚠️ Potential Breaking Changes

• @directus/stores
  • Removed sidebar states from app store (#26259 by @rijkvanzanten)

✨ New Features & Improvements

• @directus/app
  • Added support for downloading multiple files and entire folder trees (#26006 by @Nitwel)
  • Added AI chat sidebar (#26259 by @rijkvanzanten)
  • Added support for float intervals and min/max warnings for number inputs (#26190 by @gaetansenn)
  • Made both sidebars resizable (#26259 by @rijkvanzanten)
  • Added header interface (#26302 by @AlexGaillard)
• @directus/api
  • Added support for downloading multiple files and entire folder trees (#26006 by @Nitwel)
  • Added AI chat sidebar (#26259 by @rijkvanzanten)
• @directus/types
  • Added support for downloading multiple files and entire folder trees (#26006 by @Nitwel)
  • Added AI chat sidebar (#26259 by @rijkvanzanten)
• @directus/utils
  • Added support for downloading multiple files and entire folder trees (#26006 by @Nitwel)
  • Moved fetchRolesTree,fetchGlobalAccess, fetchGlobalAccessForUser and fetchGlobalAccessForRoles to the public utility package (#26248 by @ComfortablyCoding)
• @directus/sdk
  • Added support for downloading multiple files and entire folder trees (#26006 by @Nitwel)
• @directus/system-data
  • Added AI chat sidebar (#26259 by @rijkvanzanten)
• @directus/errors
  • Added AI chat sidebar (#26259 by @rijkvanzanten)
• @directus/themes
  • Added AI chat sidebar (#26259 by @rijkvanzanten)

🐛 Bug Fixes & Optimizations

• @directus/app
  • Fixed an issue where input focus ring disappears on hover (#26315 by @formfcw)
  • Fixed display template not appearing for relations inside translations on new items (#26219 by @gaetansenn)
  • Ensured the created revision uses the correct label (#26289 by @vizzv)
  • Added reactive primaryKey prop to useFlows composable (#26287 by @AlexGaillard)
• @directus/api
  • Added redirect validation (#26346 by @br41nslug)
  • Moved fetchRolesTree,fetchGlobalAccess, fetchGlobalAccessForUser and fetchGlobalAccessForRoles to the public utility package (#26248 by @ComfortablyCoding)
  • Updated synchronization of remotely stored extensions (#26192 by @br41nslug)
  • Fixed missing accountability for files.upload when TUS is enabled (#26247 by @br41nslug)
• @directus/types
  • Moved fetchRolesTree,fetchGlobalAccess, fetchGlobalAccessForUser and fetchGlobalAccessForRoles to the public utility package (#26248 by @ComfortablyCoding)
  • Updated synchronization of remotely stored extensions (#26192 by @br41nslug)
• @directus/storage-driver-cloudinary
  • Updated synchronization of remotely stored extensions (#26192 by @br41nslug)
• @directus/storage-driver-supabase
  • Updated synchronization of remotely stored extensions (#26192 by @br41nslug)
• @directus/extensions-sdk
  • Updated esbuild dependency from 0.25.12 to 0.26.0 (#26215 by @dependabot)
• @directus/system-data
  • Updated esbuild dependency from 0.25.12 to 0.26.0 (#26215 by @dependabot)
• @directus/sdk
  • Updated esbuild dependency from 0.25.12 to 0.26.0 (#26215 by @dependabot)
• @directus/themes
  • Made both sidebars resizable (#26259 by @rijkvanzanten)
• @directus/utils
  • Preserved Error when passed to run-script operation (#26234 by @gaetansenn)
• @directus/composables
  • Set default sidebar shadow to false (#26259 by @rijkvanzanten)

📦 Published Versions

• @directus/app@14.4.0
• @directus/api@32.2.0
• @directus/composables@11.2.8
• create-directus-extension@11.0.24
• @directus/env@5.3.3
• @directus/errors@2.1.0
• @directus/extensions@3.0.15
• @directus/extensions-registry@3.0.15
• @directus/extensions-sdk@17.0.4
• @directus/memory@3.0.13
• @directus/pressure@3.0.13
• @directus/schema-builder@0.0.10
• @directus/storage-driver-azure@12.0.13
• @directus/storage-driver-cloudinary@12.0.13
• @directus/storage-driver-gcs@12.0.13
• @directus/storage-driver-s3@12.0.13
• @directus/storage-driver-supabase@3.0.13
• @directus/stores@2.0.0
• @directus/system-data@3.5.0
• @directus/themes@1.2.0
• @directus/types@13.5.0
• @directus/utils@13.1.0
• @directus/validation@2.0.13
• @directus/sdk@20.3.0

nginx-1.29.4 mainline version has been released, featuring HTTP/2 to backend and Encrypted ClientHello.

📦 Downloads available at

• https://user.bitfocus.io/download

💵 Donate to the project at

• open collective https://opencollective.com/companion

Companion v4.1.6 - Release Notes

🐞 BUG FIXES

• Setting local variables for another control failing #3813
• Unable to select module beta version for connection #3815
• Suppress some logged errors about local variable names
• Avoid spamming log with surface lock state messages #3792

Full Changelog: v4.1.5...v4.1.6

Security Release

• Update Instructions
• Update details on blog

BookStack v25.11.6 has been released.

This is a security release to address a vulnerability in our dependencies related to XML
handling, which could allow users to replay SAML authentication requests with specially crafted & manipulated requests.

It's strongly advised to update if you're using SAML authentication for BookStack.

Full List of Changes

• Updated application PHP dependencies.

If you’re ever in need of a device that works great with Home Assistant, well, I have just the program for you. Works with Home Assistant is our certification program that ensures devices work seamlessly and locally, all with brands that back them up.

Did you know that this year the Works with Home Assistant program has certified 12 partners across 12 months? That’s more than were certified in the two years since the program launched in 2022! The full list of devices is insanely long now (luckily, we made it searchable). To make all this happen over just one year, a lot of important things have been happening behind the scenes.

Moving to a non-profit foundation

In August 2024, the Open Home Foundation took over Works with Home Assistant. This helped reinforce that this program is not a commercial venture: it exists solely to connect our users with brands that support the foundation’s core values of privacy, choice, and sustainability.

When we moved it over to the foundation, we also took that chance to beef-up our processes, with robust legal contracts that ensure every partner who joins the program formally commits to things like offering users long-term support and easy updates.

It’s all about the devices

When we started the program we certified brands, but now we certify devices. This means you know exactly which sensors, switches, or other gadgets have been rigorously tested by us to ensure the best experience with Home Assistant. Each certified device has to work locally, without the need for cloud subscriptions or control.

We can now certify in phases, rather than overwhelming our testers with a truckload of devices in order to launch one partner. Also, if a manufacturer has one device that is cloud-controlled, it doesn’t blacklist any remaining items they have that could operate perfectly well locally. It sometimes means that sometimes your favorite devices aren’t part of the first wave of certification but, trust us, the partners check the comments 😉.

Making it easy to find certified devices

Here’s a conundrum: the more products that are certified, the harder it is for you to see and find them. The good news is I think we’ve cracked it!

Last week, we published the first version of our new searchable certified device list. Previously, you’d have to hunt around for info by checking the integration page or digging through launch blogs to see if a device was certified. Now, certified devices are kept up to date in one central, easy-to-use location, with extra information on the region they’re available in, the protocol we’ve certified them under, and notes about any secondary functionality we’re still working on.

So many (useful) columns!

The badge had a makeover

Every certified device earns the right to display our badge on its packaging, proudly announcing it Works with Home Assistant. If you’re not part of the program, you’re not allowed to use the Home Assistant logo. We used to have different versions of the badges depending on whether the device used Matter, Zigbee, or Z-Wave, and so on, but – let’s be honest – they were overcomplicated and impossible to actually read on a box!

Since the badge is such an important signal when you’re browsing products, we decided to simplify it and focus purely on that mark of quality. Now we have just two versions: a color badge and a monochrome design that are easier to read on any packaging.

We love to see the new badge being used IRL!

Companies of all sizes

For 2025, our goal was simple: we wanted both the big names and passionate community projects to be able to join. Yes, we’re thrilled to have major smart home players such as Shelly and Reolink committing to the program, but it’s equally important for us to connect with smaller, community-built projects – the start-ups or developers who keep open source at the heart of everything they do, like AirGradient and Apollo Automation.

This commitment to inclusivity is a big reason why we keep the annual fee for joining the program deliberately low, at only 500 CHF (per partner, not device) per year. We want to ensure being part of Works with Home Assistant is achievable for everyone who shares our vision.

Some of our team visiting the Apollo booth at IFA Berlin in September.

Improving testing

Testing hasn’t always been perfect – we knew we needed to make improvements, and the community has been amazing in helping us find things we need to look at. Like everything we do, we learn as we go, we iterate, and we improve. Previously, everyone was testing in their own way, but now we’ve standardized the way we test and give feedback to partners. This means testing is more consistent, exacting, and able to handle higher volumes – one of the reasons why we’ve been able to increase the number of devices we’ve certified so radically!

A lot of devices that come across our desks don’t pass certification, and it’s often due to organizations not fully understanding the requirements of joining. While this can vary greatly depending on the device and protocol, it was clear we needed to be more transparent. So as well as publishing our Works with Home Assistant Working Group Resolution, we’re also publishing further testing information: this sample testing report for a simple smart plug shows you the process we follow.

Keeping Home Assistant on the bleeding edge

Because we get to see and test new devices in advance, and receive feedback from our certified partners as part of the process, we have a sneak peek into what vendors have in mind for 2026 and beyond. This allows us to look at our product roadmap and see where we need to realign with innovations in the market. By testing today’s devices, we’re guiding tomorrow’s Home Assistant features!

Spot one of the certified cameras in our State of the Open Home segment

What can be controlled in Home Assistant

A core aim of the program is to ensure all certified devices have their “key functionality” available within Home Assistant. So how do we decide what aspects are controllable in Home Assistant and what doesn’t make the cut?

1. Key: First, we look at the functionality as a whole. Let’s use a door lock for example. The door should lock and unlock from within Home Assistant. That’s key functionality, get it? 😉
2. Secondary: If the lock also chimes when it locks or unlocks, we think of that as “secondary” functionality. We recommend that the manufacturer has it as an “exposed feature” in Home Assistant, so you can turn it off during quiet hours for example, but it wouldn’t block certification.
3. We have to look at what’s actually supported by the open standard that we’re testing against too. If a feature is not currently supported by the specification, there’s no way for the manufacturer to actually implement it. This is one of the major challenges in certifying against ‘younger’ specifications such as Matter.

We use our best judgment on this, but we also want your feedback, because everyone has a slightly different point of view, even within our team and testers – so look out for our user research requests, or please share your thoughts in our comments below!

Connecting with our community

For all this talk of testing, Works with Home Assistant is primarily about people and partnerships! As a foundation, we’re focused on making sure the program stays deeply connected with the community it serves, both online and in person.

We’ve been stepping up our presence at meetups and events around the world, so we can share the latest developments and gather your valuable feedback. From gigantic trade shows like CES in Las Vegas to small, local get-togethers, you can expect to see us there! We also want to do this online, so you can ask partners questions on streams, or in comments – keep an eye out for more of this in future.

San Diego Meetup

On to 2026

So that was 2025 in a (big) nutshell. As for 2026, we want to kick it off with some wonderful Zigbee partners we’ve been working really hard on – particularly after the awesome launch of Connect ZBT-2. Even though Zigbee is one of the longest-established protocols, it’s actually one of the hardest for us to test and certify because so many devices operate outside the official specification. This means our team and partners do a lot of prep to get them to a testable state – but in doing so we’re driving big improvements in functionality for everyone!

We also want to improve coverage globally, so, regardless of region, everyone who uses Home Assistant has a good range of certified options to choose from. This means we’re actively seeking partners who will cover regions outside of Europe and North America for everyday essentials like smart plugs and lighting.

As ever, everything coming up will be covered right here – so stay tuned for updates… and here’s to certifying many more devices in 2026! 🎉🥳🎊

• [p]Improved shadow fidelity on view models.[/p][/*]
• [p]Added local client icon cache for inventory items.[/p][/*]
• [p]Fixed a case that caused a small number of users to receive an erroneous VAC ban. The bans will be removed.[/p][/*]

• View downloads
• View release notes

1. Add support for FreeBSD 15.0
2. New tested ISO. (Total 1300+)

Wana boot and install OS through network (PXE)? Welcome to my new project iVentoy.

About iVentoy https://www.iventoy.com/
iVentoy is an enhanced version of the PXE server.
Extremely easy to use
Many advanced features
x86 Legacy BIOS, IA32 UEFI, x86_64 UEFI and ARM64 UEFI mode supported
110+ common types of OS supported (Windows/WinPE/Linux/VMware)
......

SHA-256

57689c6ef027eb5994c2aad8a2325c38455249451de3b29107274a30e15e7633  ventoy-1.1.08-linux.tar.gz
ad312c5a2f0fe65d92ee3e31b428a944ab6a93101f66a005ae494ea6e8c349d4  ventoy-1.1.08-livecd.iso
2eeb7553e62a940449a42b59ede3b4d3550023b2ff864a297dee818086e3564b  ventoy-1.1.08-windows.zip

Part-DB 2.3.0

New features

• Added the ability to define custom part states (PR #1053, thanks to @webdevinition)
• Added the ability to automatically suggest and generate IPNs (PR #1054, thanks to @webdevinition)
• Added experimental ability to rename datastructure types with the new synonym system, which allows you to define domain specific names for concepts of "parts", "categories", etc. (thanks @webdevinition)

Improvements

• Improved ability to determine category from info provider (#1113)
• Do not require a trailing slash for DEFAULT_URI (#1118)
• Define preview images for partkeepr imports (#1115)

Bug fixes

• Allow long URLs for attachments (#1022)
• Fixed issues related to mass import form (#1102, #1103, #1104)

Docker

• Added COMPOSER_EXTRA_PACKAGES env to docker containers, to install additional composer packages, like email bridges (#1138)

Miscellaneous

• Improved translations
• Updated dependencies
• Improved documentation

New Contributors

• @webdevinition made their first contribution in #1053
• @Copilot made their first contribution in #1124

Full Changelog: v2.2.1...v2.3.0

• Battlefield 6: Gaming stability issues [5582125]
• Counter-Strike 2: Text may appear slightly distorted when in-game resolution is lower than the native resolution of the display [5278913]
• Like a Dragon: Infinite Wealth: Light flickering after driver update on some system configurations [5432356]
• Like a Dragon Gaiden: The Man Who Erased His Name: Corruption after driver update on some system configurations [5432356]
• Black Myth: Wukong: Lower performance in driver branches newer than R570 [5562283]
• Monster Hunter World: Iceborne: Some particle effects may be missing on GeForce RTX 50 Series GPUs [5546598]
• Call of Duty: Black Ops 3: Gameplay becomes dim over time [5488108]
• Madden 26: Stability issues [5535693]
• Users running R580 branch drivers (58x.xx) or newer may observe lower performance in some games after updating to Windows 11 October 2025 KB5066835 [5561605]
• The Witcher 3: Wild Hunt: Random corruption on main character's sword corruption [5363151]

• Adobe Premiere Pro: Freeze During Export Using Hardware Encoding [5431822]
• Sophos Home Antivirus: System stability issues [5581371]
• Green line observed while viewing videos in Chromium browser on GeForce RTX 50 Series GPUs [5535388]

Changes in 8.2.1:

• Added a review prompt in the Microsoft Store version after a month's use
• Windows: Added TWAIN support to arm64 installer
• Windows: Fixed some OCR compatibility issues
• Windows: Fixed preview window being cut off
• Mac: Fixed SANE crash
• Escl: Fixed some compatibility issues
• Sane: Fixed some duplex compability issues
• Linux: Fixed Gmail/Outlook Web options not showing
• Linux: Fixed hidden buttons after disabling PDF encryption
• Sdk: Fixed extraneous error log

Changes in 8.2.0:

• NAPS2 is now available on the Microsoft Store
  • It costs a small fee to support the developer and provide automatic updates
  • NAPS2 will continue to be freely available at www.naps2.com
• Added "Edit with" under the "Image" menu for using an external image editor
• Added "Share even when NAPS2 is closed" option for Scanner Sharing
  • This will show a system tray icon and restart on login
• Imported file names are now used as the default file name when saving
• The "Apply to all selected" checkbox now stays checked
• Escl: Increased maximum time searching for devices from 5s to 60s
• Escl: Scanner IPs are now cached for faster and more reliable scanning
• Windows: Added an arm64 installer
• Windows: Replaced the "No friendly name" device name from some drivers with "Unknown Scanner"
• Mac: Fixed an issue where saved files didn't always have the right extension
• Mac: Disabled the "Apple Mail" email provider when not the default email reader
• Mac: Updated icons for Split/Combine
• Linux: Fixed issues with the Save dialog

Changes in 8.1.4:

• Windows: Added a "Theme" setting to switch between Light and Dark mode
• Linux: Fixed OCR on older Linux versions (e.g. Ubuntu 20.04)
  • Ubuntu 18.04 is no longer supported (use NAPS2 7.5.3 if needed)

Changes in 8.1.3:

• Twain: Fixed issues with Kyocera Ecosys scanners
• Sane: Fixed duplex with some scanners
• Windows: Fixed issues with multiple monitors with different DPI

Changes in 8.1.2:

• Added "Apply to all selected" for Split action
• Fixed "unsaved changes" prompt after auto saving
• Fixed issues with Placeholders in Default File Path
• Windows: Fixed OCR errors on some systems
• Windows: Fixed crash with right-to-left languages