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 1.1.5)
Thank you for choosing Tanium. This article documents changes between releases of Tanium Patch.
Tanium Patch 1.1.5.36
Release Date: 8 June 2016
Feature Improvements
- Patch list rules can now be configured from within the list edit dialog.
- We have added support for "Does Not Contain" logic to patch list rules.
- Patch lists can now be exported and imported.
- The Patch Workbench solution can now be uninstalled. Note that solution uninstall requires Tanium platform version 6.6 or 7.0.
- We have added a new status for deployments to better handled unsigned cab files from Microsoft. Deployment results will report "Bad Cab File" in cases where the deployment cannot proceed because the cab file signature is invalid. Note that this requires that the Windows Security Patch solution be upgraded to 2.1.0.0037 or better.
- We have made a number of stability and performance improvements to the patch workbench.
Bug Fixes
- We resolved an issue in which the patch service could consume excessive server resources.
- We resolved an issue in which deployments would fail in cases in which Microsoft included hidden high-bit characters in patch KB numbers.
- We resolved an issue in which a deployment with a single patch application failure would show failed status even if other patch applications in the deployment succeeded. Patch deployments in this condition will now correctly report partial success.
Known Issues and Workarounds
- In rare circumstances, deployments may fail to initiate in multi timezone environments. Workaround: If you think you are experiencing this issue, create deployments with a defined start time in the future, for instance Tomorrow at 8PM.
- Deployments targeting more than 10 computer groups will fail. Workaround: When creating patch deployments, target 10 or fewer computer groups.