Topics

Hello!

Looking at the Supported Products List (https://patchmypc.com/supported-products), there's a note for "Oracle Java 8" that it requires a manual download.

But it appears that the same product is available through Winget. Looking at the manifest from the Winget community repository (https://github.com/microsoft/winget-pkgs/blob/master/manifests/o/Oracle/JavaRuntimeEnvironment/8.0.4210.9/Oracle.JavaRuntimeEnvironment.installer.yaml), the URL listed in it is reachable, and it does not seems like it requires any kind of authentication.

Would it be possible to verify if Oracle Java 8 could download and update without having us to provide a local content?

Thanks!

[Update existing application's metadata, deployment type, detection method, and content files]

Hello!

I've been reviewing https://patchmypc.com/base-install-update-options-explained, and also tumbled upon https://patchmypc.com/forum/index.php?topic=7830.0. Just wanted to make sure and confirm:

When application updates are set to the default option Update existing application's metadata, deployment type, detection method, and content files, are manually-created relations of supersedence, dependencies and global conditions retained after the app is updated to a newer version?

We have previously packaged a software with an EXE installer, and that software is available in PMP's catalog as an MSI installer. We were wondering if we could supersede the old app with the new PMP-packaged app, and that supersedence would be retained when a new version gets released.

We might also explore at limiting the ability of certain apps to install on various environment using global conditions, and were wondering if they too would stick after an app update.

Thanks!

Hello!

We observe that there is no option to prevent the execution of a post-installation (or a post-uninstallation) script if the main software installation/update exits with a failure code.

For example, say a post-uninstallation script that do some additional cleanup after the uninstallation of the main program had finished. If the uninstallation fails with a RC = 1603, then the post-uninstallation script would still be executed.

What would be your recommendations to handle such a situation?
Could an option be added in the Publisher to prevent a post-(un)installation script to run with RC different than a success code? (And if so, could it consume the return code as set in the "Modify return code" property of an update/configmgr app?)

Thanks!

Hello!

I took notice of the addition of icons in the product treeview now indicate if the product requires local content, or is configured to skip the install if running by default -- which is great!

Quick question: does this new change only add icons when these ability are determined as required by Patch My PC, or should they also appear when we enable "Manage Conflicting Process"? (Behind the scene, I suspect the Publisher only display the MCP icon for apps/updates having a McpDefaultEnabled element in supportedproducts.xml, and would not use a BlockingProcessManagementPolicy element from Settings.xml as another source for displaying the icon.)

Reading the McpDefaultEnabled element in supportedproducts.xml, I find there is useful information about why PMP recommends/enabled MCP by default for a specific app/update -- for example, for Jaspersoft Studio (EXE-x64): <McpDefaultEnabled>Returns Exit Code 1, update will fail if application is open during update process.</McpDefaultEnabled>. Is that information displayed textually somewhere in the Publisher Console?

Thanks!

Hi!

Looking at the FAQ Are Driver Updates for Dell, Fujitsu, HP, and Lenovo Supported?, the answer is pretty clear that drivers from HP, Fujitsu, Dell and Lenovo would not be considered for addition to Patch My PC's update catalog -- since these manufacturers maintain their own third-party catalog that can easily be added to SCCM, it would hardly make sense to duplicate the feature in PMP.

I'm wondering if Patch My PC is closed to all drivers submissions, or only to those from the above manufacturers or others that provide a TP catalog for SCCM?

Thanks!

Hello!

It is mandatory for our organization to have user-facing text description in French. We observed that, for software updates generated by Patch My PC, the default description added at packaging time is English-only, and there does not seem to be a way to customize it. Not possible, also, to clear the default text and leave it empty.

As a comparison, the localized description can be customized for configmgr apps -- thus, we can set custom text in French that is re-used by the Publishing Console at every repackaging.


Any idea, except completely hiding software updates deployments in Software Center?

[Steps to replicate:]

Hello!

Steps to replicate:

• In the Publishing console, under the "ConfigMgr Apps" tab, check the box next to an application to enable this app's creation in SCCM. For this test, let's use "Git (x86)";
• Run Publishing Service Sync, and wait for the sync to complete;
• Go in SCCM. Observe that a Git (x86) application has been created successfully;
• Return to the Publishing console. Untick the box in front of "Git (x86)" ConfigMgr App;
• Run Publishing Service Sync, and wait for the sync to complete;
• Go in SCCM. Observe that a Git (x86) application still exists. Its sources also continue to exist in the deployment type's source folder.

Is that the normal and expected behavior?
Did I miss an option somewhere in the Publishing console to remove an app (and its retained previous versions) when it gets unticked from the list of apps to sync?

If so, that's something I'll need to document when I do a knowledge transfert to my colleagues, and to remember to do some manual cleanup if and when an app gets unticked.

Thanks!

Hello!

I think I found an issue in the Publisher Settings console (version: 2.1.16.0). After I set a custom location to create logs on "All Products", if I disable log management on a specific update then re-enable log management on it, the Folder path for that update has reverted to Patch My PC's default location.

Steps to replicate:

• Under the Updates tab, right-click on "All Products", and select "Manage installation logging". In 'Folder Path', type a custom location (i.e. 'C:\MyLogs');
• Scroll down on a specific product (i.e. "Adobe Acrobat DC Continuous (x64)"). Right-click on it, select "Manage installation logging", and uncheck 'Enable logging'. Click 'OK';
• On "Adobe Acrobat DC Continuous (x64)", right-click on it, select "Manage installation logging", and check 'Enable logging'. Observe that 'Folder path' is now filled with 'C:\windows\ccm\logs\PatchMyPCInstallLogs'.

Expected behavior: since I have selected a custom logging location on "All Products", I would have expected that when re-enabling log management the 'Folder path' to be filled with my globally-configured custom folder path.


Strangely, the other settings seem to persist when disabling then re-enabling log management:

• Under the Updates tab, right-click on "All Products", and select "Manage installation logging". Check 'Enable verbose logging', 'Prefix the log with computername', 'In case of installation failure...' and set a secondary location;
• Scroll down to "Adobe Acrobat DC Continuous (x64)". Right-click on it, select "Manage installation logging", and uncheck 'Enable logging'. Click 'OK'.
• On "Adobe Acrobat DC Continuous (x64)", right-click on it, select "Manage installation logging", and check 'Enable logging'. Observe that all the settings are still enabled;
• Still on "Adobe Acrobat DC Continuous (x64)", uncheck 'Prefix the log with computername', then uncheck 'Enable logging'. Click 'OK';
• On "Adobe Acrobat DC Continuous (x64)", right-click on it, select "Manage installation logging", and check 'Enable logging'. Observe that 'Prefix the log with the computer name' is unchecked.

Though if you uncheck 'In case of installation failure...', the secondary location is emptied, and checking the option again would not fill it with the globally-configured secondary location.

Hello!

Quick question: for ".ps1" pre-scripts and post-scripts, is the interpreter always Windows Powershell? Looking at PatchMyPC-ScriptRunner.log, I can observe that:

Code Select Expand

<...>
Running script preinstall.ps1 ScriptRunner 2023-08-23 2:50:30 PM 1 (0x0001)
Running PowerShell Script. ScriptRunner 2023-08-23 2:50:30 PM 1 (0x0001)
Running C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy Bypass -file "preinstall.ps1" ScriptRunner 2023-08-23 2:50:30 PM 1 (0x0001)
Exiting With code: 0 ScriptRunner 2023-08-23 2:50:31 PM 1 (0x0001)
<...>
I have set nowhere which version of Powershell to prefer, so I'm assuming ScriptRunner is responsible of selecting the appropriate one. I'm wondering if it will always default to Windows Powershell, or if it might at some point detect that PS7 is present and use it, or if it looks at a favorite interpreter somewhere, etc. ?

Thanks!

Hi all,

We are currently reviewing Patch My PC, and I've ben tasked to find a way to count the number of installation that were realized by a Patch My PC update or configmgr app. Is there a way I can track that kind of statistics?

Currently, we allow apps that rely on a native updater (i.e. Google Chrome, or Adobe Acrobat/Reader) to auto-update using their built-in mechanism. On top of that, we've enabled these updates in Patch My PC. We want to quantify the number of updates that were done by PmP vs those completed by the auto-update mechanism.

Thanks!

[Add custom pre/post update installation scripts]

Hello!

Publishing Console version 2.1.14.0

We enabled the ConfigMgr App Adobe Acrobat Reader DC MUI in order for Patch My PC to automatically generate an application during sync. We needed to add an MST transform file to the base installer, we stumbled upon Add an MST Transform to the Adobe Acrobat Reader Base Install in Patch My PC's knowledge base.

Wanting a better organisation of our files (separate scripts and resource files), instead of adding the MST file as an additional file in the Add custom pre/post update installation scripts window, we added a whole folder --which contains the MST file. Then, we customized the command line as with additionnal arguments TRANSFORMS="%CurrentDir%\res\AcroRead2.mst" /QN.

What we observed, though, is that installation of Acrobat Reader ended with exit code 1624 -- the MST file was not found at expected location. Looking at the command line run by the ScriptRunner, we could see that the Transforms argument has been modified to contain double-times the path to the CcmCache folder!

See attached screenshots.

Question: is this behavior something specific to Adobe Acrobat Reader? In the command line modification, does %CurrentDir% always resolves to C:\Windows\CCMCache\xx\C:\Windows\CCMCache\xx ?



(We ended up adding the MST file directly instead of as an additional folder, exactly as described in the knowledge base. Now, the installation works.)

[Microsoft Power BI Desktop 2.104.941 (x64)]

Hi!

So I'm new here in using Patch My PC.

Trying to use the latest Microsoft Power BI Desktop 2.104.941 (x64) software update as published in SCCM by Patch My PC to update current installs of PBI Desktop. I notice that the PBI Desktop installer proceed with a software uninstall before installing the newest release. This causes two behaviors I'm wondering how to work around:
- the software update would not install when an instance of Power BI Desktop is running, and there is no notification i.e. in the PBI Desktop's user interface to request the user to close the app. Thus, the software update installation fails;
- any customization made during an initial installation is lost. For example, here, we set the default language to French using the LANGUAGE=fr-FR installation option in our SCCM application; after the installation is completed, there is an HKLM\Software\Microsoft\Microsoft Power BI Desktop:DefaultUICulture = fr-FR registry value. During the software update installation, I noticed that the whole Microsoft Power BI Desktop key is deleted, and after the software update is installed, the value of DefaultUICulture = en-US.

How do you guys work around these limitations?