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.2106)

From Tanium Knowledge Base
Jump to navigation Jump to search

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.2086)

Tanium Client 7.6.4.2106

  • Tanium Cloud availability date: N/A.
  • On-premises availability date: January 21, 2025.

Special Notes

  • N/A.

Security Updates

  • N/A.

New Features

  • N/A.

Improvements

  • The Tanium Client can now recover its communications to a Tanium Server when the endpoint's local clock changes to a date and time outside the accepted time validity of the server's certificates.
  • Tanium Platform tool components are now updated to Python v3.8.20 for systems still requiring the v3.8 version.
  • Tanium Platform components now ship with Curl v8.11.0.
  • Tanium Platform components now ship with libexpat v2.6.4.

Bug Fixes

  • Fixes an issue in the Tanium Client installer where ServerNameList entry values might be duplicated.
  • Fixes an omission in the handling of Tanium Client peer keep alive traffic to now update the state of "best peer" when receiving these messages.
  • Fixes a condition in the Tanium Client where in its periodic reset process it would not follow the rule of issuing a SIGTERM before SIGKILL on the currently running sensor.

Known Issues and Workarounds

  • N/A.

Product Documentation and Resources