Purpose
How to troubleshoot 2359302 errors in the Deployment Tracker, CL5 Log, and the Windows Event Viewer
Symptoms
- Deployment Tracker in Shavlik Protect displays the Status Failed with a Description of "returned 2359302"
- c:\windows\propatches\CL5 Log on the target machine shows CommandLine.cpp:1833 CMD_TRACELOG: [Patch Install returned 2359302: Windows6.1-KB2861698-x64.msu]
- Windows Event Log show: "Windows update could not be installed because of error 2359302 "" (Command line: "C:WindowsSystem32WUSA.exe "C:WindowsTEMP739d98c6-b473-4611-9ecc-62da945d89eaWindows6.1-KB2388210-x64.msu" /quiet /norestart ")". Error 2359302 = WU_S_ALREADY_INSTALLED
Cause
2359302 is a Microsoft code that signifies the patch has already been installed.
The 2359302 message is also occasionally returned in error when the Windows Update Service is not working properly See. Eventvwr shows 2359302 ErrorCode
Resolution
Reboot the target machine to ensure the previous install attempt did not just need a reboot.
Check the patch Definition Version under the scan summary. Sometimes a deployment is based on a older scan job that detected the patch as missing. See How to check Protect Definition Versions for instructions to check Definitions version and to refresh files. If Patch Assessment version is outdated, refresh files and re-scan to see if the patch is still showing as missing. If the patch is still listed Under "Patch Missing", follow the troubleshooting steps in the document Protect Detects A Patch That Should Not Be Detected As Missing to determine if the Shavlik detection logic is in error. If the patch definition logic seems to be is in error, follow instructions under the Information to Send to Support section of the same document and open a case with Shavlik Support
If Shavlik Protect is detecting the missing patch correctly and manual installation fails, the Windows Update Service may not be working properly Refer to the following Microsoft posts:
Eventvwr shows 2359302 ErrorCode and
Customers have also had success running a dism.exe /scanhealth against the client machine to correct the issue.
Additional Information
Microsoft Community Posts addressing code 2359302:
Microsoft Community - Microsoft Windows
Affected Product(s)
Protect 9.X