Messages

You are correct. Our new native code signing method is much less picky in terms of certificate usage.

Other users have had success by doing the following:

• Delete the existing PatchMyPC.exe app
• Delete the folder "Patch_My_PC,_LLC" from "C:\Users\USERNAME\AppData\Local"
• Redownload and run the Patch My PC home updater from our website (https://patchmypc.com/freeupdater/PatchMyPC.exe)

Hello,

How are you publishing these updates? via our publisher or ConfigMgr in-console publishing?

Please recreate the detection method for this app, this issue was solved about a month ago, and the detection method just needs to be recreated. Thanks!

Hi,

Can you please send your settings.xml and patchmypc.log to [email protected] and we can take a look at why it is still attempting to use the proxy?

Have you restarted the Patch My PC Windows Service since turning the proxy off?

Hi,

When deploying this product as an application, you can deploy it with an uninstall intent and it will work properly.

https://ideas.patchmypc.com/ideas/PATCHMYPC-I-1375

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.

Hi,

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]?

Hi,

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:

Code Select Expand

      <sdp:IsInstallable>
        <lar:And>
          <msiar:MsiApplicationInstallable />
          <lar:Or>
            <lar:And>
              <bar:FileExists Path="Cisco Systems\Cisco Jabber\CiscoJabber.exe" Csidl="42" />
              <bar:FileVersion Comparison="LessThan" Path="Cisco Systems\Cisco Jabber\CiscoJabber.exe" Version="12.9.5.55511" Csidl="42" />
            </lar:And>
            <lar:And>
              <bar:FileExists Path="Cisco Systems\Cisco Jabber\CiscoJabber.exe" Csidl="38" />
              <bar:FileVersion Comparison="LessThan" Path="Cisco Systems\Cisco Jabber\CiscoJabber.exe" Version="12.9.5.55511" Csidl="38" />
            </lar:And>
          </lar:Or>
        </lar:And>
      </sdp:IsInstallable>
      <sdp:Metadata>
        <msiar:MsiApplicationMetadata>
          <msiar:ProductCode>{A17CAD61-815C-42AA-B6E7-76AFEF2C9311}</msiar:ProductCode>
        </msiar:MsiApplicationMetadata>
      </sdp:Metadata>

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 12.9.5.55511

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.