IMPORTANT: This site is planned to be decommissioned in 2026. Visit the Tanium Resource Center for all Tanium release notes, user guides, and support information. To view release notes in the Resource Center, see Tanium Release Notes.
IMPORTANT: If you are using semi-annual releases for on premises, see the Release notes for 2024H1 semiannual release, Release notes for 2024H2 semiannual release, or Release notes for 2025H1 semiannual release on the Tanium Resource Center.
Effective October 15, 2024: On prem release notes on the Tanium Knowledge Base are frozen. For release notes related to 7.4 or 7.5 Server and Solutions, see the Monthly updates for Tanium Version 7.4 and 7.5 Server and Solutions on the Tanium Resource Center.
Release Notes Tanium Client (Version 7.6.4.2172)
Thank you for choosing Tanium. The following Release Notes document changes between releases of the Tanium Client.
The previous Tanium Client version can be found here: Release Notes Tanium Client (Version 7.6.4.2160)
Tanium Client 7.6.4.2172
- Tanium Cloud availability date: N/A.
- On-premises availability date: SAR-2025-H2.
Special Notes
- N/A.
Security Updates
- N/A.
New Features
- Implements a new reserved
Action Statussensor in the Tanium Client which reports the status of the action ID provided as a parameter.
Improvements
- Tanium Platform components now ship with OpenSSL v3.5.4.
- Tanium Platform components now ship with libExpat v2.7.3.
Bug Fixes
- Fixes a behavior in the Tanium Client where it would declare an action to be failed if the client was stopped in the middle of copying files once downloaded. Now instead the client will retry the action when restarted.
- Fixes a build condition where the v7.6.4 SBOM did not list the use of OpenSSL.
- Fixes a problem in the linking of Tanium Client binaries in Solaris which would cause installation and service failures with the message: "
TaniumClient: fatal: libcrypto.so: version 'OPENSSL_3.2.0' not found". - Fixes a problem in the handling of Tanium components
pki.dbdatabases which could result in the error: "Failed to add message signing certificate: Key already exists with fingerprint".
Known Issues and Workarounds
- N/A.