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

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Cody Mathis (Patch My PC)

Note that Click Share is marked with a 7 on our supported products page.

7 The product isnÔÇÖt supported anymore due to a download format change.
At this time this is how the script will function when generated by the Publisher.

We have plans to improve the Teams Machine Wide Installer, but at this time they are not in place.

What you have done is the current workaround.
Can you please make an idea on our uservoice portal linked below for the MSI version of this application and we will look at getting it added this month


We are using the EXE for real VNC server at this time so it would not natively support an MST file.

The MST option is made available for files which are an MSI.f

Do you have an MSI version of real VNC server that is made available to you as a paying customer?

This is the first we are hearing of this issue. We have tested against 20H2 without issue.

It might be good to submit a ticket and provide the list of logs in the following link - https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#application-troubleshooting-client-logs

Good catch! Interesting thing for Chrome to change.... I wonder if this has to do with the flash deprecation maybe?

I believe this is the first issue we are hearing of. You are welcome to submit a support case at the below URL and provide the logs described in the second UR: below.


Thanks for the heads up. We will get this updated in the next day or two.
Ahh, these are MSP.

We should have this updated later today to resolve this issue.

We also intend to add the ability to set the command line for MSP in the near future. Sorry about that!!
This is likely due to a new UWP app that Adobe is packaging with the software. We will be updating our commandline today but you should be able to add  INSTALLUWPAPP=NO to your command line to prevent these errors from happening.

It looks like this install fails in some cases when no user is logged on due to a new UWP app that is packaged with the software.

For now you can add  INSTALLUWPAPP=NO to your command line and it should resolve the issue.

We intend to add this to our catalog today as well.
What are you referencing?

The issue this thread references is in relation to a bug with a trailing space on the custom command line.
Rich, can you please open a support case for this and provide your settings.xml as well as your patchmypc.log file?

You can find the idea for this application below.


This item was accidentally added to the list of software prior to us having the work complete.
This is how the Teams Machine Wide Installer functions from Microsoft. They discuss this in their docs here https://docs.microsoft.com/en-us/microsoftteams/msi-deployment#pc-installation. With the notable line being: "The Teams MSI will place an installer in Program Files. Whenever a user signs into a new Windows User Profile, the installer will be launched and a copy of the Teams app will be installed in that user's AppData folder. If a user already has the Teams app installed in the AppData folder, the MSI installer will skip the process for that user."

So, any user will have Teams installed in their user profile the next time they log into their PC, which is typically when the PC reboots in most cases. They say 'new Windows User Profile' in the doc but it really just applies to the first time a user logs on after the Teams Machine Wide installer has been installed.

I hope this helps clear up what is happening.