How to debug a patch that has a NOT PATCHED detection status with a SUCCESS (102) (4278418)

How to debug a patch that has a NOT PATCHED detection status with a SUCCESS (102) on the deployment status and it tried to deploy 3 times.

Usually when a patch has tried to deployed 3 times and still has a "NOT PATCHED" detection status with the "SUCCESS (102)" on deployment, it is an indication that the patch may have some issue during installation and it is not recorded back to the K1000 appliance. The error message arise in the MSI level and will need to find out the error message to determine the issue.

Please NOTE:

SUCCESS (102) - Status means that the end system needs a reboot to get the patch registered and installed.  If this is done then please follow the instructions to gather information.

The issue can be of a few things:

• Incorrect detection of the patch which cause's the patch to deploy unsuccessfully because it is not needed
• There is an issue with the actual MSI package of the patch

Privileges of writing to the registry or file system to register the patch during installation

To help determine the cause of the issue, here is a list of items to check:

• Make sure to reboot the client machine and manually run a detection through the K1000 appliance to be sure that the patch is installed and registered. If the patch still doesn't change the status from "NOT PATCHED" to "PATCHED" continue to step 2.
• Check the Application Event Logs for WSH or MSI error message:
  • Here is a example of a WSH Error message:
    • PLUS DEPLOYMENT: Error
      File Name: Windows6.0-KB905866-v29-x86.msu
      INSTALL:
      An error was returned from the executable while installing the patch.
      Error Returned: 1008

 
Here are some references on MSI error codes and office 2007 installation error messages:

• MSI error messages: http://desktopengineer.com/msierrors
• Office 2007 Error messages: http://technet.microsoft.com/en-us/library/cc179058.aspx
• Check to see if the specific patch is really installed on the client machine:
  • Click Control Panel | Add / Remove Programs | Show Updates 
• The last thing to try out is to run the actual patch file manually in the C:\Windows\temp directory:
  • For example:
    • The "MS 905866 Windows Mail Junk E-mail Filter Update (May 2009)" patch executable is: Windows6.0-KB905866-v29-x86.msu
    • It will be located in C:\Windows\Temp\Windows6.0-KB905866-v29-x86.msu

 
Manually execute it by double clicking it and see if it installed successfully or failed with an error message.
 
How to enable debugging for patching:

How to turn on client debugging for Patching on the K1000