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:
Patch Management 8.x
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.
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.
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 the article, "What data is needed to troubleshoot a possible rules issue in Patch Management?,"to gather the rule data for support will need to review if the targeting of the Software Update is in order.