• Welcome to Support Forum: Get Support for Patch My PC Products and Services.
 

Recent posts

#1
We are using the MSI set to install per-system by adding the following to the command line:

REBOOT=ReallySuppress MSIINSTALLPERUSER=0
#2
The publisher successfully downloaded the file late yesterday without any issues so I think we are all set!
#3
Hi @msysadmin, I just downloaded the Citrix Workspace 25.3.10.69 installer and calculated its hash/digest. For me, it matches the one we have in our catalog. Is this still an issue for you?
#4
I was curious if the PatchMyPC version of Arduino is running as system or user, and so if it installs to user\appdata or to Program Files. Thanks.
#5
Quote from: Dan Gough (Patch My PC) on July 09, 2025, 02:25:09 AMBTW we list all dependencies here:

https://patchmypc.com/kb/known-issues-considerations-when-using/

Dependencies have to be created manually if you're using the Publisher, but we will update the dependency links in both directions if RDM or .NET 9 are updated. You can now however create them in Cloud:

https://docs.patchmypc.com/patch-my-pc-cloud/cloud-deployments/deploying-an-app-using-cloud/cloud-configurations-deployment-tab/dependencies-deployments

For further info - the reason we have this script to block the install if the pre-req is missing is to prevent users being upgraded to a version of the app that they can no longer use.



It would be helpful to include a note about any dependency requirements in the publishing report generated after the publishing sync. This note could contain warnings or information about necessary dependencies, allowing us to address issues proactively rather than waiting for a helpdesk ticket or dealing with an annoyed user :)

Potential feature request?


#6
Is anyone experiencing errors when the publisher tries to download Citrix Workspace 25.3.10.69? It appears that the update was released this past Monday, July 7, 2025, but I'm still encountering a hash mismatch error.

The hash of file downloaded is different than the file hash in our catalog. Hash errors happen when vendors release updates that aren't available in our catalog yet. This error should be resolved in the next catalog update.
#7
BTW we list all dependencies here:

https://patchmypc.com/kb/known-issues-considerations-when-using/

Dependencies have to be created manually if you're using the Publisher, but we will update the dependency links in both directions if RDM or .NET 9 are updated. You can now however create them in Cloud:

https://docs.patchmypc.com/patch-my-pc-cloud/cloud-deployments/deploying-an-app-using-cloud/cloud-configurations-deployment-tab/dependencies-deployments

For further info - the reason we have this script to block the install if the pre-req is missing is to prevent users being upgraded to a version of the app that they can no longer use.
#8
Confirmed the script matches so I would believe everything is good, just need to note that .Net 9 is required before installing RDM from the company portal.
#9
Quote from: NMcIntire96 on July 03, 2025, 09:59:55 AMI thought something was wrong with RDM and PatchMyPC as it was working great deploying to intune as a company portal app. I started to get reports that the app failed to install for people and also failed for my test laptop.

I eventually figured out the issue was that RDM now needs .Net 9 installed and seems that the PatchMyPC installer is not adjusted for this change and believe its still doing .Net 8.

I installed .Net 9 then my Company Portal app was able to install for RDM.

PatchMyPC needs to update the script you guys are using for this application to resolve this issue. Finding this form fully confirmed my suspensions and has confirmed that its not a issue on our end but is a issue on the PMYPC side as I have published other apps and those install as normal.

The script has in fact been updated, you should be seeing:

Script: https://patchmypc.com/scupcatalog/downloads/scripts/PatchMyPC-dotNetCheck.ps1
Arguments: -Version 9

When this script is working, the outcome should be expected that the deployment will fail if .NET 9 is not installed, so it sounds like it might in fact be working as intended?

If however you have a different script name or no script arguments, you may be suffering from a bug where the Publisher is not updating the script properly. Assuming you are using the on-prem Publisher, could you try disabling the app, press save, then re-enable it and select the right-click option 'Republish during next sync cycle', then perform another sync.
#10
Hi there, 
The update is now in the catalog :) Thank you for the heads up and sorry for the delay!