Patch My PC Publisher

Currently the only way of knowing which scripts are being used in the pre and post installation steps is to view the client-side logs. It would be useful to include an indication of the script name and location that has been set.

If I uncheck an item that had customizations accidentally, then recheck it, the customizations are wiped out even without hitting Apply or Save and Close. I understand this design might be so that you start fresh without customizations but maybe a...

When customizing an update, it is possible to enable the "Manage conflicting processes..." option and configure a desktop notification to require the user to close running apps. That notification is custom-made and does not intergrate seamlessly w...

this would allow certain pieces of software to only be installed on VM's, currently the only options are Only install on servers or only install on workstations. It would be useful for some pieces of software (VMTools as an example) to be pushed o...

Instead of we all have to vote up our preffered languages, then look for a way, where it is possible to enable several languages. this could be done in the right click meny for each update.e.g Firefox |  right click | enable language #1, lang...

Sometimes, some processes run as AppName-AppVersion.exeCustomers have to update the Conflicting process notification with each newer version. Would be good to be able to support wildcards for process names.

I want to propose a button/checkbox/process to ONLY create/update applications, separate from the publishing of software updates to the WSUS catalog. Although it makes perfect sense to create/update applications as part of a scheduled publishing s...

Having the number of enabled Apps and Updates visible on their respective tabs (somewhere suitable on the Publisher GUI of course) would be useful when comparing the number of Apps vs Updates that are activated. This would also be useful during re...

Please allow the option to dynamically deploy updates based on particular CVEs

Currently if you choose to exclude a vendor from auto-publishing rules, it is a point-in-time operation, ie only affecting the products supported at that time by PMPC. If PMPC subsequently adds support for new products from that vendor, those prod...