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.

Messages - Cody Mathis

Pages: [1] 2 3 4 5 6

We do not provide support for troubleshooting Windows 10.

This forum is for the Patch My PC product that we sell.

Hi there!

What is the specific file that is triggering this?

I suspect this is PatchMyPC-ScriptRunner.exe. This file is updated somewhat regularly and because of this Symantec will trigger on it occasionally. Note the 'Current Reputation' and 'Historical Reputation' that 'There is some evidence that this file is trustworthy'

When we first update this binary we see the occasional customer who will have this flagged. As more customers update and Symantec is aware of the file the alerts stop based n their updated definitions.

For more context, ScriptRunner is our wrapper for doing installations and does have bits of code that can do a lot of tasks as system and can be a trigger to AV. This includes user impersonation and querying various bits of system information.

Are you possibly able to trust a signing certificate?


We do not officially support using this for other purposes, but you are more than welcome to interpret the package.xml files and attempt to use them for your own purposes assuming you have a PMPC licence.

We would not provide support.


This is due to a bug that was introduced in version of the publisher.

We have just released version of the Publisher which resolves this issue.

Can you please update and try again?


This is a very interesting idea!

Can you please submit this on our idea portal?

Any details you can provide would be great.

Pre-3.0 is effectively a different app and is not an 'update' but rather an 'upgrade' which would require an uninstall of the old and install of the new. This is why we have this limitation in place. Our updates must support a clean update from a previous version.

Regarding UWP applications, this is not something that is currently on our roadmap.


The current version of Google Chrome in our catalog is 90.0.4430.93. You may have an issue with your current Publisher installation or configuration if you are not seeing this version.

Can you please send your patchmypc.log file from the installation directory of the publisher to [email protected]



This will definitely work!

It will rely on the package.xml file being available, as well as the DLL Files which are packaged alongside scriptrunner.

We also recently made changes so that the default behavior of scriptrunner is /installpackage which means if you have all the files in place you can simply double click scriptrunner.

If you are unable to get this to work I encourage you to put in a support ticket with the below link with details.

We do not currently have Microsoft Teams in our update catalog, it is only there as a base install.

It is listed in the catalog in such a way as to prevent it from being published as an update. We address this in our known issues and considerations page.

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 -

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

Pages: [1] 2 3 4 5 6