Quantcast
Channel: Symantec Connect - Endpoint Management
Viewing all articles
Browse latest Browse all 7163

BUG: Symantec Patch Management SWD Package does not implement new MSU-based Windows Update exit codes

$
0
0
I do not need a solution (just sharing information)

When Symantec Patch Management executes a patch on a system, it can exit with different return codes, such as Windows Installer (MSI) or Windows Updates (MSU).

Most notable is when a patch states 'Failed to install' and opening the package shows the exit code as 2359302.

Per Appendix G: Windows Update Agent Result Codes (http://technet.microsoft.com/en-us/library/cc720442(v=ws.10).aspx), this is what the result code means; 'The update to be installed is already installed on the system.'

0x240008    2359304    WU_S_ALREADY_DOWNLOADED    The update to be downloaded has already been downloaded.    
0x240006    2359302    WU_S_ALREADY_INSTALLED    The update to be installed is already installed on the system.    
0x240007    2359303    WU_S_ALREADY_UNINSTALLED    The update to be removed is not installed on the system.    
0x240004    2359300    WU_S_MARKED_FOR_DISCONNECT    A callback was marked to be disconnected later because the request to disconnect     
0x240005    2359301    WU_S_REBOOT_REQUIRED    The system must be restarted to complete installation of the update.    
0x240002    2359298    WU_S_SELFUPDATE    Windows Update Agent updated itself.    
0x240001    2359297    WU_S_SERVICE_STOP    Windows Update Agent was stopped successfully.    
0x240003    2359299    WU_S_UPDATE_ERROR    Operation completed successfully but there were errors applying the updates..    

Looking at the package information for any Windows Update-based patch, shows "Success codes" of 0, 3010, 3011 and 1641. These are ONLY the Windows Installer success codes. The product does not have the correct success codes for the type of package it is deploying.

The problem with the product is that this is NOT a failure code. What's worse is that this information has been around for years, but even in these forums product users have been told this is caused by something being wrong with their environment, such as overtargeting?!

Please fix this.


Viewing all articles
Browse latest Browse all 7163

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>