Software Updates fail to install with Exit Code 17028, 17031, 17035 and other related errors.

book

Article ID: 155824

calendar_today

Updated On:

Products

Patch Management Solution for Windows

Issue/Introduction

Targeted the managed end-point with Software Update Policies; found the Client Logs and Agent GUI display Software Updates failed to install with Exit Codes via Patch Management's Software Update Cycle on schedule and failed to install when manually executed.

Confirmed the target rule logic was in order; the update targets the vulnerable .dll/file as detailed from Microsoft.

 

Exit Codes as follows:

  • 17025: Patch already installed
  • 17028: No product installed for contained patch
  • 17031: Detection: Invalid baseline
  • 17034 (17035): Error: Required patch does not apply to the machine
  • 17044: Installer was unable to run detection for this package
  • 17302: Error: Applying Patch
  • 1642: The installer cannot install the upgrade patch because the program being upgraded may be missing or the upgrade patch updates a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch.
  • 1612: The installation source for this product is not available. Verify that the source exists and that you can access it.
  • 1613: This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer Service

Cause

Found these errors most commonly direct to issues with how the software (i.e. Office Software) was deployed, or how it was upgraded with a Service Pack, or corruption was generated when later components were installed.

Environment

Patch Management 7.5.x, 7.6.x and 8.x

Resolution

Method 1: Run the "Microsoft Office Diagnostics" tool reports (can be found in Start \ Programs \ Microsoft Office \ Microsoft Office Tools \ Microsoft Office  Diagnostics). Check to see if any repairs are needed on the product.

  • Note: The Microsoft Office Diagnostics tool is no longer provided in version 2010 and up. The repair will need to be performed via Control Panel > Add/Remove Programs (Programs & Features); highlight the Software listed and Right-click > Repair
  • Additional repair process for Office on Windows 7, 8 and 10 detailed on Microsoft's Support Site.
     

Method 2: Ensure there are proper language packs or Service Packs installed on the client for Office, for if the client's targeted dll's (vulnerable files) are lower than the targeted level for IsInstalled=TRUE, then the update will target; however, if the base software is not laid down properly with the level of SP's & LP's then it will fail to install. The best method for ensuring 100% compliance is to get the base software to supported status.

 

Method 3: Uninstall / Reinstall the Office Suite to ensure the versions and product integrity are in order.

 

Advisory: If Patch Management still continues to fail to install these software updates; work through HOWTO60789 to gather the rule data for support will need to review if the targeting of the Software Update is in order.