Messages

This is now resolved in our latest catalog release.

Hi Matt,

Andrew from the catalog team here. Just to confirm, are you using the WSUS patches for this app? We just found that we had a prereq on the 32-bit version of our PowerShell WSUS update that would only allow it to install on 32-bit OSes. We're working on fixing the WSUS rules for this update now, and hope to have a fix automatically rolled out sometime this week.

You can add an additional pre or post installation script if you aren't able to use the command line option to add your unique id. note that you cannot replace the installation command with a script.

You can click on the right-click option for the Patch My PC defined prescript and it will show you the script used. Our prescript for this app is just an uninstall script to remove the previous version of the app. If you need to provide additional command line arguments, utilize the right click option to "modify command line".

Still working with Bentley to get access to the latest installers and I'm finding that the version on their download page is the previous version. Would someone please upload the latest version and we'll get it into the catalog? Thanks!

There should be no issues running the service on an Azure VM.

Hello, this is a known issue on our known issues page: https://patchmypc.com/known-issues-and-considerations-when-using-patch-my-pc, we are working on a Publisher fix for this, but for now, you can resolve this issue by enabling the "Run installation and uninstall program as 32-bit processes on 64-bit clients." option on the deployment type.

Thanks for letting us know, we'll get ESET Endpoint 12 added to our catalog in the coming weeks as a new product.

Publisher with ConfigMgr should move requirements automatically by default.

It should, but it may be an option that needs to be enabled actually. Are you using Publisher or Cloud, and ConfigMgr or Intune?

We've updated the table today and se the default for that app to "skip" if conflicting processes are running. Thanks for bringing this to our attention!

For deploying as an application, we do not add any additional requirements, so I would recommend adding a requirement to the application after Patch My PC generates it (when new versions are created, PMPC should copy the requirement to the new versions). When deploying as an update, we should detect the already installed version's bitness and install the correct version based on that.

We've added Bandicam 2024 as its own product in the catalog today. Thanks again for bringing this to our attention!

We are planning on adding this option to the Publisher, and tracking if this setting needs to be set as well. I don't have a timeline for adding that feature yet, however.

We've actually found a workaround on this and have been trying to dissect why this specific behavior is occurring over the last week. The workaround is to set the "Run installation and uninstall program as 32-bit processes on 64-bit clients." on the deployment type for Adobe.

What we are planning on doing, since this issue keeps reoccurring, is to add this option into the Publisher directly, and have the Publisher set this flag automatically for applications that run into this issue.