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 Server and Tanium Client (Version 7.6.1.6412)
(Redirected from Release Notes (Version 7.6.1.6412))
Thank you for choosing Tanium. The following Release Notes document changes between releases of the Tanium Server and Tanium Client.
This platform release includes the release of both a Windows and Linux Tanium Server as well as the Tanium Client for all supported platforms.
The previous version can be found here: Release Notes (Version 7.6.1.6393)
Tanium Server for Windows and Linux and Tanium Clients for all platforms v7.6.1.6412
- Tanium Cloud availability date: November 1, 2023.
- On-premises availability date: N/A.
Special Notes
- This version of Tanium Server shipped with: Console (Version 3.6.37.0000).
- Tanium discourages new installations of this software version on Windows 2012 and 2012-R2 given its End-Of-Life on
2023-10-10.
Security Updates
- This release includes security updates. Details of the issues, including affected versions and mitigation information, can be obtained within Tanium's Support Portal or by contacting your TAM.
New Features
N/A.
Improvements
- Tanium Platform components now ship with SQLite v3.42.0.
Bug Fixes
- Fixes incorrect determination of hash collisions in the Tanium Server when receiving results from case-insensitive sensors from legacy clients.
- The Tanium Server question API will now return empty results for
GetResultInfoandGetResultDatarequests on expired questions, being that such requests cannot be fulfilled anyway and would result in "Question cache not found" errors being logged for them. - Fixes a behavior in the Tanium Client by which it would always deliver its sensor statistics information to its reporting server instead of forwarding them to its connected peer.
- Fixes an omission in the Tanium Server where it would not process incoming
server_health_updatemessages received from zone servers. - Modified the output of the
TaniumClient quarantine listcommand to match that of legacy versions, because there exist content sensors and packages that depend on the format of this output. - Fixes a condition where the Tanium Server might corrupt its new string cache bitmaps.
- Fixes an omission by which the Tanium Server would not reflect updates received from legacy endpoints when an
[RCU]resolution was received or a legacy hash collision was detected. - Implements a re-processing of sensor string files in the Tanium Server during upgrade to avoid case insensitive string hash mismatches which would cause
[RCU]errors in question results. - Fixes a mismatch between server and client in the treatment of case insensitive sensor string hashing which would result in
[RCU]errors which would never resolve in question results. - Introduces controls on the Tanium Client to determine the structure and content of string hash reports.
- Fixes an omission in the Tanium Server where delayed/ future string reports would not be noticed in the resolution of missing strings.
- Fixes a condition in the Tanium Client where it would incorrectly send a throttle control command which would risk breaking its established connections.
- Adds necessary field keys in the new Tanium Server results cache needed to implement the required behavior for letter-case folding in sensor results.
Known Issues and Workarounds
- The Tanium Client will fail to parse a PAC proxy file referenced by
ProxyAutoConfigAddresswhen more than one proxy server is defined, logging "Failed to parse proxy name. Too many colons" atLogVerbosityLevel=41.
Workaround: None. A fix for this issue is will be released with a new version of the Tanium Client post-v7.6.1.6432. - On upgrade from v7.4 clients v7.6.1 client releases may display an incompatibility with older OpenSSL v1 dependent client extensions. Tanium strongly encourages installation and upgrades to the latest release of v7.6.2+ clients, starting with 7.6.2.1204.