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 Patch (Version 2.0.9)
Thank you for choosing Tanium. This article documents changes between releases of Tanium Patch.
Tanium Patch 2.0.9.294
Release Date: November 8, 2017
Bug Fixes
- The Tanium File Info utility included with 2.0.9.292 was found to cause higher than normal CPU usage and has been updated. Customers that previously installed 2.0.9.292 are advised to upgrade to 2.0.9.294. After upgrading, customers can accelerate remediation of the issue by issuing the "Patch - Stop Patch Process" package once into the environment to cause endpoints to terminate current Patching activities and restart with the updated utility.
Tanium Patch 2.0.9.292
Release Date: October 31, 2017
Feature Improvements
- Addressed handling of maintenance windows being set from differing time zones
- Improved user workflow when repeatedly creating patch deployments through the introduction of deployment templates
- Provides role based access controls for Tanium 7.1 and above
- Improved solution uninstall behavior, including disabling Saved Actions, Scheduled Questions, and clean up of endpoint files and processes
- Improved workbench loading performance
- Addressed miscellaneous issues when using Patch on Tanium 6.5
Known Issues and Workarounds
- Tanium Client may fail to download Patches and experience higher than normal CPU usage if the ServerName value in the Tanium Server registry key has been changed from the default of 0.0.0.0
- Before you install Patch 2.0, remove Patch 1.x. The Patch 2.0 import automatically fails if Patch 1.x is installed. Contact your Technical Account Manager for assistance.
- If you are using an air-gapped environment with an offline CAB file, you must upload the wsusscn2.cab file and MS-CVEs.dat files to the Patch - External File References package. Optionally, use the WSUS scanning method.
- You might need to run a Windows Agent upgrade for reliable scanning and patch deployment on Windows XP and Windows XPx64.