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.2.1218)
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.2.1204)
Tanium Client 7.6.2.1218
- Tanium Cloud availability date: May 13, 2024.
- On-premises availability date: May 16, 2024.
Special Notes
- N/A.
Security Updates
- N/A.
Improvements
- N/A.
Bug Fixes
- The Tanium Client
sensor-historylog now presents sensor execution events in an all-JSON format and includes both thewhat_hashanddefinition_idfor the sensor implementation used, in order to make the report information accurate. - Fixes a behavior in the Tanium Client where when communicating through proxy servers with uncommon
CONNECTresponse behavior would cause high CPU consumption in theTaniumClient -cprocess. This condition happened when the proxy server would not offer a response to the connection request, which is unexpected. - Fixes an issue in the handling of question expiration and cleanup times in the Tanium Client which would cause a small increase in CPU utilization while waiting for the appropriate cleanup time.
- Fixes a condition in Tanium components communications where a process could spin and consume higher amounts of CPU when a TLS negotiation was terminated abnormally.
Known Issues and Workarounds
- N/A.