FS Protection macOS releases (2026)

Release 26.1 beta 1 (build 67550)

We are pleased to announce the availability of a new release of FS Protection for macOS. This update is available for download from My FS Protection and delivery to existing installations will be started soon.

Highlight of this release:

• Updated illustrations in product main and settings UI apps
• Improved license state management for "Log out" and "Log in" button in the UI
• Improved handling of license termination. UI properly transitions into unactivated state to allow for re-activation.
• Improved handling of automatic activation flow with attribution ID token embedded to the Installer mpkg file to better handle a case of multiple users begin logged in at the same time.

If you experience any issues, please report them in this forum. Please run "Support Tool" when the issue happens and be prepared to provide the resulting file if we requested. For issues related to Browsing protection and Parental control, remember to include any URLs that reproduce the problem in your bug report. You may also submit false positives and uncategorized web pages directly to F-Secure Labs using  https://www.f-secure.com/en/support/submit-a-sample .

As always, we welcome any feedback via the community pages!

Release 26.1 beta 3 (build 67683)

We are pleased to announce the availability of a new release of FS Protection for macOS. This update is available for download from My FS Protection and delivery to existing installations will be started soon.

Highlight of this release:

• Addressed an issue that causes welcome view to be shown unexpectedly after upgrade

If you experience any issues, please report them in this forum. Please run "Support Tool" when the issue happens and be prepared to provide the resulting file if we requested. For issues related to Browsing protection and Parental control, remember to include any URLs that reproduce the problem in your bug report. You may also submit false positives and uncategorized web pages directly to F-Secure Labs using  https://www.f-secure.com/en/support/submit-a-sample .

As always, we welcome any feedback via the community pages!

Release 26.2 beta 1 (build 67940)

We are pleased to announce the availability of a new release of FS Protection for macOS. This update is available for download from My FS Protection and delivery to existing installations will be started soon.

Highlight of this release:

• Improved handling of feature set changes in the usr license. Welcome view is only shown for features that were not previously accessible to the user instead of showing it on any change.
• Clean up of product installation script from user defaults migration needed for pre Total Mac 18.0 versions.
• Improved hotfix daemon launch interval to be "every 6 hours" instead of "every day".
• Changed the behavior of "Scam Protection" feature telemetry. Previously, the entire event was dropped if user consent is missing. Now the event is always sent but the it is missing user confidential information (URL blocked by the feature) if consent is not granted in product settings.

If you experience any issues, please report them in this forum. Please run "Support Tool" when the issue happens and be prepared to provide the resulting file if we requested. For issues related to Browsing protection and Parental control, remember to include any URLs that reproduce the problem in your bug report. You may also submit false positives and uncategorized web pages directly to F-Secure Labs using  https://www.f-secure.com/en/support/submit-a-sample  .

As always, we welcome any feedback via the community pages!

Hello!

26.2 beta program had ended. The version has reached general availability in production. Thanks everyone for participating!

We will continue updating this thread with the next beta version releases. 

Stay tuned!

Thank you for the report. It will be addressed in the upcoming release.

I can share a few additional observations based on analysis on our side.

DeepGuard feature actually gets disabled but product settings UI fails to reflect that. The launchd job is meant to be still running even after disabling of the feature in the UI. The mode is switched to passive. This is how it works by design.

Generally I would advise against manually altering state of product launchd jobs as this is an unexpected involvement in the product state management. It introduces untested configurations of product which could cause unexpected results.