Reference: Common errors

Review common Patch error messages and possible solutions. For information about general errors in Patch, see Troubleshooting Patch.

Client API connection failed. Unable to download file. Error #9

Cause

An endpoint performed a client reset while downloading a patch.

Solution

This error message can typically be ignored. After the client reset is complete, the endpoint typically continues downloading the patch within minutes. If you continue to see this error message, Contact Tanium Support.

Error creating Update Service Object - See C:\Windows\windowsupdate.log for more details. Error #9

Cause

Patch is unable to establish communication with the local Windows Update API.

Solution

Review the Windows Update log for errors, and then consult the Microsoft documentation for information about each error.

Patch <Patch UID>: WU_E_DM_INCORRECTFILEHASH. Error #-2145099774

Cause

A patch file becomes corrupted in transit from Microsoft to the Tanium Server.

Solution

For help with this error message, Contact Tanium Support.

Patch <Patch UID>: ERROR_INSTALL_FAILURE. Error #-2147023293

Cause

This error can have various causes, but it is likely caused either by a third-party application or by corruption in the Windows update.

Solutions

  • Review your Host and network security requirements and make sure you have added the necessary security exclusions so that antivirus software is not blocking Tanium processes.
  • Use Tanium to target the endpoint and deploy the Patch - Reset Windows Update Client package to perform a Windows Update Agent reset. To obtain this package, Contact Tanium Support.

Patch <Patch UID>: WU_E_CALL_CANCELLED. Error #-2145124341

Cause

This error is likely caused by interference from anti-virus software on an endpoint.

Solution

Review your Host and network security requirements and make sure you have added the necessary security exclusions so that antivirus software is not blocking Tanium processes.

-2147024784 ERROR_DISK_FULL

Cause

The installation drive on an endpoint is full.

Solution

Check the system drive and the drive on which the Tanium Client is installed and provide more disk space. Use the Disk Free Space, System Disk Free Space, Low Disk Space, or Low System Disk Free Space Tanium sensors to identify systems with low amounts of free disk space.

OfflSnc WARNING: failed to copy offline cab. hr = 0x80070070

Cause

The drive that contains the Tanium Client does not have enough disk space to download the offline CAB file.

Solution

Increase the amount of space available on the drive. Use the Disk Free Space, System Disk Free Space, Low Disk Space, or Low System Disk Free Space Tanium sensors to identify systems with low amounts of free disk space.

-2145124320 WU_E_NO_INTERACTIVE_USER

Cause

The patch cannot be installed silently, and a user must sign in and interact with the installation. Typically, this error occurs when conducting server patching.

Solution

Add the update to a block list or remove it from your deployment patch list. For more information, see Exclude patches with block lists and Edit a list.

E_PROP_ID_UNSUPPORTED

Cause

This error is triggered by the Windows Update Agent, and usually indicates that the endpoint needs to be restarted.

Solutions

Unable to Load PatchLib

Cause

This error is likely caused either by an endpoint not being part of a Patch action group, or by an incorrect version of Patch on the endpoint.

Solutions

  • Verify that the affected endpoint is in the Patch action group so that it is within scope of operations. For more information, see Configuring Patch.
  • Verify that asking Get Endpoint Configuration – Tools Status contains Patch in Interact shows the correct version of Patch is installed.

Windows Update Error: -2145124338 WU_E_XML_INVALID

Cause

The Windows Update Agent found invalid information in the XML data for the update.

Solution

Make sure that the endpoint is using the latest version of Windows Update Agent.

Unrestored registry snapshot found

Cause

The Patch Manager process was interrupted during a scan. This issue can happen if the endpoint restarts during a scan.

Solution

This issue is usually transient and no longer appears after the next scheduled scan. If you continue to see this error message, Contact Tanium Support.

Windows Update Manager timed out waiting for the Windows Update Service to reach a Stopped state

Cause

Tanium attempted to restart the Windows Update service prior to executing a Tanium Scan for Windows scan. This attempt timed out if the Windows Update service was busy performing an operation (likely unrelated to Tanium Patch) at the time Tanium attempted to restart the service.

Solutions

  • Check the following Windows Update Agent logs to determine what invoked the operation (for example, automatic updates scan or WSUS):
    • C:\Windows\Logs\WindowsUpdate
    • C:\Windows\WindowsUpdate.log
  • Use the Patch - Reset Windows Update Client package to reset Windows Update Agent. To obtain this package, Contact Tanium Support.

Windows Update Error: -2145107951 WU_E_PT_SUS_SERVER_NOT_SET

Cause

Either the endpoint is running Windows 10 Home Edition, or else the registry value is not set for a WSUS scan.

Solutions

  • Windows 10 Home Edition does not support Tanium Scan or WSUS scan. Contact Tanium Support if you see this error in your environment.
  • Use the Registry Value Data Tanium sensor to identify the value set for WUServer on the endpoint. WSUS scans require the registry value HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\WUServerWUServer. If that value does not exist on the endpoint, use the Registry - Set Value Tanium Package to set the value. For more information, see Tanium Console User Guide: Managing packages.

    Windows Group Policies overwrites this registry change if a Group Policy object specifies an intranet server to host updates from Microsoft Update. For more information, see Microsoft Documentation: Configure Group Policy settings for automatic updates.

Linux: Could not get results

Cause

This error is likely caused by Patch tools not being installed on endpoints.

Solution

Verify that the Patch tools are installed on your Linux endpoints.

  1. On the Patch Overview page, click Settings and then click Operating Systems to verify that the Enhanced Linux Support option is enabled.
  2. Verify that the Patch tools are installed on your Linux endpoints.
    If the Patch tools are not installed on your Linux endpoints, the Endpoint Configuration - Tools Status sensor returns
    Not Installed for Patch.

Linux: Failed to download repomd.xml

Cause

The Tanium server is unable to reach the repomd.xml file from the repository.

Solution

Check for the following issues:

Linux: Repo URLs found but unable to snapshot metadata files, likely due to connectivity issue

Cause

This error indicates that the Tanium Server cannot access the source repository for download.

Solutions

Linux: Selected repo <repository_name> is missing required Yum variables

Cause

This error indicates that Patch could not gather Yum variables for the operating system type of the selected repository. This issue might occur after you import a new version of Patch.

Solution

  1. Ensure that the process is running on Linux endpoints. For more information, see Patch process is not running on Linux or macOS endpoints.
  2. Re-create the Yum variables by clicking the Interact icon in the message.

Linux: Repo URLs were found but the snapshot could not be created, likely due to a Yum variable mismatch

Cause

This issue indicates that Patch could not resolve the listed Yum variables in the repository upstream URL.

Solution

  1. Ensure that the Patch process is running on Linux endpoints. For more information, see Patch process is not running on Linux or macOS endpoints.
  2. Ensure that custom Yum variables in the URL are accurate.
  3. Ensure that you have defined the custom Yum variables on your Linux endpoints.
  4. Reinitialize Patch, which runs the Patch - Repository variables sensor to gather Yum variables from Linux endpoints. For more information, see Initialize Patch endpoints. Alternatively, wait up to three hours for normal processing to gather the variables.