On macOS 26, ISL AlwaysOn uses updated system permissions. Customers upgrading to macOS 26 will need to grant the new permissions for the application to work correctly.
🚀 New Features
Updated ISL AlwaysOn to Qt 6.10.0
ISL AlwaysOn has been updated to use Qt 6.10.0. This brings platform improvements, updated system libraries, and better long term compatibility across Windows, macOS, and Linux.
Support for extended mouse events
ISL AlwaysOn now supports extended mouse input, including:
- Horizontal scrolling
- Mouse Back button
- Mouse Forward button
Please Note: This support is currently implemented on the agent side only. It will become usable once the next ISL Light release adds operator-side support.
Remote state: disable_audio_call / disable_video_call
ISL AlwaysOn now sends the disable_audio_call and disable_video_call state to the operator.
This will allow ISL Light (in an upcoming release) to hide the audio and video call buttons in the session toolbar when connecting to unattended ISL AlwaysOn computers.
Audio and video calls are not supported in ISL AlwaysOn, so this will prevent confusion among operators.
Update logo: ISL Online Powered by PDQ.com
The ISL AlwaysOn installer and application logo now includes “Powered by PDQ”. The About window was also updated to reference Terms of Service.
Minimum OS requirement changes
The minimum supported operating system versions for ISL AlwaysOn have been updated:
- Windows: raised from Windows 7 to Windows 10
- macOS: raised to macOS 14
- Linux: now requires
glibc 2.35or newer
🐞 Bug Fixes
macOS 26 permission issue
Users on macOS 26 experienced an issue where Screen Recording and Accessibility permissions could not be granted, preventing remote control. ISL AlwaysOn now runs its launch agent from inside the .app bundle, which resolves the permission handling problem.
Please Note: Users will need to grant permissions again for the new process.
New root bundle ID: com.islonline.islalwayson.agent
This change only affects macOS 26. Older macOS versions continue using the previous implementation.
macOS installation issue
The macOS installation procedure for ISL AlwaysOn was updated. Application bundles are now installed as non-relocatable. Previously, PackageKit could incorrectly detect existing binaries on disk, which could cause installation failures.
Uninstall was also updated, and the store_product_flags executable is now removed during uninstall.
ISL AlwaysOn service not starting automatically after macOS Sequoia upgrade
The macOS daemon updates (background service) are now serialized. Previously, the daemon could be removed from system settings or during uninstall/install at the same time. Additionally, the log files for the install and uninstall commands were moved to a new log file called aon_update.out.
The ISL AlwaysOn service update is now performed in a separate process. The main issues solved are:
- Parallel installation of launch daemons/agents is now serialized and atomic (ISL AlwaysOn and ISL Light restart/resume)
- Service updates in ISL AlwaysOn are now performed in a separate process
Both were the root cause of unreliable ISL AlwaysOn installations.
macOS boot issues when launch agents fail to start
Some users experienced boot issues on macOS after installing ISL AlwaysOn.
Previously, the ISSC daemon would kill the loginwindow process during startup if the agent was not detected. This workaround was required due to a macOS issue with bootstrapping launch agents, but it was timing-sensitive and not fully reliable.
The installation process was updated so that agents are now installed/uninstalled only after the main service setup is complete. macOS is now responsible for restarting agents and managing their lifetime.
AutoTransport send correct SNI with IP hint
AutoTransport https-direct and wsstun-direct will send correct hostname SNI when using IP hint. httpt-direct and wstun-direct will set correct hostname in Host header instead of IP hint.
Make logfile changes atomic
Some users saw unexpected files starting with @ in the installation directory. This was caused by non-atomic log file updates. Log handling is now atomic, and these files should no longer appear.








