[2.3.177] FSE-Windows - April 30, 2025

1. Overview

This article provides an overview of new features and resolved issues in the Fortanix Filesystem Encryption (FSE)-Windows 2.3.177 release.

The FSE policy now supports adding local on-premises Active Directory (AD) users and groups when adding an Access Control List (ACL) (JIRA: FSE-66).
For more information, refer to Filesystem Encryption for Windows as a Service Using Fortanix Data Security Manager - Policies.
The Fortanix FSE agent now supports deleting unmounted encrypted directories that are no longer needed or are experiencing issues (JIRA: FSE-251).
For more information, refer to Filesystem Encryption for Windows as a Service Using Fortanix Data Security Manager - Client Configuration.

Fixed an issue where users could not access files shared over a network path on Windows Server 2019 and later (JIRA: FSE-419).
Fixed an issue where group and user information were not being fetched exactly at one-minute intervals but at one minute and six seconds (JIRA: FSE-440).
Fixed an issue where the default path pattern in ACL was incorrectly set to ** instead of the correct /**, which is required for appropriate path matching (JIRA: FSE-431).

If the Fortanix FSE Agent UI is already running in an admin login session, it might not open or may freeze when attempting to launch it as an admin in another user's login session (JIRA: FSE-321).
Workaround: To prevent the UI from freezing or failing to open, launch it only once per user at a time or only once as an admin across all user sessions.
The Fortanix FSE agent does not restrict access to files such as databases and logs by default. This means that unauthorized users might access them (JIRA: FSE-185).
Workaround: Set file permissions to ensure only the Fortanix FSE Agent’s service account and authorized administrators can access these files.
Named pipe squatting occurs when an unauthorized process listens on a named pipe before the Fortanix Filesystem Encryption service starts. This may lead users to mistakenly connect to the unauthorized process instead of the legitimate service (JIRA: FSE-161).
Workaround: Ensure that no other service or application on the server uses the same named pipe as the Fortanix Filesystem Encryption service.

To install the latest Filesystem Encryption package for Windows, click here.