Protect Agent Update
This release delivers a crucial update for Protected Agent - it eliminates the limitation on Major Windows update.
Previous limitation
The Protected mode of Teramind Agent blocks access to its own critical components, including the service registry key and the service object. During a Windows in-place feature upgrade, Windows Update must read and copy every service's registration data into the migrated registry. Because it cannot read the Teramind service's data, it silently skips it. Once the upgrade completes, the service no longer exists in the registry and therefore never starts.
Please note that this affects full in-place feature upgrades that rebuild the registry (i.e. 24H2, 25H2, 26H1, etc.).
Update in this release
We are adjusting the Agent's protection to grant the minimum access Windows Update needs during migration: read/write for SYSTEM and read-only for Administrators, on the service object and its registry key. The service registration is then preserved and the service starts normally after the upgrade.
Security impact
Administrators will be able to see the Teramind service. They will still not be able to configure, stop, or delete it. No other protection is relaxed.
Improvements
Improved driver stability: Resolved kernel-level system instability (blue screen errors) that could occur on affected configurations.
Agent TLS connectivity: Restored prior TLS peer-verification behavior for improved compatibility with network inspection and proxy deployments.
Bug Fixes
Fixed an issue where the protected agent created diagnostic and offline storage folders at the drive root instead of under the installation directory.
Fixed an issue where screen recordings were missing footage from before a behavior-rule violation when recording was limited to behavior-rule violations.
Fixed an issue where the first minute of screen recording after session start could be lost.
Fixed an issue where block-content-share rules did not prevent sending blocked files through Claude web and desktop when file text was sent inline with the message.
Fixed an issue where geolocation monitoring did not activate correctly on Windows 11 when Location Services needed to be enabled.