Messages

Hey Bezzoh,

We have this documented on our known issues page.

Patch My PC utilizes the Machine-Wide installer for Microsoft Teams. The Machine-Wide installer uses the same MSI Product Code for all versions. This causes multiple issues concerning updates to the product as well as detection of new versions. Microsoft does not recommend updating the Teams MSI once installed (Microsoft Docs)

This will be in today's catalogue release. I appreciate your patience here.

We added a pre-script to remove 1.x if it exists and also updated the icon.

As an FYI, the new Dell Display Manager 2 has a dependency on .NET Core Desktop Runtime version 5. When you install it, and this isn't installed, the user is prompted to download and install it (see attached). Clicking 'yes' takes the user to this link to download.

The installer does not have any option to suppress this dialogue to the user if .NET Core Desktop Runtime is not installed. It also does not have an option to automatically install the dependency, either. I recommend you install .NET Core Desktop Runtime 5 before deploying this update of Dell Display Manager v2 to avoid this confusion for users.

If you have a support contact at Dell, please make them aware of this issue. Hopefully they will hear the noise and improve it. There is some discussion of this issue on Twitter: https://twitter.com/codaamok/status/1610954039302230016

We'll likely have this fixed in tomorrow's catalogue release.

This has been resolved. Please right click on the product in the ConfigMgr Apps tab of the Patch My PC, and choose the option to "Republish during next scheduled sync cycle".

To verify I understand the request correctly, the request is to make Adobe Acrobat Reader DC evaluate as installed if the superior Adobe Acrobat Pro is installed?

Hmm. I can understand both sides.

To implement such detection into the Adobe Acrobat Reader DC would break convention in our catalogue; we install an app, and detect if _that_ software is installed - this is the premise for all products in our catalogue. This suggestion is to support an alternative logic of: install an app, but if it a superior edition of the same software is installed, return as detected.

That is the correct procedure, yes. Or, you can delete the Application in-console, and the source folder, and re-sync to recreate it which should pull down the script into the package. This is a result of a bug in the Publisher that can't add Patch My PC Recommend or Defined scripts after the fact the product has been added to the catalogue.

This was fixed in 2.1.11.0. However, unfortunately a republish doesn't work either so I've raised another bug report internally to fix this.

Hello, I'm sorry for the delayed reply! We experienced an issue with our notifications for new forum posts. Is this still an issue for you?

Hey Xanathar,

I'm sorry for the delayed reply. We experienced an issue with our notifications of new forum posts.

I will investigate this and get back to you ASAP.

Hey Ithendyr,

I'm very sorry for the delayed reply. We experienced notification issues when new forum posts were opened. We have fixed this. The delayed reply is unacceptable.

Would you be able to book a support call with me directly so we can troubleshoot the issue together?

Here are a couple of links for this:

• https://calendly.com/adam-patchmypc/30min
• https://calendly.com/d/htr-rdq-czq/patch-my-pc-support-session-with-ithendyr

You will see more immediate and better availability options in the second link if you can meet this week. Otherwise the first link should show plenty of options for next week and onwards.

Hi TimothyG, it seems this version is not a straight forward upgrade to 2.0.0.135 from 1.56.2110 and requires more testing.

First thing it's x64 only now I think.

Secondly the installer now is 62MB with a new Logo and new vendor. The previous installer was ~900KB.

Thirdly, it doesn't remove the previous version, and it seems the silent installs witch has changed.

I will update you as soon as I can.

Dell support confirm this is a known issue. If you have a contact at Dell, please open a support case to apply more pressure as this a vendor installer issue.

You can track the status of this on our known issues page: https://patchmypc.com/known-issues-and-considerations-when-using-patch-my-pc

If you're still experiencing issues with this, please send client logs to [email protected].

https://patchmypc.com/logs

Hey Danne,

You can set the option to suppress reboots in the deployment wizard of SCCM, or you can configure Manage conflicting processes to only install the update when the software is not running (this generally mitigates the 3010 exit code) - read more here: https://patchmypc.com/manage-conflicting-processes-when-updating-third-party-applications

Thanks for the feedback. I see the value in your idea. Normally we would suggest to customers to scope their deployments to only deploy a product to devices they want it installed on, however your scenario is, in my personal opinion, perfectly valid for Adobe Acrobat.

This is not a function or feature today, kindly raise it on https://ideas.patchmypc.com.

Today, we can only support single file installers, i.e. standalone .exe/.msi/.msp installers. The full installer of this software is a multi-file installer.

I understand there is an .msi inside the installation media, however I understand that depends on additional content. Even if the .msi didn't depend on extra content, today, we also cannot implement custom pre-actions to extract content within archived media before/during publishing.