Client's Log / Agent GUI display Software Updates fail to install with Exit Code 17028, 17031, 17035, 17044 and other related errors.
Exit Code 17025, 17028, 17031, 17035, 17044, 1642, 1612, 1613
Problems with how the software was deployed, upgraded with a Service Pack, or later components were installed.
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); hightlight 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 installing these software updates, then work through HOWTO60789 to gather the rule data for support will need to review if the targeting of the Software Update is in order.