Patch-Specific Failure Reason Codes for Windows

Learn more about the Patch-Specific failure reason codes for Windows:

List of Patch-Specific Failure Reason Codes - Windows

List of Error Codes for Vendor Patch Failure - Windows 

List of Patch-Specific Failure Reason Codes

See the following table that shows the patch-specific failure reason codes for patch jobs in the Jobs Results tab.






This means patch is not available for the selected language.



This means the vendor patch file failed to download. As a result, installation will not happen.



This means an unspecified error occurred during the execution of the agent that caused patch deployment failure, e.g. out of memory.



This means the vendor patch file is either not signed, or the file signature fails the validation requested by the content provider.



This means the patch installation was aborted on command.



This means the installer failed to deploy the patch.



This means the patch deployment engine (STDeploy.exe) crashed / terminated unexpectedly.



This means the vendor patch file failed the signature validation.



This means the vendor patch file failed the hash validation.



This means the vendor patch has no URL.


List of Error Codes for Vendor Patch Failure - Windows

See the following table that shows the exit codes and the possible root cause for the Windows patch failure, and possible solutions to fix the issue. To know how to view the exit code details, refer to Viewing Windows Patch Failure Error Code Details.

Exit Code & Vendor 



Possible Root Cause

Possible Solution



The patch installation is successful, and the changes will be effective only after the asset is rebooted.

The agent machine is still in the pending reboot state.


The issue will be resolved after rebooting the endpoint.




The required disk space is not available on the agent machine.

The disk space is full.

The issue will be resolved after you free up the disk space of the targeted asset.



This is a generic error that is specific to the asset.

The 1603 MSI error code indicates a generic failure, but it's asset specific.

Refer to the following link for the suggested solution:



While installing the MS Office updates that utilize the Click-to-Run technology for some versions, such as some Office 2016, all Office 2019, and later, or Office365/Microsoft 365, OfficeC2RClient.exe must be utilized to trigger the update. This is handled by the \"noop.exe\" process, which calls the OfficeC2RClient.exe process with various switches. In some cases, if this process doesn't execute successfully, the security controls return the 1603 error.

The 1603 error indicates that the noop.exe application does not have the rights to run the OfficeClickToRun.exe or OfficeC2RClient.exe executable.
Security Controls use \"noop.exe\" to deploy the OfficeClickToRun.exe or OfficeC2RClient.exe with switches that enable the Office update process to complete.


The issue will be resolved after downloading the GPO settings required for the Office Customization tool. You can download the GPO settings from Also, \"Management of Microsoft 365 Apps for enterprise\" needs to be set to "Enabled".  


Microsoft, Splunk, and VMware

The Windows Installer service couldn't install the upgrade patch because either the program to be upgraded might be missing or the upgrade patch might update a different version of the program.

The version of the program targeted in the patch differs from the one on the agent machine. It might happen when an upgrade in the application is done in any other way before the actual patch installation.

The issue will be resolved by selecting the correct patch that supports the application version on the endpoint. But if the targeted application is already updated, you can ignore this message.



This error is encountered on failed patch deployments for Microsoft Office in the "Security Controls" or "Patch for Windows" console.


This issue is caused by a corrupt Microsoft Office installation or missing installation files that cause the patch installation to fail.


currently, the issue will be resolved by the following two methods:

-  Run the Microsoft Office installer you used to install the package & use the same to repair the installation. As a result, the missing files will be replaced.

-  Completely uninstall or reinstall Microsoft Office using the following Microsoft Uninstall Support tool to ensure that any old files or registry items are removed during the uninstall.