Messages

[Disable Self-Updater]

Hey PaulKlerkx,

The Disable Self-Updater option only works for software that allow the configuration of the software updates check by setting an argument or a registry entry.

Handbrake, Keepass and Audacity don't. If you right-click on them in the Patch My PC Publisher, you'll find that Disable Self-Updater option is greyed out.
As I mentioned, this is due to these installers not supporting configuration of the self updater via command line or registry.
As an example, to disable the automatic check for updates for Audacity, you will have to update a Config file in the USER %appData% folder. More details here.
ConfigMgr / Intune will install the software as the SYSTEM account. To update files for the other user profiles you will have to use a custom script.

This should not apply to Google Chrome, however.
To troubleshoot this, we will need more details.
Are you deploying Google Chrome from ConfigMgr or Intune?
Are you deploying it as an Application or as an Update?
We also need some logs from the client side: Collecting Log Files to Send to Support for ConfigMgr and Intune
Once you have the logs, please open a support case.

Hey PaulKlerkx,

Software with special install behavior are documented in the Known Issues and Considerations when Using Patch My PC article.

Perfect! Great news! 

Thank you again for reporting this to us and for the feedback as well!

The command-line change is now part of our catalog as well, with yesterday's release.

Hey Bjerring,

By default, we are using the /AHMGUK argument for the silent install.
Based on the vendor's documentation, the /N* argument should create the shortcuts for all user profiles, otherwise they will be created only for the user running the install (which will be SYSTEM via Intune).

We'll add this additional argument on Thursday, but if you don't want to wait that long, right-click on Total Commander in the PMPC Console --> modify command line --> type in: /AHMGUKN*
Delete the app from Intune and then republish it from the PMPC Publisher.

We are monitoring the situation, when this happened in the past, they had another release quite soon. As soon as a new is released, we'll update our catalog.

Hey Rafal,

Based on Microsoft Release Notes build 123.x is the latest.

However, they pulled it without any official information.

If you go to the download page, you'll find that version 122.0.2365.106 is downloaded.

Because of this change, we rolled the changes back as well and re-published 122.0.2365.106 with an updated ID.

Great news, thank you for the update, Vik!

Great news, thank you for the update!

[General]

Hey Muja13,

This issue usually appears when the vendor releases a new version that isn't in our catalogue yet.
That isn't the case this time, as the latest version they released is the one we have in our catalogue too.

This can mean that you either get an installer with a different due to their CDN or it can mean a caching issue and the wrong installer is being downloaded.

Please open a support case to further troubleshoot this.
In the support case, please include:
1. The Patch My PC logs: They can be exported from the General tab within the PMPC Publisher console by pressing the Collect Logs button.
2. A screenshot of the hash of the Snagit installer. Manually download the Snagit Installer, and then run the Get-FileHash command to get the hash of the file that gets downloaded on the server hosting the PMPC Publisher.

Hey Vik,

Thank you for the feedback, it was very nice being there!

To investigate this issue further, please open a support case and include the following information:

1. Hit the "Collect Logs" button from the "General" tab within the Patch My PC Publisher --> it will generate a zip archive, please attach it to the support case.
2. Run this PowerShell script and include the "C:\PMPC_Repository\LocalContentHashes.csv" to the support case as well.

Hello Vik,

Was the correct installer downloaded to the local repository?
This guide will tell you which installer needs to be downloaded.

One way of doing this would be to use the PowerShell Deployment Toolkit as a "Post Script" and have it display a notification for the logged-on user.

There is an idea for us to support this option natively, using the "Manage Conflicting Processes" right-click option.
Please upvote this idea. The more upvotes it receives, the better.

Hey Ben,

When we've seen this issue before, the cause was the icon.
Can you please try another icon and see if that does the trick?

We are working to improve the error message and make it clearer.

Hey CFreeman,

Unfortunately, there is no such option. You would have to create your own custom script that does that and specify it in the "Add custom pre/post scripts" right-click option.

Please note that when ConfigMgr/Intune does the install of the app/update you deployed, it will do so as the SYSTEM account.
You will have to configure the script to display the prompt for the logged-on user while the install execution is done as SYSTEM. This is not easy to achieve, and it can be a security risk, depending on how it's achieved.