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 (Version 7.6.4.2058)
Thank you for choosing Tanium. The following Release Notes document changes between releases of the Tanium Server.
This platform release includes the release of both a Windows and Linux Tanium Server.
The previous version can be found here: Release Notes Tanium Server (Version 7.6.4.2050)
Tanium Server for Windows and Linux v7.6.4.2058
- Tanium Cloud availability date: August 6, 2024.
- On-premises availability date: N/A.
Special Notes
- The Tanium Server now uses Console (Version 3.7.16.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
- N/A.
New Features
- Implements the ability to rename a module service in the Tanium Server API.
Improvements
- Updates the manifest URL for the semi-annual release SAR-2024H2.
Bug Fixes
- Fixes a problem in the Tanium Server where running the "
clean-downloads" CLI operation could corrupt the state of theDownloads/Cache/Catalogfile if the server was up and running. This is resolved by the use of a SQLite database instead of a flat file to store this information. - Fixes an uncommon issue which would cause the Tanium Server to fail on startup with the message "
Tanium Server initialization failed: SQLiteStatementException: UNIQUE constraint failed: catalog.name" if the legacyDownloads/Cache/Catalogfile still exists after the newDownloads/Cache/catalog.dbdatabase had been created.
Known Issues and Workarounds
- N/A.