• Welcome to Support Forum: Get Support for Patch My PC Products and Services.

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Andrew Jimenez (Patch My PC)


Whenever they release a production build, we can look into adding it to the catalog. I'd recommend voting on this idea so that you can be notified if we add it.
Hi, You can use the steps defined here: https://patchmypc.com/how-to-view-applicability-rules-and-troubleshoot-detection-states-for-third-party-updates
to see the rules we use for applicability and detection. Java 8 will only update older versions of Java 8, so if you have Java 7 earlier, they will not show as applicable.

If you simply select the Java 8 Products in the Patch My PC Publisher, and provide the installation files for the latest version in the Local Content folder (info here: https://patchmypc.com/local-content-repository-for-licensed-applications-that-require-manual-download), the application that the Publisher creates will include a prescript by default that removes old versions of Java 8 before installing the latest.

Let me know if you'd like me to dive into anything specific or if you have any more questions.
Can you please zip up and send the Backups folder from the patch My PC Publisher installation directory and send it over to [email protected]?

Can you check the right click option in the Patch My PC Publisher and see what you have set for the logging path there? https://patchmypc.com/custom-options-available-for-third-party-updates-and-applications#install-logging
You are welcome. It is unfortunate, it bites us too from time to time.. Sorry I don't have better news for you :(

Ahh, In SCUP, did you happen to open the Jabber update, and click the browse button, then browse to your download?
It seems the rules we had were overwritten, and browsing to the MSI file in the edit wizard will do that...
Here are the applicability rules for Jabber from our catalog, they are the same with the latest release that is not relying on the local content path as well:
          <msiar:MsiApplicationInstallable />
              <bar:FileExists Path="Cisco Systems\Cisco Jabber\CiscoJabber.exe" Csidl="42" />
              <bar:FileVersion Comparison="LessThan" Path="Cisco Systems\Cisco Jabber\CiscoJabber.exe" Version="" Csidl="42" />
              <bar:FileExists Path="Cisco Systems\Cisco Jabber\CiscoJabber.exe" Csidl="38" />
              <bar:FileVersion Comparison="LessThan" Path="Cisco Systems\Cisco Jabber\CiscoJabber.exe" Version="" Csidl="38" />

This will install if it finds the product code {A17CAD61-815C-42AA-B6E7-76AFEF2C9311} or the file C:\Program Files [(x86)]\Cisco Systems\Cisco Jabber\CiscoJabber.exe with a version of less than
In SCUP you can click the "View XML" to see the rule. I'll see if I can pull the old catalog as well and check it out.
Hi Dominik,

Can you open a support case here: https://patchmypc.com/technical-support

And include the logs from some failed client. The logs we need are referenced here: https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#update-troubleshooting-client-logs

Also please reference this thread.
Thanks for letting us know. We've noted this and will see what we can do in terms of upgrading.
Hi Dominik,

In our testing we did not run into any issues with this application specifically. We have seen this problem before where another installation is still running and blocking the install, I am going to guess that is what occurred in this case. Have your installation numbers improved since you posted this?
No worries, the fixed rules went out yesterday for 3.8.8. Thanks for bringing this to our attention!
Are you looking at them in SCUP? They aren't actually empty, SCUP just can't process the rule type we use. if you click on the "View XML" you can see the applicability and detection rules.