Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Applies to: Patch My PC Publisher
Welcome to the Reference section for the Patch My PC (PMPC) Publisher.
This section contains articles providing technical reference-related information for PMPC Publisher.
Official product documentation for Patch My PC
Applies to: Patch My PC Cloud
The App Catalog page of the Patch My PC (PMPC) Cloud Portal lists all of the apps we currently support, which you can deploy and manage.
From the App Catalog page, you can:
Search for a specific app.
Add a new Custom App by clicking Add App.
Modify your view of the App Catalog and whether you see it as a grid view (the default view) or a list view.
Sort the App Catalog by App Name (both forward and reverse sort) and the date apps were Last Updated (both forward and reverse sort).
Apply Filters to help you refine the results you see.
.
Applies to: Patch My PC Cloud
If an app supports built-in auto-updates, this tool will be available, but the Disable Self-Update checkbox will be selected by default, disabling any auto-updates.
To manage the settings for the Built-in Auto Updates tool:
Applies to: Patch My PC Cloud
Patch My PC (PMPC) Cloud can be used to deploy apps using Microsoft Intune.
To deploy an app using PMPC Cloud:
Our all-in-one solution for managing third-party application updates across your enterprise.
Streamlining your app management with a single SaaS portal that seamlessly integrates with our Publisher and Intune.
Our real-time vulnerability alerting and awareness tool that helps Security and IT teams cut through the noise, respond faster, and stay aligned.
Our powerful suite that transforms your data into dynamic, visually rich dashboards, offering everything from software and update compliance to detailed hardware and device insights, trend analysis, and threat detection.
Our free, easy-to-use tool that helps analyze your WSUS & ConfigMgr environments for known issues and provides recommended best practices.
Helps you calculate the Return on Investment on the products supported in our current catalog you are using in your environment.
Contains reference articles that apply to multiple products.
Applies to: Patch My PC Publisher
A Data flow diagram for Patch My PC (PMPC) Publisher can be downloaded from the Additional Information section of our Trust Center.
Applies to: Patch My PC Cloud
Important
This documentation is for a pre-release feature still under development and, therefore, incomplete. As a result, both functionality and documentation are subject to change.
Once this feature is released, it will be announced and this banner removed.
As you may still need to deploy migrated applications to on-premises clients through ConfigMgr we do not recommend you perform any kind of cleanup post-migration.
Click the Built-in Auto Updates tool.
Configure the required settings.
If you do not want to configure any additional settings, click Next to move to the Assignments tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
Sign in to the portal at https://portal.patchmypc.com/
Locate the required application on the App Catalog page.
Tip
Use the Search field to help you locate the app.
Click the app to open its properties.
Click Deploy to start the Deployment Wizard.
The General Information tab is displayed, which needs to be completed.
Applies to: Patch My PC Cloud
Welcome to the Deployment section for Patch My PC (PMPC) Cloud.
Important
You need to Onboard to Intune Apps before you can use the Deployments feature.
Applies to: Patch My PC Cloud
The Role Scope Tags tool of the Patch My PC (PMPC) Cloud deployment wizard allows you to leverage Intune Role Scope Tags (Scope Tags) in your deployments to help control which Intune admins can manage a specific deployment.
Important
Before you can use a Scope Tag in a PMPC Cloud deployment, it must have already been created in the Intune admin center. Follow the process of for more details and information on Scope Tags.
If you manage Intune using PMPC Cloud, you should avoid performing any actions in the Intune admin center that can be performed in PMPC Cloud, as doing so will cause unwanted behavior.
To add Role Scope tags:
Add the .
Click the Role Scope Tags tool.
In the Profile Name field, either:
Start typing the name of the relevant Scope Tag, then click the checkbox beside it to select it.
Click the dropdown to see a list of existing Scope Tags and click the relevant checkbox(es) to select it.
Tip
You can click the X beside a Scope Tag in the Profile Name field to delete it.
The number of profiles selected is shown beside the Role Scope Tags tool.
If you do not want to configure any additional settings, click Next to move to the tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
Applies to: Patch My PC Cloud
All Patch My PC (PMPC) Cloud deployments include a status.
Important
As PMPC Cloud is performing the deployment and not Microsoft Intune, you can only view the status of these deployments from within the PMPC portal. The status of PMPC Cloud deployments is not visible from within the Intune admin center.
To see the status of a deployment:
Applies to: Patch My PC Cloud
Once the Deployment Templates () feature of Patch My PC (PMPC) Cloud has been enabled for your PMPC Cloud company and you have created at least one template, you can start using templates for your new deployments.
Applies to: Patch My PC Publisher
Welcome to the official home page for Patch my PC (PMPC) Publisher.
Important
We are currently reviewing and migrating all of our current Publisher-related content to this space, which should be considered as the most up-to-date.
Once content has been migrated to this location, it will be deleted from the old location to avoid duplication and confusion.
Applies to: Patch My PC Cloud
Important
This documentation is for a pre-release feature still under development and, therefore, incomplete. As a result, both functionality and documentation are subject to change.
Once this feature is released, it will be announced and this banner removed.
The Migration feature of Patch My PC (PMPC) Cloud allows you to migrate the following items from a Microsoft Configuration Manager (ConfigMgr) hierarchy to a PMPC Cloud company:
Applies to: Patch My PC Cloud
Welcome to the Reporting section for Patch My PC (PMPC) Cloud.
Important
This documentation is for a pre-release feature still under development and, therefore, incomplete. As a result, both functionality and documentation are subject to change.
Once this feature is released, it will be announced and this banner removed.
Applies to: Patch My PC Cloud
If an app appears on the Unmanaged tab of the Discovery node, it means there is no matching deployment in either Patch My PC (PMPC) Cloud or our on-premises Publisher for that app.
To deploy an app listed on the Unmanaged tab of the Discovery node of Patch My PC (PMPC) Cloud:
Navigate to the Discovery node.
Click Deploy beside the relevant app.
Applies to: Patch My PC Cloud
Once Patch My PC (PMPC) Cloud has successfully deployed an app, you need to decide how to manage any updates to that app.
Applies to: Patch My PC Cloud
Important
This documentation is for a pre-release feature still under development and, therefore, incomplete. As a result, both functionality and documentation are subject to change.
Once this feature is released, it will be announced and this banner removed.
ConfigMgr applications that can be migrated to Patch My PC (PMPC) Cloud and deployed as one of our apps have a
Applies to: Patch My PC Cloud
All administration-related tasks are performed from the Patch My PC (PMPC) Cloud portal.
When you sign in to the PMPC portal (), the App Catalog node is selected by default.
The Migration feature is designed to support the migration of applications from Microsoft Configuration Manager (ConfigMgr) to Microsoft Intune, with a focus on modernization rather than simply transferring technical debt.
As part of the migration process, we want to help you identify outdated applications or those exposed to known Common Vulnerabilities and Exposures (CVEs). We will also make recommendations and assist in upgrading to the latest supported, secure versions available through the Patch My PC Catalog.
All applications we migrate will benefit from an additional layer of customization to ensure they remain manageable, secure and fit for the modern desktop.
We have two approaches for migrating applications from ConfigMgr to Intune:
Wherever possible, we try to find a match for ConfigMgr applications to an app that already exists in our catalog, using various methods and metadata. If a match is found, you can then deploy this version to Intune rather than the older version, which may be vulnerable to exploits, out of support, etc.
When we migrate ConfigMgr applications using this method, we include the migration of any installation arguments, customizations, and command lines you have defined for the ConfigMgr application.
The end result is that you now have a version of the app deployed that can be managed and kept up to date for the life of that app.
For those ConfigMgr applications that we cannot find a direct match to an app in our catalog, we can still migrate it, but as a PMPC Custom App.
When we migrate ConfigMgr applications using this method, we migrate the exact version and include the migration of all installation arguments, customizations, and command lines you have defined for the ConfigMgr application.
You will be able to modify and manage the app from within the PMPC Cloud portal and take advantage of the various customizations and features of PMPC Cloud Custom Apps.
An overview of the deployment feature
How to deploy an app
How to deploy the same app with multiple configurations
How to create a deployment without assignments
How to use a Template in your deployments
All about the Update Rings feature
Monitoring the status of a deployment
Managing updates to successful deployments
Deployment management tasks










Sign in to the portal at https://portal.patchmypc.com/.
Navigate to the Deployments node.
The Deployments page loads, showing all current deployments. The Status column shows the current status of each deployment, which will be one of the following:
Success – The application was successfully created in Intune.
In Progress – The application is being created in Intune.
Failed – The application failed to be created in Intune.
To configure a new deployment to use a template:
Follow the relevant deployment scenario.
Once the Deployment Wizard has started, click Apply Template
On the Apply Template screen, select the radio button beside the template you want to apply, then click Apply.
The Deployment Wizard is redisplayed along with the Success - Template ‘<template_name>’ applied notification.
If you encounter any documentation-related issues or have any feedback, feel free to email [email protected].
The configuration guides will help you setup Patch My PC Publisher (Publisher) with Microsoft Configuration Manager and Microsoft Intune.
To help get you started, we provide a few different guides (documented or video) to help you install the Patch My PC Publisher.
Don't feel like going it alone? You can schedule a setup call with a Patch My PC engineer to help you install correctly first-time in your environment.
Are you installing the product with Configuration Manager? No problem, click the link below for our Configuration Manager guide! The guide includes a text-based version, video, and the ability to directly schedule a setup call with an engineer!
Are you installing the product for Microsoft Intune? No problem, click the link below for our Intune standalone guide! The guide includes a text-based version, video, and the ability to directly schedule a setup call with an engineer!
Curious about what fixes and new features we've added to the Publisher? You can check out our release history in the release history section for our Production and Preview releases:
You can also stay up-to-date by subscribing to our catalog release newsletter and RSS feedback to find out the moment we update our catalog with new products and updates!
If you're just getting started and need help learning the product no problem we can give you a live interactive demo where we will explain everything you need to know about our product from a deep dive inner workings of the product to licenses and security. 🔒
So you've seen a demo, and you're ready to try the product out in your environment. To get you started off right we offer a FREE guided installation of the product in your environment. We strongly encourage all customers to bring an engineer along for the ride to ensure you get the maximum value out of our product and to ensure smooth sailing. ⛵
Something seems not quite right? Maybe you want to brush up and learn about all those cool new features we've been releasing since the last time you had a demo. No worries, you can schedule a review call any time you like and our team will be happy to help you study up and help make sure your environment is in top shape. 🎩
When all else fails and you can't find the answers you need we will always be there for you. While we do have a lot of written knowledge articles sometimes those just aren't enough. If you ever find that to be the case, or something is going disastrously wrong you can always open a support case with our talented team of experts.
Not everything always works in pure documentation format and for this, we have some links to our most commonly used resources on our website including
Got questions about licensing, subscription types, or how we handle security? Don't worry we get asked those questions all the time.
Ready to head on back to our home page? Don't worry we booked you a ride there.
Curious about where we are going and what we are planning to do we make all that information publicly available on our live roadmap.
Is there something we are missing? Maybe a new document, a new feature, or a new app? If you head on over to our user voice you can submit new ideas for us and make recommendations.
Want to learn more about who we are and what we do? Head on over to our About Us page to learn more about who we are and our company's core values.
The Deployment Wizard starts.
Follow the Deploying an App process.
Once you have deployed an app, it will appear in the Managed tab.
Move the assignments for the current version over to the new version.
Install the new version on the relevant devices.
Also, if a deployment has App Dependencies (either this deployment has dependencies on another deployment or another deployment has dependencies on this deployment), at the time the Sync Schedule runs, if a newer version is found, we:
Create a new version of the app in your Intune tenant.
Move all the dependencies for the current version over to the new version.
Install the new version on the relevant devices.
The next time the Sync Schedule runs, that is when we delete the old version of the Intune app, which includes removing it from any Enrollment Status Page (ESP) profiles.
All update-related tasks for an app are performed at the deployment level from the Deployments node of the PMPC portal by:
Navigating to the Deployments node.
The Deployments page is then displayed, showing any existing deployments and allowing you to:
Once you click Migrate to migrate a ConfigMgr application to a PMPC Catalog App, the Deployment Wizard starts, and you can follow the Deploying an App using Cloud section, but please note the following:
As a double-check, you should check that the information on each tab is correct before clicking Next.
On the Configurations tab, under the Install Parameters tool/section, check that the Additional Argument field is correct and includes any required additional arguments/command line options.
On the Assignments tab, you can click ConfigMgr Assignment List to see a list of the current assignments in ConfigMgr, so you can then review this and set these up in Intune accordingly.
Important
In Private Preview, we are not matching ConfigMgr groups, assignments and Collections to Entra ID groups. You will need to manually configure your assignments.
Tip
If you don’t want to deploy this app now, just click Install App under App Without Assignments on the Assignments tab, then click Migrate to just create the app in Intune. When you are ready, you can edit the Deployment and add the required Assignment types.
Once you have added your assignments, click Migrate and the Deployment Created, Migration Pending notification is shown.
The Status field also updates to show In Progress as the deployment is being created, with any required content (such as extra files) being zipped and sent to Azure Blob Storage.
You can also monitor the progress of the deployment by clicking the Deployments node and watching for the Status of the deployment to change to Success.
Tip
To see the migrated app in Intune, within the Microsoft Intune admin center navigate to:
Home > Apps | Windows > Windows | Windows Apps > <app_name>
Applies to: Patch My PC Cloud
Some large organizations want to be able to create deployments in Intune Apps for Patch My PC (PMPC) Cloud without any assignments.
Then, their local IT organization adds and manages the assignments to the relevant deployments to meet their needs by using Intune admin center.
To create a deployment with no assignments:
Follow the Deploy an App process until you reach the Assignments tab where you can add an assignment. When you click Add Assignment, you will see the App Without Assignment sub-menu containing the following two items: • Install App - Allows the Intune admin to add Required, Available, or Uninstall assignments from within the Intune admin center. • Update Only App - Allows the Intune admin to add only an Update Only assignment from within the Intune admin center.
Tip
You can also with the App Without Assignments options configured. Then when you create the deployment, simply click Apply Template and select the relevant template to have its settings applied to this deployment.
Select the relevant option.
Uncheck the Copy-Forward checkbox if required. This checkbox is checked by default, which means whenever we see any manually created assignments on Intune, when we update the app, we’ll automatically copy forward all the assignments from the previous version to the new version.
Click Deploy and wait for the deployment to complete successfully.
Once the deployment has successfully completed, if you look in the Intune admin center you will see that the app has been created without any assignments.
Your local IT teams can now follow the process to add the relevant assignments for this app.
Important
The current release of this feature has the following restrictions:
A deployment cannot contain both regular assignment types and no assignment types.
Applies to : Patch My PC Cloud
Welcome to the Update Rings section for Patch My PC (PMPC) Cloud.
This section contains articles covering the various Update Ring-related tasks for PMPC Cloud.
Applies to: Patch My PC Cloud
Welcome to the Events section for Patch My PC (PMPC) Cloud.
Applies to: Patch My PC Cloud
The Retention Policy tool of the Patch My PC (PMPC) Cloud deployment wizard allows you to determine how many versions of an app (both Windows and macOS) you want to keep. If deploying a later version of an app causes issues, you can redeploy an older version.
By default, PMPC only retains the latest version of an app in your environment. Configuring a Retention Policy allows you to keep the current version, plus the number of configured versions as set by the Retention Policy.
For example, setting a Retention Policy of 1 for Google Chrome would mean you always have n-1 versions of Chrome, the latest and the previous version, until a newer version is deployed.
Important
The previous version (n-1) of an app may temporarily remain visible in Intune even when a Retention Policy is not configured.
The portal only deletes the previous version during the next , not in the same sync that creates the new version.
This behavior is intentional as it prevents situations where if the new version (n) fails to package, no version of the app remains available.
To configure a PMPC Cloud deployment to use a Retention Policy:
Add the .
Click the Retention Policy tool.
In the Versions to Retain box, either type the required number or use the controls to configure the number of versions of this app you wish to retain in your environment.
Tip
See for details on how to check within Intune that the correct number of versions of an app are being retained as defined in your Retention Policy.
If you do not want to configure any additional settings, click Next to move to the tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
Applies to: Patch My PC Cloud
Use a Filter to help you find only the relevant Events you require.
Click the funnel button in the header of the Events page.
The filter sidebar opens.
Configure your required filters, then click Apply All Filters.
Only the Events matching the filter criteria are displayed.
Tip
When a filter is applied, a green dot appears beside the Filter button.
Click Clear All at the bottom of the filter box or navigate to a different page of the portal.
Verify the green dot beside the Filter button has gone.
Applies to: Patch My PC Cloud
Important
This documentation is for a pre-release feature still under development and, therefore, incomplete. As a result, both functionality and documentation are subject to change.
Once this feature is released, it will be announced and this banner removed.
ConfigMgr applications that can be migrated to Patch My PC (PMPC) Cloud and deployed as one of our Custom Apps have a Match Type of Custom App.
Once you click Migrate to migrate a ConfigMgr application to a PMPC Custom App, the Custom Apps Deployment Wizard starts, and you can follow the section, but please note the following:
As a double-check, you should check that the information on each tab is correct before clicking Next.
On the Configurations tab, under the Install Parameters tool/section, check that the Additional Argument field is correct and includes any required additional arguments/command line options.
On the Assignments tab, you can click ConfigMgr Assignment List to see a list of the current assignments in ConfigMgr so you can then review this and set these up in Intune accordingly.
Tip
If you don’t want to deploy this app now, just click Install App under App Without Assignments on the Assignments tab, then click Migrate to just create the app in Intune. When you are ready, you can edit the Deployment and add the required Assignment types.
On the Assignments tab, if you do not want to set up any Detection Rules, you can click Migrate. If you do want to set up Detection Rules, you should click next to proceed to the Detection Rules tab.
On the Detection Rules tab, you can either continue with the Use Custom option, i.e. what we detected in ConfigMgr, or select the Patch My PC Default (Recommended) option instead and let us use our recommended settings.
When you click Migrate, the Deployment Created, Migration Pending notification is shown.
The Status field also updates to show In Progress as the deployment is being created, with any required content being zipped (such as the primary installer file and any extra files) and sent to Azure Blob Storage.
You can also monitor the progress of the deployment by clicking the Deployments node and watching for the Status of the deployment to change to Success.
Tip
To see the migrated app in Intune, within the Microsoft Intune admin center navigate to:
Home > Apps | Windows >Windows | Windows Apps > <app_name>
Applies to: Patch My PC Cloud
Patch My PC (PMPC) Cloud supports the following methods for deploying apps:
The PMPC App Catalog contains apps for which there is a publicly accessible download of the installer that we can deploy and update. In the majority of cases, you should use the process to deploy your apps.
Some apps do not publish a publicly accessible download. These are typically apps:
You need to pay for.
The installer is behind a paywall that requires an individual login and password.
The vendor uses a compressed file for its installer.
We refer to such apps as Binary-free apps and you should follow the process.
If you have your own installer (EXE or MSI) that you want to deploy, then you should follow the and processes.
Applies to: Patch My PC Cloud
Important
This documentation is for a pre-release feature still under development and, therefore, incomplete. As a result, both functionality and documentation are subject to change.
Once this feature is released, it will be announced and this banner removed.
Applies to: Patch My PC Cloud
To use Patch My PC (PMPC) Cloud, you need:
An Internet connection that can access Microsoft Azure services and the Patch My PC (PMPC) Cloud Platform (https://portal.patchmypc.com/).
A Microsoft Entra ID tenant
An Enterprise Plus, Enterprise Premium, or Managed Service Provider (MSP) Plus subscription.
Important
We no longer allow customers whose Entra ID domain starts with "m365x" to start a Patch My PC (PMPC) Cloud trial. Such customers no longer see the option to start PMPC Cloud Trial and will either need to enter a PMPC Cloud license key or activate their license using their on-premises Publisher license key.
See for more information on our different subscription levels.
A minimum of two users, who will be granted privileges within PMPC Cloud.
Applies to: Patch My PC Cloud
Important
This documentation is for a pre-release feature still under development and, therefore, incomplete. As a result, both functionality and documentation are subject to change.
Once this feature is released, it will be announced and this banner removed.
To use the Migration tool, you need to have a:
Configuration Manager Primary Site running any version we .
Copy of our On-Premises Publisher (Publisher), version 2.1.50.0 or later.
A valid license. Enterprise+ or Enterprise Premium.
Enterprise+ license allows you to:
Official product documentation for Patch My PC Cloud.
Welcome to the official home page for our Cloud-based solution, Patch My PC Cloud.
Applies to: Patch My PC Cloud
The Scripts tool of the Patch My PC (PMPC) Cloud deployment wizard allows you to configure settings for install and uninstall scripts.
Applies to: Patch My PC Cloud
Important
This documentation is for a pre-release feature still under development and, therefore, incomplete. As a result, both functionality and documentation are subject to change.
Once this feature is released, it will be announced and this banner removed.
There are two different types of application migrations we currently support in Patch My PC (PMPC) Cloud, depending on the results of the Migration scan:
Applies to: Patch My PC Cloud
The Discovery feature of Patch My PC (PMPC) Cloud allows you to see which apps in our App Catalog are installed in your environment, including any Binary Free Apps or Custom Apps you may have added.
Once an app has been discovered, you can decide whether to manage it using PMPC Cloud.
Applies to: Patch My PC Cloud
Once onboarded to Patch My PC (PMPC) Cloud, you can modify certain aspects of your company-related information.
All user company-related tasks are performed from the Company node of the portal, which is accessed by:
Sign in to the PMPC portal .
Navigate to Settings | Company
Applies to: Patch My PC Cloud
Welcome to the Discovery section for Patch My PC (PMPC) Cloud.
Important
You need to before you can use the Discovery feature.
Applies to: Patch My PC Cloud
Important
This documentation is for a pre-release feature still under development and, therefore, incomplete. As a result, both functionality and documentation are subject to change.
Once this feature is released, it will be announced and this banner removed.
The way each of the nodes in the Reporting
Applies to: Patch My PC Cloud
Important
This documentation is for a pre-release feature still under development and, therefore, incomplete. As a result, both functionality and documentation are subject to change.
Once this feature is released, it will be announced and this banner removed.
Before you can perform a migration using the Patch My PC (PMPC) Cloud Migration
Applies to: Patch My PC Cloud
Important
This documentation is for a pre-release feature still under development and, therefore, incomplete. As a result, both functionality and documentation are subject to change.
Once this feature is released, it will be announced and this banner removed.
The Reporting feature of Patch My PC (PMPC) Cloud allows you to see a wealth of information about your organization that you can use to monitor, maintain, and enhance your environment.
Data is summarized into several key areas known as Statistics, which show headline numbers, and donut charts, which show a summary of data broken down by key values.
Hovering your mouse over a segment of a donut chart shows you information for that segment, including the number of records within it.
Clicking either a statistic or a segment of a donut chart displays a table showing the individual records.
From this ClickThrough, you can:
Search for a specific record within the table
Sort a column
Click an individual record to display more information about it.
Using the Device ClickThrough for an individual device allows you to view more information about the device. We also have more detailed views for Software Updates.
Like other areas of the Portal, you can:
Click through pages by clicking the relevant arrow.
Set the Items per page to your liking.
By default, Intune data is refreshed on average once day. To refresh your data, click Refresh Data.
An overview of the Update Rings Feature
Explains how Update Rings are created
How the Sync Schedule Affects Update Rings Explains how the Sync Schedule configuration affects Update Rings
Explains how Update Rings handle new versions
How to create Update Rings for a deployment
How to edit Update Rings configured for a deployment
How to view the Update Rings configured for a deployment
Check if an Update Ring has been created How to check if an Update Ring has been created
Update an Update Ring How to manually update an Update Ring immediately
How to convert an existing deployment to use Update Rings
How to delete one or more Update Rings for a deployment
Reference section for the Update Rings Feature
An overview of the Events feature
How to search for an Event
How to filter Events
How to export Events
How to sort Events
How to find out more information about an Event
How to change the number of Events shown on a page
How to navigate between pages of Events
Details the various Events generated
Use the On-Premises Publisher to retrieve a list of applications from your ConfigMgr site and send it to your PMPC Cloud Company.
Use PMPC Cloud to review and evaluate if an application can be migrated to Intune.
Enterprise Premium license allows you to:
Perform all the same migration functions as the Enterprise+ license, and also the ability to click Migrate (when supported) to automatically deploy the application to Intune as either a PMPC App or a PMPC Custom App.
PMPC Cloud Company:
That has the Migration feature enabled (if you don’t see the Migration node in your portal, then this company hasn’t had this feature enabled).
To which you have an account that has been granted the Full Admin user role (either by having this account created directly in the Cloud Company or by being a member of an Entra ID Group that has been granted this role).
An overview of the Reporting feature
Gain an understanding of how the Reporting feature works
An overview of the Migration feature
What's required to use the Migration feature
How to setup the Migration feature
How to perform a PMPC Cloud Migration
How to migrate a ConfigMgr app to a PMPC App
How to migrate a ConfigMgr app to a PMPC Custom App
What to do once Migration is complete
























Applies to: Patch My PC Cloud
If your deployments are using App Dependencies and both the deployments for the child and parent apps have Update Rings enabled, the following behavior occurs:
Each version of an app for the child deployment with update rings enabled must depend on the parent app with the version related to the last ring of the parent deployment.
When the last ring of the parent app is updated to a new version, we also move over the dependencies associated with the last ring.
If Update Rings are disabled for the parent app, we rebuild the dependency with the app that used to be Ring 1, with the lowest delay/the latest version.
If the delay for the ring with the oldest version is decreased and this ring becomes the ring with the newest version, we will delete the previous dependency and build the dependency with the app that, after editing, has the oldest version.
Modifying an existing deployment with a Retention Policy configured will only affect the current version, not all previous versions. For example, if you edit a deployment and add an extra file, the file is only added to the latest version, not all previous versions.
You should avoid deleting versions of apps manually using the Intune admin center. Inadvertently deleting a previous version from Intune will not break the Retention Policy for the deployment. When a newer version is deployed, we will delete the relevant previous version(s) accordingly to keep everything in sync.


If you have a regular deployment with update rings enabled, you cannot edit that deployment, disable update rings, remove all the assignments and then add a new no assignment type.




Scripts will be run in the same context as the application.
Each install script is limited to 1 MB per script, with a total size limit of 4 MB for all scripts.
There is a limit of 50,000 characters per script.
We currently support the following script types:
.BAT
.CMD
.PS1
.VBS
Important
Currently, scripts containing "${env:ProgramFiles(x86)}" or "${env:ProgramFiles}" cannot be uploaded as Cloudflare is falsely identifying them as a false positive related to Log4j exploits. We are actively working with them to resolve this, but as this is outside our control, we cannot provide an estimated resolution time.
To work around this issue, see the Resolution section of "TypeError: Failed to fetch" error when trying to upload a Pre or Post Script.
To add a script:
Add the Scripts tool.
Click the Scripts tool.
Click Add beside the relevant script option to add a script, then configure the required settings as per the relevant articles:
Pre-Install Script - a script that can be run before the installer runs.
Post-Install Script - a script that can be run after the installer runs.
Pre-Uninstall Script - a script that can be run before the uninstaller runs.
Post-Uninstall Script - a script that can be run after the uninstaller runs.
If you do not want to configure any additional settings, click Next to move to the Assignments tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
The process to start a migration is the same regardless of the type of target app that will be created in PMPC Cloud/Intune.
To perform a migration:
Sign in to your PMPC Cloud Company.
Navigate to Migration
Find the application you want to migrate.
Tip
You can use the Search box and start typing the name of the application to help you find it.
Alternatively, you can click the filter button and select the checkbox beside the Match Type of the application you wish to migrate (PMPC App or Custom App). Then, click Apply All Filters to view only the matching applications.
If a warning triangle is not present in Info column for that application, go to step 11.
If a warning triangle is shown in the Info column, click it to open the properties of the application.
On the properties of the application, locate the tab(s) with a warning triangle beside them.
Click the relevant tab and look for the items with the warning triangle beside them.
Review the warning and determine your course of action.
If you are happy to proceed with the migration, go to step 11.
If you cannot proceed with the migration, then close the property of the application and click Cancel to close the Migration Wizard. You will now need to determine how you address the warnings to determine your next course of action for this application.
Click Migrate beside the relevant instance of the app.
If the application is being migrated to a PMPC App, follow the process.
If the application is being migrated to a PMPC Custom App, follow the process.
When you connect your PMPC Cloud Company to your Intune tenant, we retrieve the latest copy of Intune’s discovered apps report, which contains an inventory of all installed apps on your devices.
This report includes the following information about each app:
Name
Version
Device count (how many devices the app is installed on)
Vendor i.e. who publishes the app.
We then perform a mapping process of the report’s contents (based on the Intune app name and app version properties) to check if each app matches a publicly available app in our App Catalog or any Custom/Binary Free Apps you have uploaded.
If there is a match, the app is marked as either:
Unmanaged – Apps identified as being in our App Catalog but aren’t currently managed by us as there is no matching deployment in our portal.
Managed – Apps identified as being in our App Catalog and where there is a matching deployment in our portal created by either PMPC Cloud or our on-prem Publisher.
Any matching apps are shown on the relevant tab of the Discovery node.
Tip
If you look in the Events node, you will see the Intune Application Discovered event which is created the first time Discovery is run in your PMPC Company.
Intune only updates its discovered apps report once a week. Because of this, PMPC Cloud will initially query Discovery data for your tenant once a week, randomly selecting a day between 1 AM and 5 AM based on the time zone of your PMPC company. All subsequent weekly updates will occur on the same day and time as the first discovery collection.
Important
If you create a deployment for an Unmanaged app, you will only see it move to the Managed tab either:
On the following Sunday (after the update scan runs)
When you follow the process.
Make any required changes, then click Save.
The Success - Company information updated notification is shown.

Overview of the PMPC Cloud discovery feature
How to deploy an app listed on the "Unmanaged" tab
How to administer apps discovered as "Managed"
How to manually refresh discovery data
Examples of how various apps appear on the “Managed” tab
You also need to ensure that the Enable Application Migration checkbox on the Cloud tab is checked.
By default the Publisher polls the ConfigMgr Site Database every 60 minutes for application changes.
Important
If you click Disconnect on the Cloud tab of the Publisher, all of the data for the Migration feature will be deleted from your PMPC Cloud company. You should avoid doing this until you have completed the migration of everything you need to migrate from ConfigMgr to PMPC Cloud.
Next, sign in to your PMPC Cloud company and verify that the Migration node is visible.
Tip
The following log files can be used for more information and for troubleshooting the migration feature:
"%ProgramFiles%\Patch My PC\Patch My PC Publishing Service\Logs\PatchMyPC-AppMigrationService.log”
"%ProgramFiles%\Patch My PC\Patch My PC Publishing Service\Logs\PatchMyPC-CloudFileUploadBackgroundService.log”
"%ProgramFiles%\Patch My PC\Patch My PC Publishing Service\PatchMyPC.log”
Your license type determines the name of the reporting node in your portal:
If you are either using an Enterprise Premium license or you are an Enterprise Plus customer who has signed up for an Enterprise Premium Trial, the Cloud Reporting feature will be named Advanced Insights and consist of the following sub-nodes, each of which contains the most common datasets organizations typically want to report on:
Home - Contains a summary of all of the information from the other tabs.
Updates - Contains a summary of the most common software update-related information.
Hardware - Contains a summary of the most common hardware-related information.
Intune - Contains a summary of the most common information from your Intune tenant.
If you are using the Enterprise Plus license, the Cloud Reporting feature will be named Patch Insights, and you will only be able to access the Intune sub-node, which contains a summary of the most common information from your Intune tenant.
Important
The data in the Intune sub-node is populated using Microsoft Graph calls to your Intune tenant.
For data to appear and update in the other Reporting sub-nodes, you need to install our client on any devices you wish to collect data from. See Patch My PC Client for more information.
See Working with Cloud Reporting for more details on working with the data presented by the Reporting feature.
Latest product and feature updates
What's required to run our cloud product
How to sign up for a free trial of Patch My PC Cloud
The App Catalog contains all of the apps we currently support
Deploying and managing apps
Using the Update Rings feature
Understanding and working with events
Using the Migration feature to migrate from ConfigMgr to Intune
See which apps in our App Catalog are installed in your environment
Learn how Cloud can report on and manage your environment
Performing various admin-related tasks
Deploying and managing your paid apps
Deploying and managing your in-house apps
Deploying and managing apps using Intune
Managing the macOS devices in your environment
Learn all about the MSP feature of Cloud
When things go wrong, how to fix them
Various reference articles about the product and its features
Definitions for the various terms and abbreviations we use
Applies to: Patch My PC Cloud
The Dependencies tool of the Patch My PC (PMPC) Cloud deployment wizard allows you to create dependencies within a deployment, whereby the app being deployed requires one or more other apps to have already been installed on the targeted resource before it can be deployed.
If the required app(s) (known as the parent) have not already been installed on the device, they will automatically be installed before the app that is being deployed (known as the child app) is installed.
Important
Before you can create an App Dependency in a PMPC Cloud deployment, the deployment for the parent app(s) must:
exist already
have been deployed successfully
To add a dependency:
Add the .
Click the Dependencies tool.
From the Add Dependencies field, either:
Start typing the name of the relevant app that this app depends on already being successfully installed on the target device.
Click the dropdown and select the relevant app that this app depends on already being successfully installed on the target device.
The selected app appears under the Parent Deployment section.
Repeat Step 3. to add any additional dependencies.
Tip
Once a dependency has been configured, you can view it as part of the app’s properties in the Microsoft Intune admin center.
For more information, see of .
Warnings
If we encounter any problems with app dependencies, we display a yellow exclamation mark (“!”) warning. Hovering over this will display more information.
We typically generate warnings in the following scenarios:
If you do not want to configure any additional settings, click Next to move to the tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
Applies to: Patch My PC Cloud
The Categories tool of the Patch My PC (PMPC) Cloud deployment wizard allows you to leverage Intune App Categories (Categories) in your deployments to help users find apps in the Company Portal.
To add a Category to a deployment:
Add the .
Click the Categories tool.
Go to Step 6. to add a new category or in the Add Category field, either:
Start typing the name of the relevant Category, then click the checkbox beside it to select it.
Click the dropdown to see a list of existing Categories and click the relevant checkbox(es) to select it.
Tip
You can click the X beside a Category in the Add Category field to delete it from the list.
Repeat this process to add any additional categories.
Go to to step 8. if you do not want to add a new Category.
To add a new Category, type its name in the Add Category field.
Press ENTER and the Success – The category “<category_name>” has been created notification is shown, confirming the new category has been added to both Intune and this deployment.
The number of categories selected is shown beside the Categories tool.
If you do not want to configure any additional settings, click Next to move to the tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
Applies to: Patch My PC Cloud
The ESP Profiles tool of the Patch My PC (PMPC) Cloud deployment wizard allows you to configure your deployments created in our portal to be part of one or more profiles configured on the Enrollment Status Page (ESP) of the Microsoft Intune admin center.
To configure a PMPC Cloud deployment to use an ESP Profile:
Add the .
Ensure the ESP Profile(s) you want this deployment to belong to have already been created in Intune.
Click the ESP Profiles tool.
In the Add Profile field, either:
Start typing the name of the relevant ESP Profile, then click the checkbox beside it to select it.
Click the dropdown to see a list of existing ESP Profiles and click the checkboxes beside the relevant profiles to select them.
The selected ESP Profile(s) are added to the Add Profile field.
Tip
You can click the X beside an ESP Profile in the Add Profile field to delete it from the list.
Also, the number in brackets shows the number of apps currently added to an ESP Profile, with 100 being the maximum.
Repeat this process to add any additional ESP Profiles.
The number of ESP Profiles selected is shown beside the ESP Profiles tool.
If you do not want to configure any additional settings, click Next to move to the tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
Applies to: Patch My PC Cloud
Once an app appears on the Managed tab of the Discovery node, it means there is at least one matching deployment in either Patch My PC (PMPC) Cloud or our on-premises Publisher for that app.
To administer a Managed app:
Navigate to the Discovery node.
Click the Managed tab.
The list of discovered managed apps is shown.
The following columns are shown on this page:
Tip
Hovering over either the value in the Assigned To All column or Edit button for a deployment will show a tooltip providing more information.
Click the Edit button beside the app you want to edit:
If the app only has one deployment, the Edit button includes a pencil ().
If the app has more than one deployment, the Edit button includes a down arrow () beside it, which, when clicked, provides a dropdown list of all of the deployments for the app, from which you can choose the deployment you want to edit.
Important
We do not recommend deploying the same app through the Publisher and PMPC Cloud to avoid settings conflicts and unwanted app behavior.
The Deployment Wizard starts, allowing you to make any required changes.
Make any required changes, then click Save to save them.
Important
Remember, it can take up to 24 hours for the changes you make to be applied to the discovery data, and even then, up to a week for an app to appear on the Managed tab unless you .
Applies to: Patch My PC Cloud
The Extra Files tool of the Patch My PC (PMPC) Cloud deployment wizard allows you to upload additional configuration files for a deployment.
To add extra folders and/or files:
Add the .
Click the Extra Files tool.
Either:
Drag and drop the relevant folders or files to the relevant area.
Click the relevant button to browse to and select the relevant folders or files.
Click Upload when your browser prompts you to upload the content.
The hash will be calculated for any folders/files you upload, which will appear at the bottom of the Extra Files section.
Repeat the above steps to add any additional folders/files as required.
If you do not want to configure any additional settings, click Next to move to the tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
Applies to: Patch My PC Cloud
By default, you have to wait a week for the discovery data in your Patch My PC (PMPC) Cloud portal to refresh. Rather than waiting up to a week you can refresh the data in the Discovery node every 24 hours to pick up any changes.
To manually refresh the data in the Discovery node:
Navigate to the Discovery node.
If the Refresh Data button is available, click it and go to Step 4.
If the Refresh Data button is unavailable, note the value of the Last Sync time. If it has been less than 24 hours since discovery last ran successfully, the Refresh Data button will be unavailable. Once 24 hours have passed, the Refresh Data button will be available.
The Refresh Data button changes to Collecting Data whilst discovery runs.
Currently, when the discovery process completes the portal does not auto-refresh. So periodically press F5 to refresh the portal.
Once discovery finishes running, the Last Sync time gets updated and the Refresh Data button becomes unavailable.
Tip
If you look in the Events node, you will see the Intune Discovered Applications Refreshed event which is created whenever someone clicks Refresh Data to refresh your discovery data.
Applies to: Patch My PC Cloud
You can grant Patch My PC (PMPC) support access to your portal to help troubleshoot issues.
To change the access level granted to PMPC to your portal:
Navigate to Settings | Company.
Scroll down to the Customer Support section.
Slide the Grant Access slider to the right to allow PMPC Support to access your portal.
Select the amount of time you wish to grant access to our support team from the Access period dropdown if you want to be longer than the default of 1 day.
Select the relevant level of access you want to grant from the Access Type dropdown:
Cloud Admin Read Only – PMPC Support can only see your portal but cannot make any changes.
Full Admin – PMPC Support can impersonate you and have full access to your portal.
Important
Full Admin does not include access management, i.e., PMPC cannot invite another user to your company on your behalf. Also, any actions PMPC perform are logged in the Events area, where you can review them as required.
Click Save to save your changes.
The Success - Company information updated notification is shown.
The timer now begins counting down. You can click Edit to amend it as required or even revoke access if your issue is resolved before the timer expires.
Applies to: Patch My PC Cloud
To navigate between pages of Events in Patch My PC (PMPC) Cloud, in the footer of the Events page, click the relevant control to go to the first page, previous page, next page, or last page.
Applies to: Patch My PC Cloud
Once you have finished using the Patch My PC (PMPC) Cloud portal, you can sign out of the company you are signed into by clicking your name in the top right-hand corner and selecting Sign Out from the dropdown.
The Ready to explore screen is shown, allowing you to sign in or sign up to PMPC Cloud.
Applies to: Patch My PC Cloud
More information about a Patch My PC (PMPC) Cloud can be shown for an event by clicking it.
The details page is displayed for the Event.
Either click the X or click outside of the details page to close it.
Applies to: Patch My PC Cloud
To sort Events:
On the Events page, click the relevant column heading to sort the entries by this column.
The column heading will be highlighted and an arrow will show you whether the results are displayed in ascending or descending order.
To sort by a different column, just click the column name.
Applies to: Patch My PC Cloud
Important
This documentation is for a pre-release feature still under development and, therefore, incomplete. As a result, both functionality and documentation are subject to change.
Once this feature is released, it will be announced and this banner removed.
Click on Migration and the
Applies to: Patch My PC Cloud
You can deploy the same app with different configurations using Patch My PC (PMPC) Cloud.
Important
For this to work, you must use a different Display Name for the deployment. If you don't, you will receive the error.
To deploy the same app with a different configuration:
Applies to: Patch My PC Cloud
As detailed in , an app will appear on the Managed tab of the Discovery node of Patch My PC (PMPC) Cloud if there is at least one matching deployment in either PMPC Cloud or our on-premises Publisher (Publisher) for that app.
This article includes examples of each of the supported scenarios.
Tip
Hovering over either the value in the Assigned To All column or
Applies to: Patch My PC Cloud
If you have for an app in Patch My PC (PMPC) Cloud and want to update it as soon as possible rather than waiting for the nightly sync job to run:
Applies to: Patch My PC Cloud
Using Patch My PC (PMPC) Cloud, you can delete software from Intune and recreate it to retrigger the deployment on the targeted resources.
To recreate a deployment:
From the Deployments page, click the ellipsis (⋮) beside the relevant deployment you want to recreate and click Recreate.
On the Are you sure you want to recreate <
Applies to: Patch My PC Cloud
The Summary tab of the Patch My PC (PMPC) Cloud deployment wizard provides a summary of the deployment so you can confirm that it is configured correctly before you create it.
Review the summary of the deployment shown on the Summary page. If you are happy click Deploy. If you need to change something, click
Applies to: Patch My PC Cloud
If you are using the Update Rings feature of Patch My PC (PMPC) Cloud, you may find that a version of an app deployed to a ring works fine and you now want to deploy this version to the next update ring without waiting for either the configured delay to be reached for that ring or the to be run.
To update an individual Update Ring to a later version:
Navigate to the Deployments node.
Click the relevant deployment to open its properties then click More Info.
Applies to: Patch My PC Cloud
Once you have signed into the Patch My PC (PMPC) Cloud portal, you can modify your user profile by clicking your name in the top right-hand corner and selecting Profile from the dropdown.
The User Profile screen is shown, allowing you to make any required changes and save them by clicking Save.
The Success – User Profile updated notification is shown.
Applies to: Patch My PC Cloud
The Switch Company feature allows you to switch to a different Patch My PC (PMPC) Cloud company without signing out of the current company.
To switch to a different company, click your name in the top right-hand corner and select Switch Company from the dropdown.
On the Select the Company You Want to Sign in To screen, click Select beside the company you want to sign in to.
Applies to: Patch My PC Cloud
The Update Rings feature of Patch My PC (PMPC) Cloud allows you to deploy apps and updates in a phased manner across your Intune estate.
For example, you may want to deploy software to a pilot group of users/devices to ensure it functions as expected. Then after a set period of time, you want to deploy the update to wider group of users/devices and pause a set amount of time to check for issues. Then finally, if there are no issues, deploy the update to the remaining users/devices in scope for the deployment.
Although this approach increases the amount of time it takes to deploy software, it can reduce the impact of deploying software with unforeseen issues that impacts your business in undesirable ways.
Applies to: Patch My PC Cloud
An event is written to the Events node whenever a user performs a task in the Patch My PC (PMPC) Cloud portal. Events are also created if the user's action triggers a component that performs an activity.
Events are created with one of the following severity levels:
Applies to: Patch My PC Cloud
All deployment-related tasks for Patch My PC (PMPC) Cloud are performed from the Deployments node of the portal.
To manage deployments:
Sign in to the Portal at .
Navigate to the Deployments node.
Applies to: Patch My PC Cloud
Important
Events are only held in the portal for 30 days, after which they are automatically groomed from the database. If you wish to keep events longer than 30 days, you need to export them.
To export today's events plus the past 29 days of events, click Export in the header of the Events page.
Applies to: Patch My PC Cloud
Preview Features in Patch My PC (PMPC) Cloud are pre-release features we are developing, which may not be functionally complete or contain bugs. When you enable Preview Features, you will gain access to all features we have marked as Public Preview, plus any new ones we release in the future will be automatically enabled.
Important
By enabling this option, you agree to accept that you may encounter some functionality issues and bugs.
Applies to: Patch My PC Cloud
An event is written to the Events node whenever a user performs a task in the Patch My PC (PMPC) Cloud portal. Events are also created if the action a user performs triggers a component to perform an activity.
To access the Events node:
Using your portal account, sign in at .
Navigate to Events.
Applies to: Patch My PC Cloud
In Patch My PC (PMPC) Cloud, the option for Update Rings doesn’t create an Update Ring until any configured delay has passed.
As a result, you cannot edit a deployment that uses Delayed Update Rings until all rings have been created.
Applies to: Patch My PC Cloud
To view the Update Rings configured for a Patch My PC (PMPC) Cloud deployment:
Follow the process to open the properties of the relevant deployment whose Update Rings you want to view.
Click More Info.
Any configured Update Rings are shown as tabs, which you can switch between to review your settings.
Applies to: Patch My PC Cloud
To change the number of events shown per page in Patch My PC (PMPC) Cloud:
Click the down arrow beside Items per page in the footer of the Events page and choose the required number.
Update Rings do not use Intune's built-in capability to create delayed assignments using Availability and Deadlines.
The use of Update Rings is optional and is controlled at the individual deployment level.
See our Update Ring Forecaster YouTube video for an explanation of Update Rings, plus how to use our free Get-UpdateRingForecast script on GitHub which creates an interactive HTML visualization of app update deployment rings for staged rollouts. It calculates and displays a schedule based on specified parameters and helps you understand your version rollout cadence across different environments.
Not contain the backslash (\) or quote (") characters
Not be the name of a script.
If a Category is created in the portal and then removed from the Intune admin center, it will be re-added by the portal.
Categories are also copied forward to a new version of an app.















Also, apps that have not been successfully deployed (such as those with a status of Failed, Retrying, Processing, etc.) cannot be used to create an app dependency, nor can apps with Uninstall or Update Only assignments.
If a dependency fails to be created. In this case, a warning is shown on the impacted child app(s) at the deployment level.
If a dependency fails to be carried forward. In this case, a warning is shown on the impacted child app(s) at the deployment level.
When multiple parent dependencies exist, any warnings will specify which particular dependency failed to be created to help you troubleshoot the issue.
If an entire deployment fails before the dependencies stage is reached, no warnings are shown, as we only show warnings for successful deployments.






Different ESP Profiles can be used in different Update Rings if required.
If you edit an ESP Profile that is used in a deployment that uses Update Rings, the changes will only be applied to the version of the deployment that is applied to the ring with the lowest delay.
If during a Sync Schedule the number of apps within an ESP Profile exceeds 100, we do not fail the deployment. The deployment will be completed with any new versions being assigned. However, we will display a warning indicator in the portal and the message “Failed to add application with version “<version_number>” to “<esp_profile_name>”.





Uploading a .mst file automatically adds the following to the Additional Argument field of the Install Parameters section:
TRANSFORMS=[<mstfile>].mst
where <mstfile> is the name of the uploaded MST file.



































Applies to: Patch My PC Cloud
This section contains various deployment-related articles for Patch My PC (PMPC) Cloud.
Total Apps
Breakdown of detected ConfigMgr applications by match type. See table below for more information on how apps are matched.
CVEs Detected
This chart shows the number of known vulnerabilities (CVEs) linked to the applications discovered in your ConfigMgr environment.
If we recognize the hash of a ConfigMgr app, we checks whether that hash is associated with any published CVEs. If matches are found, the CVEs are grouped by severity (Critical, High, Medium, Low).
In the example above, we found:
1 x Critical CVE
12 x High severity CVEs
6 x Medium severity CVEs
2 x Low severity CVEs
Totalling 21 CVEs across all ConfigMgr applications where we recognized the hash of the installer.
Migration Status
Shows the total number of ConfigMgr applications discovered and their current migration progress.
Not Supported Apps
Displays the number of ConfigMgr applications that cannot be migrated, with reasons based on validation errors.
From the Migration Dashboard, you can click the Apps tab, showing a list of the ConfigMgr applications that have been detected with the following information.
Match Type
The result of our attempt to match the ConfigMgr application to an app in our App Catalog, which will be one of the following:
Catalog App – We have successfully matched the ConfigMgr application to a version in our catalog. These apps can be deployed into Intune as a PMPC App and kept up to date by us for you. Custom App – We have been unable to successfully match the ConfigMgr application to a version in our catalog, but we can still help you migrate it to Intune.
Publisher App – We have identified that the application was created by Patch My PC Publisher. These apps are not supported for migration. Not Supported – We cannot currently migrate the ConfigMgr application, such as PSADT, or an app we’ve published from our Publisher to ConfigMgr, where it doesn’t make sense to migrate it, as you can just deploy it straight from our catalog to Intune using PMPC Cloud. TIP: You can hover over the “(i)” for an unsupported match type to see why it is unsupported for migration.
Matched App
The name of the app we have matched the ConfigMgr application to in our catalog.
Status
The migration status of the ConfigMgr application, which will be one of the following: Not Started – The migration process has not been started.
Pending – The migration process has been initiated.
In Progress – The migration is in progress.
Migrated – The application has been successfully migrated to PMPC Cloud.
Info
If there is further information/warnings about this application that we want you to review (such as we’ve detected a setting in the ConfigMgr application we cannot migrate), a warning triangle is displayed in the Info column. The triangle includes a number, which is the number of warnings. If you hover your mouse over the triangle, you will see a summary, and if you click the triangle, it will open the properties of the application and display the triangle beside the items we are warning you about. Clicking the triangle will show you more details that you should review before continuing to migrate the application.
Sign in to the portal at https://portal.patchmypc.com/.
Locate the required app on the App Catalog page.
Tip
Use the Search field to help you locate the app.
Click the app to open its properties, then click Deploy to start the Deployment Wizard.
On the General Information tab, in the Display Name field, enter a unique name for this deployment, then click Next.
On the Configurations tab, configure the settings to add any required scripts or additional installation parameters, then click Next.
On the Assignments tab, click Add Assignment, then select the assignment type you want to add for this deployment.
On the Add <assignment_type> Assignment page, select the relevant options, then click Save.
The Assignments page updates to show the newly created deployment.
Configure the settings for deployment, if required.
Tip
You can click Deploy on this page if you don’t want to add additional assignments or see the Overview page, which allows you to double-check the settings you’ve configured for this deployment.
Add any additional assignments for this deployment by clicking Add Assignment and repeating Steps 6 to 8, then click Next.
Review the deployment summary shown on the Summary page. If you are happy, click Deploy.
If you need to change something, click < Prev to backtrack through the Deployment Wizard to the relevant setting. Make the change, then step back through the wizard to this page. If everything is now correct, click Deploy.
The Deployments page is displayed along with the Success - Created <deployment_name> notification.
If the app has only been deployed using PMPC Cloud, the app:
Has the PMPC Cloud () icon beside its name.
Has either a red X () or green tick () in the Assigned To All column, depending on whether there is at least one deployment with a Required or Update Only assignment type to the Intune pre-defined All Users or All Devices assignments:
A red X indicates there isn’t.
A green tick indicates there is.
The Edit button is either:
A pencil () if the app only has one deployment.
A down arrow () if the app has multiple deployments. When you click the arrow, a dropdown list opens containing all of the deployments for the app from which you can choose the deployment you want to edit.
In the following screenshot:
Both Notepad++ and Zoom Workplace have only been deployed through PMPC Cloud.
Notepad++ has a single deployment with a Required assignment type to All Users.
Zoom Workplace has multiple deployments, but none have a Required assignment type to All Users or All Devices.
This can be confirmed by searching for the app in the App Catalog.
If the app has only been deployed using Publisher, as PMPC Cloud did not create the deployment, the app:
Has the On-Prem Publisher () icon beside its name.
Has a value of Unknown in the Assigned To All column.
The Edit button is disabled as you need to edit the deployment in Publisher.
In the following screenshot, the Google Chrome app has only been deployed using Publisher.
This can be confirmed by searching for the app in the App Catalog.
Important
We do not recommend deploying the same app through the Publisher and PMPC Cloud to avoid settings conflicts and unwanted app behavior.
If the app has been deployed using PMPC Cloud and Publisher, the app:
Has both the PMPC Cloud () and On-Prem Publisher () icons beside its name.
Has either a red X () or green tick () in the Assigned To All column, depending on whether there is at least one PMPC Cloud deployment with a Required or Update Only assignment type to the Intune pre-defined All Users or All Devices assignments:
A red X indicates there isn’t.
A green tick indicates there is.
The Edit button is only available to edit the PMPC Cloud deployment and will either be:
A pencil () if the app only has one deployment.
A down arrow () if the app has multiple deployments. When you click the arrow, a dropdown list opens containing all of the deployments for the app from which you can choose the deployment you want to edit.
In the following screenshot, Notepad++ has been deployed through Publisher and PMPC Cloud, with the PMPC Cloud deployment having a Required or Update Only assignment type to the Intune pre-defined All Users or All Devices assignments.
This can be confirmed by searching for the app in the App Catalog.
Click Sync Now to install any updates for the app immediately.
On the Are you sure you want to update <app_name> to the latest version popup, click OK.
The Deployment <app_name> updated notification is displayed and the deployment Status changes to In Progress.
Once the deployment has been completed successfully, the Status changes to Success.
Tip
If you look in the Events node, you will see the following event:
Deployment <app_name> Updated.
The Status of the deployment changes to In Progress and the Recreating the deployment <deployment_name> has started message is displayed.
Once the deployment has been recreated, the portal auto-refreshes and the Status changes to Success.
Tip
You can also click Recreate on the property page of a deployment to recreate it.

The App Catalog is redisplayed along with the Success - Created <deployment_name> notification.
Important
When a new version of software is released, it is automatically deployed using the settings of the existing deployment. The old version will be removed from the target user/device and replaced with the newer version.

If you can update a ring to a newer version the Update Now button is available.
Important
Some important points to note:
The Update Now option is only available if the deployment has been deployed successfully. It will not be shown if the deployment is in any other state or if Pause Updates has been enabled for this deployment.
An individual update ring can only be updated to a later version than the one it is currently running.
An individual update ring can only be updated to a later version that has already been applied to the ring with the lowest delay.
You are only updating a specific ring to a later version, not the whole deployment or any other rings.
Click Update Now and select the relevant version you want to upgrade this ring to.
On the Update “<deployment_name>” ring to version <version_number> dialog box, click Confirm.
The portal refreshes showing that the deployment is In Progress and the Success – Ring <ring_name> updated notification is shown.
Once the deployment has completed successfully, if you navigate back to the ring, you will see the version number has changed and the Update Now button is unavailable.
The App Catalog for the selected company appears, with your user name and the company of the selected company shown in the top right-hand corner of the portal.
You can switch back to the original company you switched from or a different company by repeating this process.

Clicking the ellipsis (⋮) beside a deployment opens the management menu, allowing you to:

Note
The number in parentheses beside the Export button shows how many events will be exported.
A CSV file called events_log_entries.csv is downloaded to your computer. This contains the number of entries shown in parentheses and can then serve as an archive or be imported to another application for onward manipulation.
We export the following:
Date
Title
Architecture
Installer Type
User
Category
Operation
Type
Version
Description
Here is an example:
Tip
You can use Filters to control which events you export, rather than exporting all events. See Filter Events for more information.

Also, enabling this option only enables Public Preview features. To gain access to any features we mark as Private Preview requires you to email a request to [email protected].
To enable Preview Features:
Navigate to the Company node.
Scroll down to the Preview Features section.
Click to check the Enable Preview features checkbox.
Click Save to save your changes.
The Success - Company information updated notification is shown.
Important
Only users assigned the Full Admin role will be able to see the Events node.
See User Roles for more information.
The Events page is then displayed, allowing you to:
Important
Events are only held in the portal for 30 days, after which they are automatically groomed from the database. If you wish to keep events longer than 30 days, follow the Export Events process.

Use the Edit a deployment process to navigate to the properties page of the deployment.
Each Update Ring is represented by a separate tab and the status of the ring shows you whether it has been created or not: • Success – The ring has been created. • Scheduled – The ring has not been created. In the following example, Ring 1 has been created as it has a status of Success.
However, as Ring 2 has a status of Scheduled, it has yet to be created as the configured delay has not passed.
Tip
If you look in the top right-hand corner of the deployment, the timestamp shows when the deployment was created. From this and looking at the number of days delay configured for a ring, you can work out when a specific ring will be created.
Note
If any rings have a status of Scheduled, it means that specific ring has yet to be created. See Check if an Update Ring has been created for more information.
Click the red X in the top right-hand corner to close the More Info page and return to the Deployments node.

App Name
The name of the app, which is always taken from our App Catalog as there may be a situation where multiple products from an app have been mapped to a single discovered app from Intune. In such cases, we show you the multiple records for each app. We also show you which product published the app: • PMPC Cloud ()
• On-Prem Publisher ()
Vendor
As shown in Intune. If no vendor name exists in Intune, we show the one from our App Catalog.
# Of Installs
The number of installations of this app in your environment.
Assigned To All
Shows:
• How the app was deployed
• Whether there is at least one deployment with a Required or Update Only assignment type that is assigned to All Users or All Devices
• Unknown if the app has only been deployed via Publisher.




Applies to: Patch My PC Cloud
To sign up for a free trial to PMPC Cloud:
Navigate to https://portal.patchmypc.com/
Click Sign Up.
On the Sign in screen, enter the Entra ID you want to use to onboard to PMPC Cloud or click to select the relevant account from the list of already signed-in accounts. Then click Next.
Enter the password and click Sign in.
If the Permission requested screen is not displayed, go to Step 7.
Review the Permission requested screen, clicking Accept if you are happy to continue.
Tip
You can click the down arrow beside each permission to get more information.
If do have previously created a Cloud Company and do not see the Select the Company You Want to Sign-In To screen, go to Step 9.
On the Select the Company You Want to Sign-In To screen, select the relevant option:
If you are setting up a new company, click Create Company and continue to Step 9.
If your email address has already been used to create a user in a PMPC Cloud company, you will see Select beside the relevant companies that you can sign in to.
Tip
You can click the Remember my Selection checkbox to on the Select the Company You Want to Sign-In To screen to save your choice to save you having to chose the company you want to sign into each time.
On the Company Info screen, click Select for the location where your company’s data will be stored.
In the Company Name field, type your company’s name.
Important
You cannot use the AT symbol (@), forward slash (/) or plus (+) symbols in your Company Name.
Select your company’s country from the Country dropdown.
Click Continue.
On the User Info screen, verify your First Name and Last Name are correct, amending as required.
Enter a valid email address in the Contact Email field.
Click the Terms and Conditions link to see these for using PMPC software and services.
The Terms and Conditions page is displayed. Once you’ve reviewed them, click the X in the top right-hand corner to close this window.
If you agree with our terms and conditions, check the Accept all Terms and conditions checkbox.
Click Continue.
The PMPC Portal loads, showing the App Catalog page.
Now you've finished onboarding to PMPC Cloud, you should consider:
Connecting Publisher by following the process.
Connecting your Intune tenant by following the process.
if you have already purchased a PMPC Cloud license.
Applies to: Patch My PC Publisher
In order to function and to help improve our product and services, Patch My PC (PMPC) Publisher collects and stores the following telemetry data.
.NET Version Number where the Publisher Software is installed
The version of .NET where the Publisher software is installed.
Understand if future releases of the Publisher and any code changes will be supported.
Alert Configuration
Boolean value showing if alerts (such as or ) have been enabled within the Publisher.
Determine how customers can be notified of changes, actions, or errors within the Publisher.
The list above is current through August 20, 2024. We try to keep this list updated, but it may not contain every instance of data collection. Please contact with any questions or you can review our .
Applies to: Patch My PC Cloud
To create Update Rings for a new Deployment in Patch My PC (PMPC) Cloud:
If you are unfamiliar with creating a deployment, follow the Deploy an App process until Step 7.
On the Assignments page, click Enable Update Rings.
From the Update ring start time dropdown, choose how you want your Update Rings to handle the start times for their assignments: • •
By default, two Update Rings are created with a two-day delay between them.
If you do not want to add additional Update Rings, go to step 7. To add an additional Update Ring, click Add Update Ring.
On the Add Update Ring dialog box, enter the name for the new ring in the Name field and click Save.
A new ring is added.
Important
Whenever you add a new Update Ring, it is created with a default delay of 0 days, i.e. the deployment will be installed immediately on any targeted users/devices.
If you already have another ring with a default delay of 0 days, you will see the Two rings cannot have the same delay value message besides the second ring with the duplicate delay.
You should adjust the delays on your Update Rings to avoid duplicates.
Repeat step 4 to add any additional Update Rings.
If you do not want to change the names of any of the rings, go to Step 10. If you want to change the name of any of the rings, click the pencil icon () beside the relevant ring.
Enter the ring's name in the Name field of the Edit Update Ring dialog box, then click Save.
The updated name appears.
Change the name of any other rings.
If you do not want to change the delay for any of the rings, go to Step 11. If you want to change the delay for a ring, click the plus (+) or minus (-) sign beside the relevant rings.
Click Add Assignment and add the relevant assignments for each ring, configuring the settings for each assignment as required.
Tip
You can drag assignments between Update Rings by clicking the double ellipsis () beside the relevant assignment and dragging and dropping it to the relevant Update Ring.
Click Deploy.
The “<deployment_name>” Deployment Summary dialog box appears, summarizing what you are deploying, to which groups, and when.
Either click : a. Cancel to return to the Assignments tab to make any changes (after which you need to click Deploy). b. Click Confirm to continue.
When you click Confirm, the Deployments node appears showing the deployment as In Progress and the Success – Created <deployment_name> notification.
Applies to: Patch My PC Cloud
The Assignments tab of the Patch My PC (PMPC) Cloud deployment wizard allows you to configure various assignments (explained below) for how you want the app to be deployed.
From the Assignments page you can also:
Apply a of pre-configured settings to this deployment.
for this deployment.
To add an Assignment to a deployment:
Click Add Assignment and then choose the assignment type you want to add for this deployment:
Add Required – A mandatory application that will be installed automatically for all users or devices it is assigned to.
Add Available – An optional application that will be available to install via the Company Portal for the primary user of the device.
d. Add Uninstall – A mandatory uninstall that will remove the application from any users or devices it is assigned to, using the apps uninstaller.
e. Install App - Allows the Intune admin to add Required, Available, or Uninstall assignments from within the Intune admin center.
f. Update Only App - Allows the Intune admin to add an Update Only assignment from within the Intune admin center.
On the Add <assignment_type> Assignment screen, choose the relevant Entra ID security groups to target for this assignment, then click Save.
The Assignments page updates to show the newly added assignments, including their configuration.
Make any of the following optional modifications to the assignment(s).
Tip
You can click Deploy on this page if you don’t want to add additional assignments or see the Summary page, which allows you to double-check the settings you’ve configured for this deployment.
Add any additional assignments for this deployment by clicking Add Assignment and repeating the steps in this section.
If you are happy you have entered all of the details for the deployment correctly, click Deploy to deploy the app. However, we recommend you click Next to move to the tab, where you can verify the settings for this deployment before you deploy this app.
Applies to: Patch My PC Cloud
Welcome to the Administration section for Patch My PC (PMPC) Cloud.
This section contains articles covering the various administrative tasks for Patch My PC (PMPC) Cloud.
Applies to: Patch My PC Cloud
If the Pause Updates feature of Patch My PC (PMPC) Cloud has been configured for an app that has since been updated, and you want to bring the app up-to-date to the latest version, you need to disable pause updates.
To resume updates for an app:
Click on the relevant deployment that has been paused.
Tip
Click the filter button () and select the Enabled option under the Updates section, followed by Apply Filters to see just those deployments that have updates paused.
Click the Pause Updates slider to disable it.
Click the X to close the deployment properties page.
The list of deployments is displayed without UPDATES PAUSED under the deployment you just unpaused.
Updates for this app are now resumed.
You now need to decide how you want to install any updates for this app:
Install the updates now – If you want to install the updates as soon as possible, follow the process.
Wait for the nightly sync to run – If you are happy to wait for the updates to be installed the next time the daily sync runs (at 2 am by default), you do not need to do anything.
Applies to: Patch My PC Cloud
As the Sync Schedule affects when your portal checks for updates to your Patch My PC (PMPC) Cloud deployments, how often it runs can also affect how your Update Rings behave.
For example, if you have deployed an app that updates more frequently than your configured Sync Schedule, the ring with the lowest delay (for example Ring 1) will have the latest suitable version applied.
Depending on how often you run your Sync Schedule and the delay between your rings, the scenario could arise where we have to skip versions to keep everything configured as per your ring strategy.
If this arises, we will not deploy a version of an app to any rings that has not been deployed to at least Ring 1. This ensures we only deploy apps to later rings that have been tested on at least one ring.
Also:
If you create your Update Rings with an Immediate start time, the Sync Schedule configuration only impacts the daily update of the rings and their assignments (promotion to the new version).
If you create your Update Rings with the Delayed start time, the Sync Schedule configuration impacts both the initial creation of the rings and the daily update of their assignments (promotion to the new version). For example, you create a deployment with two Update Rings with the default two-day delay between them. The first ring will be created when you deploy the software. The second ring won’t be created until two days have passed since the time the deployment was created and the next Sync Schedule run.
The following table summarizes how your configuration determines how you can configure the delay between Update Rings.
These limitations ensure that the update delays align with your chosen sync frequency and is why we advise configuring your to run on a daily basis when using Update Rings.
Applies to: Patch My PC Cloud
If you upload Extra Files as part of your Patch My PC (PMPC) Cloud Deployment, you can reference those files in any of the Scripts in the same deployment by building a path relative to the script's current location.
This ensures your script can reliably locate the files you uploaded, whether they are in the root or a subfolder.
Below are examples for referencing a file named file_to_be_copied.txt, either from the script root or a subfolder called MyFolder.
To reference additional files you’ve uploaded, use $PSScriptRoot\file_to_be_copied.txt or $PSScriptRoot\MyFolder\file_to_be_copied.txt if the file is in a subfolder.
For example:
To reference additional files you’ve uploaded, use %~dp0file_to_be_copied.txt or %~dp0MyFolder\file_to_be_copied.txt if the file is in a subfolder.
For example:
To reference additional files you’ve uploaded, use scriptDir & "\file_to_be_copied.txt" or scriptDir & "\MyFolder\file_to_be_copied.txt" if the file is in a subfolder.
For example:
Applies to: Patch My PC Cloud
The Pause Updates feature (which is disabled by default) of Patch My PC (PMPC) Cloud allows you to prevent an app that’s previously been successfully deployed from being updated whenever a new version is released.
Important
Pausing updates for an app only affects our portal. If a new version of an app becomes available and updates are paused, the portal won’t create a new version of that app while updates are paused.
However, any existing versions of apps already in Intune that are assigned will still be evaluated and, if applicable, installed by your devices.
To Pause Updates for an app:
Click on the relevant successful deployment you want to pause for updates.
Tip
Click the filter button () and select the Disabled option under the Updates section, followed by Apply Filters to see just those deployments that do not have updates paused.
Click the Pause Updates slider to enable it.
Click the X to close the deployment properties page.
The list of deployments is displayed and UPDATES PAUSED shows under the deployment name so you updates are paused for this specific deployment.
Applies to: Patch My PC Cloud
To view the properties of a Patch My PC (PMPC) Cloud deployment:
On the Deployments page, click the relevant deployment to open its properties screen.
To find out more details, click More Info to open the more info page.
More information about the deployment is shown.
Click X in the top-right corner to return to the Deployments page, or click Less Info to return to the deployment’s property page.
Applies to: Patch My PC Cloud
To delete a deployment in Patch My PC (PMPC) Cloud:
From the Deployments page, click the ellipsis (⋮) beside the relevant deployment you want to delete and click Delete.
On the Are you sure you want to delete <deployment_name> dialog box, click Yes.
The deployment is deleted and the Success - Deployment <deployment_name> deleted notification is displayed.
Warning
Deleting a deployment will also delete the:
latest and all old unassigned versions of this deployment if a has been configured.
Tip
You can also click Delete on the property page of a deployment to delete it.
Applies to: Patch My PC Cloud
A Post-Uninstall Script is a script that can be run after the uninstaller runs.
To add a Post-Uninstall script:
Click Add beside the Post-Uninstall option.
To import an existing script, click Import then browse to the location containing the script and select it.
Applies to: Patch My PC Cloud
Update Rings in Patch My PC (PMPC) Cloud provides two different implementations, both of which depend on the start time of the relevant deployment and how you have your Sync Schedule configured:
Applies to: Patch My PC Cloud
To sort Deployments in Patch My PC (PMPC) Cloud:
On the Deployments page, click the relevant column heading to sort the entries by this column.
The column heading will be highlighted and a small arrow will show you whether the results are displayed in ascending or descending order.
To sort by a different column, just click the column name.
An overview of the portal and how to work with it
How to manage settings for your PMPC Cloud Company
Details user account-related tasks
How to manage your environments
How to manage Connections
How to manage Branding in Intune Apps
How to manage Notifications
How to manage Naming Conventions
Managing when your company syncs
How to delete the Enterprise App
Daily
Delays between rings can be configured as required.
Weekly
Ring 2 has to have a minimum delay of 7 days
Ring x has to be configured with a delay of at least 7 days apart from any other ring.
Monthly
Ring 2 cannot have a delay of less than 31 days
Ring x has to be configured with a delay of at least 31 days apart from any other ring.
Was the application installed or uninstalled?
The version of the app that is installed
Were there any exceptions during the installation?
The OS that the app was installed on
The version of .NET, IIS, Java runtimes
Is the device x64 or x86?
The geographic location of the installation (e.g. US, UK, Germany)
Were the prerequisites met?
Certificate Validation Errors
Reported as a string, the contents of any errors occurring if the Publisher encounters an error when performing certificate validation, which it does whenever it communicates with Patch My PC servers.
Ensure the security and availability of the connection between the Publisher and Patch My PC servers.
Cloud Attached
Boolean value of the status of the cloud connection, indicating if a connection between the Publisher and Patch My PC Cloud has been configured.
Validate the connection between the Publisher and Patch My PC Cloud to ensure the availability of cloud-enabled features.
ConfigMgr Application Creation Enabled
Boolean data type, which tells us if the Enable creation of applications in Configuration Manager checkbox is enabled.
Understand whether customers are using all the features they may be entitled to within their subscription.
ConfigMgr Application Metadata
The list of ConfigMgr Applications and related metadata is reported back as a JSON payload. This includes information such as the installation command line, uninstallation command line, detection method, file names, file hashes, display info, and other application-related information. The collection of this information is dependent on the Publisher being cloud-connected and the Migration feature being enabled.
This data is used to allow for the ConfigMgr to Patch My PC Cloud Migration feature. The data collected is analyzed to determine which applications are eligible for migration.
Configuration Manager Site Version
Publisher reports back the Configuration Manager site version if the SMSProvider is defined as a string value.
Contact affected customers of compatibility or supportability issues with a specific ConfigMgr build we are aware of.
Device Counts
An integer of the number of devices in a ConfigMgr site or an Intune environment.
For ConfigMgr this is specifically the MemberCount from the ‘All Systems’ collection and the ‘All Desktop and Server Client’ collections.
For Intune, this is the count of devices returned by Graph when queried for Windows, MDM-managed devices that have synced within the last 365 days.
Determine the scale of usage for our products as part of product development and road mapping. Additionally, it is used as a data point for licensed device count evaluation,How Data is Transferred which is subject to our Terms of Service.
Error Description if Publishing an Update or Application Fails
A string value used by the Publisher to report the specific error returned if an update or application fails to be created.
This applies to the Updates, ConfigMgr Apps, Intune Apps, and Intune Updates tab.
NOTE: Error description reporting can be disabled with the following registry value:
REG ADD “HKLM\SOFTWARE\Patch My PC Publishing Service” /v DisableErrorReporting /t REG_DWORD /d 1 /f
See any issues a customer has when applications or updates fail to be created. Our goal is to be able to proactively reach out to customers who are experiencing known publishing issues.
Feature Usage
Boolean values of features (such as the Pause Feature) being enabled.
Determine the usage of new features within the Publisher and contact customers if a bug affects them.
Heartbeat
Every 4 hours Publisher sends a heartbeat, which is simply an indication that the Patch My PC service is running.
Determine if an instance of the Publisher is active. This data is used in troubleshooting failed upgrades and understanding Publisher usage.
Intune Application Creation Enabled
Boolean data type, which tells us if the Enable creation of Win32 applications in Microsoft Intune checkbox is enabled.
Understand whether customers are using all the features they may be entitled to within their subscription.
List of Selected Products
Reported as a list of product identifiers and product types.
Understand the usage of our catalog and ensuring we can reach out to customers regarding specific products
Number of Products Enabled and Published
An integer of the specific number of products enabled within each of the following Publisher tabs: Updates, ConfigMgr Apps, Intune Apps, and Intune Updates.
Publisher also reports back as an integer the number of updates, applications, and CVE’s published.
See the percentage of enabled versus available products and how many products are being published.
Number of Times the Catalog is Downloaded
An integer we increment each time our catalog is downloaded via an HTTPS request. We also report the next scheduled sync time as a DateTime.
Get critical insights into understanding if a specific customer has been able to utilize our products and services effectively.
Preview and Self-Updates Updates Enabled
Boolean data types that tell us if the Disable self-updates and Install preview builds options have been enabled.
Understand which customers have enabled these options, helping us notify customers of any specific actions that may need to be taken.
Version Number of the Publisher Software
A string value representing the version of the Publisher installed.
Understand how our self-updates are progressing and if any notifications may need to be sent based on notices for customers running a specific build.
WSUS Build Number
A string value representing the WSUS build number.
Identify WSUS APIs we need to test, support, or depreciate.
WSUS Database Type
Publisher reports back the type of WSUS Database, whether WID or SQL.
Better understand how our customers use WSUS, which can impact how our software works.
WSUS Updates Cleanup Information
Integer values reported back during a sync of the number of updates, size of the updates, and folder count cleaned up by the Publisher when it performs WSUS cleanup.
Better understand Publisher's hard disk usage.
WSUS Maintenance Configuration
Publisher reports back the current WSUS Maintenance configuration from the respective tab in ConfigMgr, which includes:
Decline expired updates in WSUS according to supersedence rules
Add non-clustered indexes to the WSUS database
Remove obsolete updates from the WSUS database.
Better understand how our customers use WSUS, which can impact how our software works.
Intune does not support using the Update Only assignment type with a deployment that is also configured to use ESP Profiles. If you try to use this configuration, the Deploy button will be greyed out and the Configurations tab will show a red "X". In this scenario, you either need to:
Remove the Update Only assignment type
Or remove all ESP Profiles.
Include
If checked, all of the items in this group will receive the assigned app.
Exclude
If checked, all of the items in this group will not receive the assigned app. Can be used in conjunction with Include to exclude a subset of devices when you have an Include of a superset of devices. For example, you want to target all of your computers except for your test devices. To achieve this, you'd configure your Entra ID groups as follows: o Check Include for your All Company Devices Entra ID group. o Check Exclude for your Test Devices Entra ID group.
Add Filter
The ability to add filters you have already created in Intune to target specific device types for the deployment. TIP: You can click the red X beside a filter to remove it.
Notifications
When to display notifications related to this deployment.
Content Download
How to download the content for the deployment: o Foreground - The default for initial installs. o Background - The default for updates.




In the current release, you can only sort by certain columns.




















































































# File in script root
Copy-Item -Path "$PSScriptRoot\file_to_be_copied.txt" -Destination "C:\TargetFolder"
# File in subfolder
Copy-Item -Path "$PSScriptRoot\MyFolder\file_to_be_copied.txt" -Destination "C:\TargetFolder"
:: File in script root
copy "%~dp0file_to_be_copied.txt" "C:\TargetFolder"
:: File in subfolder
copy "%~dp0MyFolder\file_to_be_copied.txt" "C:\TargetFolder" Set fso = CreateObject("Scripting.FileSystemObject")
scriptDir = fso.GetParentFolderName(WScript.ScriptFullName)
' File in script root
fso.CopyFile scriptDir & "\file_to_be_copied.txt", "C:\TargetFolder\"
' File in subfolder
fso.CopyFile scriptDir & "\MyFolder\file_to_be_copied.txt", "C:\TargetFolder\" Once you accept the permissions, you will not see this dialog box again on subsequent sign-ins.
If your email address is not associated with a user in a PMPC Cloud company, you can click Request Access beside the company you want to join.
The Request Access to join <company_name> popup appears. Enter an optional Reason for Request then click Submit. The Request Access text changes to Renotify and the Success - Access request sent notification is shown.
You now need to wait for a user with the Full Admin with Access Management role to review and approve your request.


















The Add Post-Uninstall Scripts page is populated with the imported script.
To manually add a script, enter a unique name for the script in the Script Name field.
Select the type of script from the Script Format dropdown.
In the script editor, type your script.
In the Arguments field, enter any arguments you want to provide to the script.
Tip
You can use variable names as arguments, provided they are enclosed by percentage signs (%). We provide common variables under this field, which you can add by clicking the plus (+) symbol or relevant variable name.
%ReturnCode% is currently only supported on post-scripts.
Important
Using script Arguments is currently unsupported when deploying an app to macOS.
Click Save to save your script.
The Configurations tab is re-displayed with the name of the configured script beside it.
Tip
You can click Edit to edit a script or its settings. You can also click the red “x” beside a script to delete it.
If you do not want to configure any additional settings, click Next to move to the Assignments tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.

The Delayed option works as follows:
The first Update Ring is created immediately and the software is deployed to the assigned test users/devices (usually known as a pilot group).
After waiting the configured number of days from when the deployment was created (to allow testing to be performed), the next Update Ring is created, and the software is deployed to the assigned users/devices (usually a bigger group/all assigned users/devices).
Step 2 is repeated until all Update Rings have been created and the software has been deployed to all users/devices requiring it.
The advantage of the delayed option is:
As the next ring (and therefore the next set of assignments) has not been created, if the software causes an issue that is detected in the first ring, the issue cannot propagate to other rings as they haven’t been created.
The disadvantages of the delayed option are:
Your Sync Schedule configuration can impact both when the initial rings are created and when the Sync Schedule runs, which will update your rings and their assignments, including promoting a new version to your relevant rings.
You cannot edit a deployment that uses delayed Update Rings until all of the rings have been created. If you try, you will see the Error - Editing is not allowed until all rings are created after the configured delay.
The Immediate options works as follows:
All Update Rings are created immediately with their relevant delays and assignments.
Assignments from all of the Update Rings will be applied to the version of the app you created the deployment with.
Update Rings will not begin to work until the next version (current plus one or n+1) of the software is released. At this point, the assignments from the previous version are moved to the latest version and Update Rings start to function as configured.
The advantages of the immediate option are:
All rings are created and configured once.
The deployment can be edited and adjusted as required.
The disadvantages of the immediate option are:
If the software in one ring causes an issue, if the admin forgets to pause the deployment or remove any additional rings, the issue could be spread to the next ring, even if a delay between rings is configured.
All assignments from all Update Rings are applied to the same version of the application the deployment was created with. However, this is only true for the initial creation of the Update Rings. All of the other functionality of Update Rings will work as normal for any new versions of the app.
Important
You need to consider the following when working with Update Rings:
You cannot mix standard deployments (that don’t use Update Rings) and Update Rings in a single deployment.
for more information on how your configuration of the Sync Schedule will affect how Update Rings behave.
for more information about how update rings handle new versions, including worked examples.
Applies to: Patch My PC Cloud
Important
If a Patch My PC (PMPC) Cloud deployment is created with Delayed Update Rings, you cannot edit it until all of the rings have been created. If you attempt to edit a deployment with incomplete Update Rings you will see the Error - Editing is not allowed until all rings are created after the configured delay message.
Also, if you make any changes to Return Codes for a deployment where Update Rings are enabled, these changes are only applied to the latest ring (newest version).
To edit the Update Rings configuration for a deployment:
Navigate to the Deployments node.
Click the relevant deployment whose Update Ring configuration you want to edit.
Tip
Click the filter button () and select the Enabled option under the Update Rings section, followed by Apply Filters to see just those deployments that have update Rings configured.
Click Edit.
Click the Assignments tab.
Make any required changes, for example:
Applies to: Patch My PC Cloud
A Post-Install Script is a script that can be run after the installer runs.
To add a Post-Install script:
Click Add beside the Post-Install option.
To import an existing script, click Import, browse to the location containing the script, and select it.
The Add Post-Install Script page is populated with the imported script.
To manually add a script, enter a unique name for the script in the Script Name field.
Select the type of script from the Script Format dropdown.
In the script editor, type your script.
In the Arguments field, enter any arguments you want to provide to the script.
Tip
You can use variable names as arguments, provided they are enclosed by percentage signs (%). We provide common variables under this field, which you can add by clicking the plus (+) symbol or relevant variable name.
%ReturnCode% is currently only supported on post-scripts.
Important
Using script Arguments is currently unsupported when deploying an app to macOS.
Click Save to save your script.
The Configurations tab is re-displayed with the name of the configured script beside it.
Tip
You can click Edit to edit a script or its settings. You can also click the red “x” beside a script to delete it.
If you do not want to configure any additional settings, click Next to move to the tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
Applies to: Patch My PC Cloud
In Patch My PC (PMPC) Cloud, a successful deployment can be edited (changed) should you wish to change any of its settings (e.g., assignments, command line parameters, etc.).
There are two ways to edit a deployment:
To edit an existing deployment from the Deployments node:
Navigate to the Deployments node.
Click the relevant deployment you want to edit.
On the deployment's property page click Edit.
Tip
You can also edit a deployment from the Deployments node by clicking the ellipsis (⋮) beside the relevant deployment you want to edit, then click Edit.
To edit a deployment from the App Catalog:
Navigate to the App Catalog and click on the app whose deployment you wish to edit.
Tip
Any apps already deployed by Intune Apps have the green cloud icon with a tick () next to the version number.
Click Edit Deployment on the deployment's property page.
The behavior of the Edit Deployment button depends on whether there is at least one existing, successful deployment:
If there is only deployment for an app, clicking the Edit Deployment button starts the Deployment Wizard.
If there is more than one deployment for the same app, clicking the Edit Deployment button provides a dropdown list of all deployments for this app, from which you can select the relevant deployment to edit. Clicking a deployment starts the Deployment Wizard.
The Deployment Wizard starts.
Follow the process.
Applies to: Patch My PC Cloud
If you have already successfully deployed an app using Patch My PC (PMPC) Cloud, you can convert that deployment to use Update Rings.
To convert an existing deployment to use Update Rings:
Edit the deployment and navigate to the Assignments tab.
Any existing assignments for the deployment are shown.
Click Enable Update Rings.
On the Move Assignments or Delete dialog box, click Move to create the Update Rings and move any existing assignments to the first Update Ring.
Any existing assignments are moved into the first Update Ring.
Continue from Step 3 of the process to configure your Update Rings. For example, adding additional assignments, moving assignments between rings, etc.
Once you have completed reconfiguring the deployment, click Save.
Applies to: Patch My PC Cloud
A Pre-Install Script is a script that can be run before the installer runs.
To add a Pre-Install script:
Click Add beside the Pre-Install option.
To import an existing script, click Import then browse to the location containing the script and select it.
Applies to: Patch My PC Cloud
Important
This documentation is for a pre-release feature still under development and, therefore, incomplete. As a result, both functionality and documentation are subject to change.
Once this feature is released, it will be announced and this banner removed.
For certain applications in the Patch My PC (PMPC) App Catalog, we include scripts to enhance the installation and configuration of the app, based on our experience. By default, if an app includes one of our recommended scripts, these are automatically executed at the time the app is installed.
Applies to: Patch My PC Cloud
For a Patch My PC (PMPC) Cloud deployment with Update Rings enabled, you can either:
Applies to: Patch My PC Cloud
This article lists the various that are generated with the Security severity by Patch My PC (PMPC) Cloud.



























Rejected
A user failed to complete the "Recover Your Company" process.
Customer Support Settings Updated for Company <company_name>
Company
Updated
The settings for a company are updated.
Group role with id <entra_id_security_group_id> was created with role <user_role_assigned>
Group Role
Created
When an Entra ID Security Group is added to the portal
Group Role Removed
Group Role
Removed
When an Entra ID Security Group is removed from the portal
Group role with name <group_name> and id <entra_id_security_group_id> was changed to role <new_user_role>
Group Role
Updated
When the role of an Entra ID Security Group is changed within the portal
Intune Connection Added
Intune
Connected
An Intune tenant is connected to the portal.
Intune Connection Removed
Intune
Disconnected
An Intune tenant is disconnected from the portal.
Invitation Sent to <user_name>
Invitation
Created
A user invitation is sent.
Preview Features Setting Updated by <user_name>
Company
Updated
A user changes the Preview Features setting for a company
User Account Created for <user_name>
User
Created
A user is created.
<user_name> Removed by <admin_name>
User
Removed
A user is deleted.
<user_name> Role Changed by <admin_name>`
User
Role changed
A user's role is changed.
Company Ownership Approved for <user_name>
Access
Approved
A user successfully completed the "Recover Your Company" process.
Company Ownership Rejected for <user_name>
Access
Move Assignments between rings using drag and drop
Rename rings by clicking the pencil icon beside the relevant ring
Modify the delay for a ring by clicking the minus (-) or plus (+)
Add a ring by clicking Add Update Rings
Delete a ring by clicking the red x after the delay.
Click Save to save your changes.
If you make any changes that affect how the Update Rings will work, you will see the “<app_name>” Deployment Summary asking you to either confirm or cancel your changes. For example, reducing the delay for Corel All Users ring from 3 days to 2 results in the following.
Either click Cancel to return to the Assignments tab and make any required changes or click Confirm to save your changes. The Deployments node is redisplayed along with the Success – Edited <deployment_name> notification.




The Deployment Wizard starts.
Follow the Deploy an App process.





The Add Pre-Install Script page is populated with the imported script.
To manually add a script, enter a unique name for the script in the Script Name field.
Select the type of script from the Script Format dropdown.
In the script editor, type your script.
In the Arguments field, enter any arguments you want to provide to the script.
Tip
You can use variable names as arguments, provided they are enclosed by percentage signs (%). We provide common variables under this field, which you can add by clicking the plus (+) symbol or relevant variable name.
Important
Using script Arguments is currently unsupported when deploying an app to macOS.
Check the Don’t attempt software update if the pre script returns an exit code other than 0 or 3010 checkbox if you don’t want the app to be installed if the pre-script returns an exit code other than 0 or 3010.
If you do not check this checkbox, we will attempt to install the app regardless of the exit code returned by the pre-install script.
Check the Run the pre-update script before performing any auto-close or skip process checks checkbox if you want to run the pre-install script before the conflicting process notification is displayed (if relevant). If you do not check this checkbox, we will run the pre-install script after the conflicting process notification.
Click Save to save your script.
The Configurations tab is re-displayed with the name of the configured script beside it.
Tip
You can click Edit to edit a script or its settings. You can also click the red “x” beside a script to delete it.
If you do not want to configure any additional settings, click Next to move to the Assignments tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.

However, this default behavior can cause issues for some customers who are not aware of the scripts and their contents.
To give you better visibility and to allow you to customize the deployment process, for those apps that include our recommended scripts, you will now see the Customer Scripts | PMPC Scripts toggle on the Scripts tool page of the Configurations tab of the PMPC Cloud Deployment Wizard.
Contrast this to an app that does not include any recommended scripts.
To view the PMPC scripts, click the PMPC Scripts toggle.
Any recommended scripts included with the app are shown.
Once you have clicked PMPC Scripts, you can:
Hover over the script’s name to see its location.
Click the script, which will open it in a new browser tab so you can see its contents.
Click Edit to open the script in the relevant script editor window.
If you do not want to use our recommended scripts in your deployments, you can disable them (although we’d recommend you do not do this unless you have a genuine reason for doing so).
To disable a PMPC script:
Either deploy or edit an existing deployment for the relevant app.
Navigate to the Configurations tab.
Click the Scripts tool if it is not already selected.
Click PMPC Scripts
Click Edit beside the relevant script.
If the app includes a recommended Post-Install script, go to Step 9.
If the app includes a recommended Pre-Install script, you have the option of checking either or both of the following checkboxes:
Don’t attempt software update if the pre script returns an exit code other than 0 or 3010
Disable the Patch My PC Recommended Pre-Install scripts for this product
Go to Step 10.
If the app includes a recommended Post-Install script, check the Disable the Patch My PC Recommended Post-Install scripts for this product checkbox.
Click Save
The Configurations tab is displayed.
If either a Pre or Post-Install script has been disabled, a red circle is shown beside the script to indicate this and that it will not be included as part of the deployment.
If you have previously disabled a PMPC Script, you can re-enable it by editing the deployment and following the Disable a PMPC Script section, but uncheck the Disable the Patch My PC Recommended <script_type> for this product checkbox.
When you click Save to save the deployment, a new deployment will be created that includes the script.
If you create a deployment for an app and disable the PMPC Scripts, when your Sync Schedule runs and creates a new deployment for the new version, we check the existing deployment, and if you have disabled any scripts, we will also disable them for the new deployment of the new version.
All deletion tasks for Update Rings are performed from the Assignments tab of the respective deployment.
To delete all Update Rings for a deployment:
Edit the relevant deployment and navigate to the Assignments tab.
If you want to delete a single Update Ring, use the Delete a Single Update Ring process. To delete all Update Rings for this deployment, click Remove all Rings.
On the Move Assignments or Delete dialog box, click Move to remove the Update Rings but keep all the existing assignments.
The Update Rings are removed and any existing assignments are kept.
Click Save to save your changes.
Important
As removing all Update Rings disables Update Ring functionality for this deployment (which could result in unintended results), the "<deployment_name>" Deployment Summary is shown detailing the impact of your proposed change. For example, this version of the app will be deployed immediately to all of the following assignments without any of the delays enforced by using Update Rings.
Click Cancel to return to the Assignments tab to make any required changes, or click Confirm to save your changes. The Deployments node is displayed along with the Success – Edited <deployment_name> notification.
Tip
If you edit the deployment and click More Info, you will see the tabs representing the Update Rings are no longer present.
To delete a Single Update Ring:
Navigate to the Assignments page of the deployment.
Click the red X beside the Update Ring you want to delete.
The ring and any assignments it contains are deleted.
Click Save to save your changes.
As you’ve removed an Update Ring and it’s assignments, the "<deployment_name>" Deployment Summary is shown detailing the impact of your proposed change. For example, by deleting the 7-Zip Pilot +7 Days ring, this app will not be deployed to the 03 - Patching - Production - All - 7 Days Entra ID group.
Click Cancel to return to the Assignments tab to make any required changes, or click Confirm to save your changes. The Deployments node is displayed along with the Success – Edited <deployment_name> notification.
Tip
If you edit the deployment and click More Info, you will see the tab representing the deleted Update Ring is no longer present.
Applies to: Patch My PC Cloud
A Pre-Uninstall Script is a script that can be run before the uninstaller runs.
To add a Pre-Uninstall script:
Click Add beside the Pre-Uninstall option.
To import an existing script, click Import then browse to the location containing the script and select it.
The Add Pre-Uninstall Script page is populated with the imported script.
To manually add a script, enter a unique name for the script in the Script Name field.
Select the type of script from the Script Format dropdown.
In the script editor, type your script.
In the Arguments field, enter any arguments you want to provide to the script.
Tip
You can use variable names as arguments, provided they are enclosed by percentage signs (%). We provide common variables under this field, which you can add by clicking the plus (+) symbol or relevant variable name.
Important
Using script Arguments is currently unsupported when deploying an app to macOS.
Check the Don’t attempt software uninstall if the pre script returns an exit code other than 0 or 3010 checkbox if you don’t want the app to be uninstalled if the pre-script returns an exit code other than 0 or 3010. If you do not check this checkbox, we will attempt to uninstall the app regardless of the exit code returned by the pre-install script.
Check the Run the pre-uninstall script before performing any auto-close or skip process checks checkbox if you want to run the pre-uninstall script before the conflicting process notification is displayed (if relevant). If you do not check this checkbox, we will run the pre-uninstall script after the conflicting process notification.
Tip
You can click Edit to edit a script or its settings. You can also click the red “x” beside a script to delete it.
If you do not want to configure any additional settings, click Next to move to the tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.







































Click Save to save your script.
The Configurations tab is re-displayed with the name of the configured script beside it.










Applies to: Patch My PC Cloud
The General Information tab of the Patch My PC (PMPC) Cloud deployment wizard allows you to configure various general settings (explained below) for how you want the app to be deployed.
Once you have finished configuring the relevant options, go to Next Steps.
Allows you to apply a of pre-configured settings to this deployment.
Shows the type of connection. Currently, we only support connections to Intune.
The unique name for this deployment. This is also the name of the app as it will appear on the target devices.
Multiple language entries will be present if the vendor offers separate installers for that language. For example, an EXE installer for en-US, de-DE, etc. The majority of installers are multi-language (one installer, multiple languages), and the software can be configured in different languages by:
Specifying additional installation parameters
Configuring .config or .xml files
Setting registry values.
In such cases, it is the vendor that determines the level of support and the behavior.
The architecture of the installer to be deployed:
64-bit installers can only be installed on 64-bit devices
32-bit installers can typically be installed on either 32-bit or 64-bit devices.
Unspecified installers typically contain install logic for both architectures.
The context in which to install the application:
System – Available to all users.
User – Available only to the specific user.
The available installer types you can choose from to install this app.
We currently support the following Windows installer types:
.exe
.msi
.msp
We currently support the following macOS installer types:
.dmg
.pkg
Once you have finished configuring the relevant options, click Next to move to the tab.



Applies to: Patch My PC Cloud
This article lists the various that are generated with the General severity by Patch My PC (PMPC) Cloud for the following categories:
Applies to: Patch My PC Cloud
The Configurations tab of the Patch My PC (PMPC) Cloud deployment wizard allows you to configure various configuration settings (explained below) for how you want the app to be deployed.
The most common settings are displayed by default. You can configure additional, optional settings by either scrolling down the page until you find the relevant section or by clicking the relevant section heading.
Intune Discovered Applications Refreshed
Updated
Created whenever someone clicks Refresh Data to refresh your discovery data.
Managed Company Relationship for <child_company_name> Removed by <user_name>
Removed
A child company is unlinked from a parent MSP company
NOTE This event is shown on both the parent and child companies
Default Branding - <branding_app_name> Created
Created
The default Branding App is created.
Default Branding - <branding_app_name> Deleted
Removed
The default Branding App is deleted.
Application <app_name> Created
Created
An app is created
Application <app_name> Changed by <user_name>
Updated
An app is updated
Application <app_name> Removed by <user_name>
Removed
An app is removed
Intune Application Discovered
Created
Client Deployment Created for <preview_or_production>
Created
PMPC Client has been deployed
Client Deployment Updated for <preview_or_production>
Updated
List of Entra ID Groups PMPC Client deployed to has been updated or the Uninstall Client feature is used.
Client Deployment Deleted for <preview_or_production>
Removed
PMPC Client deployment is deleted
Company <company_name> Created by <user_name>
Created
A company is created
Company <company_name> Updated by <user_name>
Updated
A company is updated
Managed Company <child_company_name> Created by <user_name>
Created
A child company of an MSP is created
Environment <environment_name> Updated
Updated
An environment is updated
Custom Branding <branding_app_name> Created
Created
A Branding App is created.
Custom Branding <branding_app_name> Recreated
Recreated
A Branding App is recreated.
Custom Branding <branding_app_name> Deleted
Removed
A Branding App is deleted.
Custom Branding <branding_app_name> Updated
Updated
Deployment <deployment_name> Created
Created
An Intune deployment is created.
Deployment <deployment_name> Deleted
Removed
An Intune deployment is removed.
Deployment <deployment_name> Recreated
Recreated
An Intune deployment is recreated.
Deployment <deployment_name> was updated by scheduled synchronization
Synchornized
macOS (Trial) Applied
Applied
A macOS trial begins
macOS (Full) Applied
Applied
A full (not trial) macOS license is applied
Invitation Accepted by <users_email_address>
Approved
A user accepts an invitation to an MSP company
Invitation Sent to <users_email_address>
Created
An invitation to an MSP company is sent to a user
Invitation Deleted by <users_email_address>
Removed
A user deletes an invitation to an MSP company
Invitation Declined by <users_email_address>
Rejected
Publisher Connection Added
Connected
Publisher is connected to the PMPC Cloud portal.
Publisher Connection Removed
Disconnected
Publisher is disconnected from the PMPC Cloud portal.
Created the first time Discovery is run in your PMPC Company
A Branding App is updated.
A deployment is updated by the Sync Schedule.
A user declines an invitation to an MSP company
Grey tick - Some values have been pre-configured by PMPC
Green tick - You have configured some values
Radio button - Neither you or PMPC have configured any settings.
To add additional, optional tools to a deployment, click Add in the Additional Tools section and select the relevant tool from the popup which will add it to the list of Additional Tools.
Tip
You can check the checkboxes beside multiple tools to add them to the list of Additional Tools. You can also click the X beside an additional tools you want to remove from the list.
Any settings you configure for a deployment will be used for the current deployment and automatically applied to any new versions of the deployment as it's updated.
Once you have finished configuring the relevant options, go to Next Steps.
This button allows you to apply a Template of pre-configured settings to this deployment.
The Install Parameters section allows you to configure various installation parameters and arguments.
Install Parameter Summary
Shows any default installation parameters.
NOTE These cannot be modified or removed.
Additional Argument
Allows you to provide additional arguments to be appended to the installation command line. These can override the Patch My PC arguments in some cases (typically for MSI arguments). NOTE This field is limited to a maximum of 2,048 characters. See for a list of the variables we support in this field.
The installation of some apps cannot be completed if the app:
is currently running
uses a shared process that needs to be closed, but in doing so, could impact that process and other apps using it.
The Conflicting Process section lets you manage those conflicting processes (also known as "Conflicting Process"), and control what happens in such scenarios using one of the following options.
To manage the conflicting process for a Deployment:
Click the Conflicting Process tool.
Configure the required settings as detailed below.
This is the default option for software that can install, update, or uninstall, even when conflicting processes are running.
Automatically closes the app/process causing the conflict to allow this app to be installed.
Important
This can result in data loss so use with care.
The installation is skipped until the conflicting process is no longer in use. This will generate a 1602 error in the PatchMyPC-ScriptRunner.log and AppWorkload.log on the client side. In Intune, the status will shows as follows when you look under the Device/User Install Status blade of the package:
The user cancelled the app installation. (0x80070642)
This is the default option for software that cannot successfully install, update, or uninstall when conflicting processes are running. The user sees a notification requesting they close the app, which is preventing this install. These apps will leverage your Branding.
Tip See Manage Conflicting Processes when Updating Third-Party Applications - Patch My PC for a list of products we know will generally fail to update if they are in use.
Clicking the Settings button allows you to configure the following Advanced Settings for Conflicting Processes.
How long in minutes (5 by default and up to a maximum of 1,425 minutes with a 15 minute buffer), before the notification timeouts.
How the notification behaves if the app is currently running and Focus Assist is enabled:
Discard the Notification (default)
Always show the notification
Show the notification if the deferred policy is reached
The user cannot defer the installation. The app will close and update when the timeout expires.
When an installation is postponed, Intune interprets the installation as a failure and automatically retries it 24 hours later.
Using this option, the user can defer the installation:
Indefinitely – If selected, Intune will retry the installation forever, giving the user the option to postpone it every 24 hours.
Up to X times - The user can postpone the installation the configured number of times with a 24-hour gap between retries. Intune will retry the installation every 24 hours until the user has no more deferrals. At this point the conflicting process will be closed and the update will be installed.
First notification displayed – If a conflicting process is detected, the notification is shown immediately. The user can defer the installation or update up to the maximum number of days set in this option. During that period, Intune retries the installation about every 24 hours. If a conflicting process is still detected at a retry, the notification is shown again. Once the maximum deferral period is reached, the user can no longer postpone and the installation will proceed.
Prevents the app from opening whilst it is being updated.
Clicking the Conflicting Process button lets you see any conflicting processes we have identified that will prevent an app from updating.
You can also add additional entries or remove existing entries to suit your environment.
The Return Codes section allows you to configure Return Codes for a deployment (a Return Code is a numerical code an app typically logs and reports once it has completed running its installer).
You can manage Return Codes from within the properties of a:
Deployment
Custom App
To manage Return Codes for a Deployment:
Click the Return Codes tool.
The default Return Codes defined for the app are shown, plus any defined for the app if this is a Custom App.
If you do not want to add a new Return Code, proceed to Step 5.
To add a new Return Code for this deployment, enter the numerical value in the Return Code field, select its meaning from the Code type dropdown, then click Add.
The new Return Code is added to the list.
If you do not want to edit a Return Code, go to Step 9.
To edit a Return Code, click the pencil icon beside it.
Make any required changes.
Click the green tick to save your changes.
The Code type field is updated.
To delete a Return Code, click the red trash can beside the relevant code.
Important
If the Return Codes you define in a deployment differ/conflict with those defined for a Custom App, the Return Codes defined on the deployment take precedence.
The code is deleted from the list.
The App Info section enables you to define default values for items that will be included in the app’s metadata when it is packaged to Intune.
Any values set for the following items will appear in the app’s properties when viewed in the Intune admin center:
Vendor* - The vendor of the app.
Owner – The name of the owner of this app.
Description* - A description of the app.
Notes – Notes about the app that we send to Intune when we create a deployment.
Information URL - Link to a website or documentation that has more information about the app.
Privacy URL - A link for people who want to learn more about the app's privacy settings and terms
Developer – The name/contact details of the developer as this is a plain text field.
Set App as Featured - If checked, allows this app to appear as a featured app in the Company Portal. Once the app has been deployed, the Show this as a featured app in the Company Portal setting on the app’s properties should be set to Yes in the Intune admin center.
* denotes a required field
Tip
If you make a mistake and want to reset the information in this section, click Reset to Default followed by OK on the Are you sure you want to reset to the default values? dialog box.
Also, if the App Info section has been configured, you can view it as part of the app’s properties in the Microsoft Intune admin center.
To manage the App Info for a Deployment:
Click the App Info tool.
Configure the settings as required.
If checked, will remove the desktop shortcut created as part of the app installation.
To configure this setting:
Click the Desktop Shortcut tool.
Configure the settings as required.
If checked, allows Intune Apps to uninstall the app if the Company Portal installed it.
To configure this setting:
Click the Available Uninstall tool.
Configure the settings as required.
If you do not want to configure any additional settings, click Next to move to the Assignments tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.

Applies to: Patch My PC Cloud
Let’s assume you want to deploy an app in a controlled manner using Patch My PC (PMPC) Cloud.
First, you want to deploy the software to a pilot group containing a few users who want to test the software.
Then, a couple of days later, once you are happy the app functions correctly, you want to deploy it to a different group containing more users.
You could:
Create a single deployment targeted to the pilot users group.
Two days later, either:


















Modify the deployment targeted to the pilot users group to add the other group containing more users.
Create a new deployment targeted to the other group containing more users.
This approach is admin intensive and relies on the admin remembering to create the deployment two days later to ensure the other group containing more users gets the app.
Alternatively, you can create a single deployment and enable Update Rings with:
One ring assigned to the pilot users group.
A separate ring assigned to the other group containing more users, but with a two-day delay to allow the pilot users to perform testing.
How Update Rings behave depends on which Update ring Start Time you chose at the time of creating the rings:
For this example, we will assume you want to deploy version 2019.1 of dBase:
Initially to the dBase Pilot Users group.
Two days later, you want to deploy the software to the dBase All Users group.
This is how you would configure this deployment in the PMPC Cloud portal to use Delayed update Rings.
In this scenario, when you deploy the app the Deployments node is displayed along with the Success – Created <app_name> notification.
Once the deployment has been completed successfully, if you look in the Microsoft Intune admin center under All apps and search for the app, you will see that version 2019.1 has been successfully deployed.
If you click the app and navigate to Manage | Properties, then scroll down to the Assignments section, as you are using delayed update rings you will only see the assignments for the first Update Ring has been created and applied to this version.
If you click on the deployment in the portal, then click More Info, then click Ring 2, you will see that this ring is scheduled to be created two days after the deployment was created.
Two days after the deployment was created and after the next Sync Schedule runs, the second update ring will be created and the assignment added for the dBase All Users group to install the software to all of the members of this group.
You can now edit the deployment if required, as all of the rings have been created.
If you also look at the deployment's properties, you will see that the second ring has been created successfully and assigned to the dBase All Users group.
As the following table shows, the software is installed immediately for any users in the dBase Pilot Users group.
Any users in the dBase All Users group will not have the software installed until two days later.
0
dBase Pilot Users dBase All Users
Yes No
1
dBase Pilot Users dBase All Users
Yes No
2
dBase Pilot Users dBase All Users
Yes Yes
Now, let’s assume a new version (2019.2) gets released.
In this scenario, you can:
Wait until the overnight sync runs to pick up the new version.
Run the Sync Now process to update just this deployment immediately.
Once the deployment has been updated, you can now edit it as all of the rings have now been created. If you look at the deployment’s properties, you will see that for the Ring 1, version 2019.2 has now been assigned to the dBase Pilot Users group.
But if you click on Ring 2, you will see that version 2019.1 is still assigned to the dBase All Users group.
If you check in the Intune admin center, you will now see both the existing app (version 2019.1) and the new version we have just deployed (version 2019.2).
If you check the assignments for the original deployment (version 2019.1), you will see it is now only assigned to the dBase All Users group.
Whereas, if you check the assignments for the new deployment (version 2019.2), you will see it is only assigned for now to the dBase Pilot Users group.
Two days after the new version of the app is released and after the next Sync Schedule runs, the assignment for the dBase All Users group will be automatically moved from the version 2019.1 deployment to the 2019.2 deployment, automatically upgrading the members of the dBase All Users group to version 2019.2.
The old version of the app (2019.1), will remain, but will no longer show as Yes under the Assigned column in the Intune admin center. At the next sync, the old version of the app will be deleted.
This update process is summarized in the following table:
0
dBase Pilot Users dBase All Users
2019.1 2019.1
Yes No
2019.2 2019.1
1
dBase Pilot Users dBase All Users
2019.2 2019.1
No** No
2019.2 2019.1
* Number of days after the new version of the app is released
** Any new users/devices added to the group will receive the version applicable to the group.
For this example, we will assume you want to deploy version 2024.1 of PaintShop Pro:
Initially to the Corel Pilot Users group.
Two days later, you want to deploy the software to the Corel All Users group.
This is how you would configure this deployment in the PMPC Cloud portal to use Immediate Update Rings.
When you deploy the software, you see the Deployment Summary of how the deployment will be handled.
Once the deployment has completed successfully, if you look in the Microsoft Intune admin center under All apps and search for the app, you will see that version 2024.1 has been successfully deployed.
If you then click the app and navigate to Manage | Properties, then scroll down to the Assignments section, you will see all of the assignments for each of the Update Rings have been created and applied to this version.
As the following table shows, when using Immediate Rings, the software is installed immediately for any users in any of the groups assigned to any of the update rings.
0
Corel Pilot Users Corel All Users
Yes Yes
1
Corel Pilot Users Corel All Users
Yes Yes
2
Corel Pilot Users Corel All Users
Yes Yes
It is only when a new version of the targeted software gets released (current plus one or n+1), do the assignments from the previous version get moved to the latest version and Update Rings start to function as configured.
Now, let’s assume a new version (2024.2) gets released.
In this scenario, you can:
Wait until the overnight sync runs to pick up the new version.
Run the Sync Now process to update just this deployment immediately.
Once the deployment has been updated, if you look at its properties, you will see that for the Ring 1, version 2024.2 has now been assigned to the Corel Pilot Users group.
But if you click on Ring 2, you will see that version 2024.1 is still assigned to the Corel All Users group.
If you check in the Intune admin center, you will now see both the existing app (version 2024.1) and the new version we have just deployed (version 2024.2).
If you check the assignments for the original deployment (version 2024.1), you will see it is now only assigned to the Corel All Users group.
Whereas, if you check the assignments for the new deployment (version 2024.2), you will see it is only assigned for now to the Corel Pilot Users group.
Two days after the new version of the app is released, the assignment for the Corel All Users group will be automatically moved from the version 2024.1 deployment to the 2024.2 deployment, automatically upgrading the members of the Corel All Users group to version 2024.2.
The old version of the app (2024.1), will remain, but will no longer show as Yes under the Assigned column in the Intune admin center. At the next sync, the old version of the app will be deleted.
This update process is summarized in the following table:
0
Corel Pilot Users Corel All Users
2024.1 2024.1
Yes No
2024.2 2024.1
1
Corel Pilot Users Corel All Users
2024.2 2024.1
No** No
2024.2 2024.1
* Number of days after the new version of the app is released
** Any new users/devices added to the group will receive the version applicable to the group.
2
dBase Pilot Users dBase All Users
2019.2 2019.1
No** Yes
2019.2 2019.1
2
Corel Pilot Users Corel All Users
2024.2 2024.1
No** Yes
2024.2 2024.2























Applies to: Patch My PC Publisher
Details the production release history for Patch My PC (PMPC) Publisher, the most recent release being shown first.
The "Run installation and uninstall program as 32-bit process on 64-bit clients" option is now set as expected when needed.
The Publisher will no longer upgrade a retained ConfigMgr application in place. This prevents nested 'Retained Apps' folders from being generated.
Newly selected items within the Intune scan wizard now remain selected when you click OK and return to the main form.
In some cases, restoring the Publisher settings from a backup can unexpectedly place files on the desktop.
Ensure that if the Publisher encounters an RPC error while interacting with the SMS Provider, it stops processing the request.
In some cases, this caused a ConfigMgr application's content source to be deleted, and a subsequent sync would create a duplicate application. This build includes remediation to remove the duplicate application if it is not in use and to repair the application that had content deleted.
Restore the ability to use a DNS alias or CNAME when configuring the SMS provider.
Application lists now automatically resync when clicking Apply or Sync
The ConfigMgr Scan Wizard no longer depends on the v_add_remove_program view
Added an optional SHA1 column to the 'Show package info' tool.
Fixed default language detection under localization
Manage Conflicting Process messages now clearly differentiate between updates and installs
Resolved a context menu issue in webhook settings
Corrected a UI glitch that prevented saving webhooks unless a scope item was deselected
In some cases, the in-memory instance of settings would become corrupted. Restarting the service would resolve the issue.
This resolves issues with syncing Intune products. The bug showed in several ways, but the log lines include an "Object reference not set to an instance of an object"
In ConfigMgr, some OS requirements instances did not have a CI_UniqueId for some customers. This caused ConfigMgr applications to fail to create.
Account for ConfigMgr applications that have content instances with a file size of 0.
Fixed a bug where Migration feature would extract MSI installer icons to C:\Temp\Icon.ico
Right-click options now apply to the correct treeview, even when filtered to enabled products.
Improved Publishers ConfigMgr Scan Wizard to remove dependency on v_add_remove_program table.
Fixed a bug where selections in the ConfigMgr DB scan wizard were not persisted on save.
Fixed a bug which caused the Publisher to error when copying ConfigMgr applications. This resolves the error 'Uninstall Content not found in Contents collection.'
Publisher improved handling of missing v_Add_Remove_Programs ConfigMgr view
Fix a bug where some PS scripts can hang
Fixed bug affecting Intune apps export
Fixing UI bug where user couldn't save webhooks without unselecting one of the scope items 🇱
Fixed a bug where the list of selected products was copied between Intune tenants when you have the filter option enabled and you switch tenants.
Fixed an issue where WSUS Options could not be opened in Publisher if SmsProvider was not configured in Publisher settings.
Fixed a bug where the Publisher may select the incorrect SMS_Content instance in some cases when searching for a previous ConfigMgr application.
Migration from ConfigMgr to Patch My PC Cloud (Private Preview)
Read only for Enterprise+ customers
Read/Write for Enterprise Premium customers
Add support for ECDSA code signing certificates
Enabling publisher to allow users to override win32 app options for custom Intune apps and Intune updates
Updated the process for saving logs to use a SaveAs to allow users to customize the location and filename of the saved logs
Enhanced the notifications to include included/excluded status
Added a notification to the ConfigMgr scan wizard to notify users when there are SQL errors
Fixed a bug where additional files, folders, and Patch My PC defined pre/post-scripts were not processed when updating existing ConfigMgr applications
Fixed an issue where Selective Sync (Publish Now) would not take into account postponed ConfigMgr app updates, causing all postponed app updates to be processed regardless of Selective Sync enablement
Fixed a bug where Publisher would leave behind files from older versions of an application
Fixed a bug that caused Manage Conflicting Processes to fail to close running applications in some scenarios
When processing a ConfigMgr app, the Publisher will validate that the PackageId found in a package.xml maps to an application deployment type with a matching content source path.
If a ConfigMgr application copy fails, the left-behind content is also removed.
Fixed a bug that caused the MCP User Notification Timeout to not be translated from minutes to seconds when written to package.xml. The result is a notification being open for 5 seconds instead of 300 seconds, for example.
Note: To fix existing apps or updates with this issue .
Fixed a bug that resulted in an error when attempting to save a MCP User Notification Timeout Setting.
Allow a maximum run time of 1440 minutes for Manage Conflicting Processes for Intune.
Add the user name, user domain, device name, session ID and Windows OS version to the PatchMyPC-Sriptrunner.log.
Collect additional information regarding certificate validation failures.
Add Japanese localization text for Manage Conflicting Processes.
Fixed a bug that caused some right-click options, such as setting an update to metadata only, to take a long time to apply when set at the ‘All Products’ level.
Fixed a bug that caused the Publisher to fail to load the complete list of selected products from settings.
Fixed a bug causing the Publisher to fail to process selections from the CVE Import Wizard.
Fixed a bug that caused the treeview searchbox not to retain the previous search text.
Support applications in the catalog that download a zip file.
Idea:
Note: Additional backend and procedural changes are needed before this will be used. The Publisher can consume a catalog with software that downloads a zip file. We will not add any products like this until Q1-Q2 2025.
Scriptrunner will now expand environment variables provided in custom command line arguments.
Improve how the Publisher reads and writes settings.
Prevent the Publisher from overwriting user setting changes while a sync is happening. Previously, if a user was in the UI and clicked save while a sync was running, the user’s changes could be lost.
Prevent the Publisher from losing Intune configuration due to an abandoned mutex.
If found, the ‘Collect Logs’ button will now include the WSUS softwaredistribution.log.
Fixed a bug where Graph queries would fail if they contained a date-time filter and the machine running the Publisher had the OS set to specific cultures.
Fixed a bug where a ‘BaseInstallOnlyNotForUpdating_’ prefix would appear when using the %OriginalName% variable.
Fixed a bug where an invalid logging path was allowed, causing the Publisher not to log anything to disk.
Fixed a bug where canceling out of the Dynamic Assignments form would still apply the settings.
Intune Updates will now have the icon for the product associated with them.
Added Czech, Finnish, and Norwegian translations for .
Fixed Danish translation for .
Imported banner images are stored in the installation directory of the Publisher instead of referencing the source file.
Fixed a bug that caused the synchronization to stop if a tenant failed authentication. This impacted the Publisher with an MSP license and a multi-tenant setup.
Fixed a discrepancy between the PowerShell detection scripts and the ScriptRunner detection logic.
Fixed a bug with the filtering options for webhook notifications. The notifications should now be correctly filtered when the summary option and scope are set. For example, ‘Send alerts as each product is published…’ is unchecked, and only ‘Include Intune update notifications’ is checked.
Updated to include the list of selected products.
Added support for Microsoft Teams Workflows as a new webhook provider option. With the announced , we now support the new Workflow options. Our Teams notifications have been updated with new templates.
Configured are updated on sync for ConfigMgr applications, Intune applications, and Intune updates. If there is a mismatch between the settings in the Publisher and the published application, then the return codes from the settings will be applied. It is no longer necessary to republish a product to update the return codes.
Add support for passing additional headers when downloading binaries. This is metadata maintained by Patch My PC.
Fix a bug that caused republishing a custom ConfigMgr application with additional files to fail in some scenarios.
Fixed a bug where the return codes in settings could be duplicated if the treeview was refreshed, or you switch tenants in a multi-tenant setup.
Update Intune detection to account for registry detection checking for a nonexistent property. We now allow a NotEquals check for a property that might not exist. Previously, this would cause an unhandled exception.
Signed the installer with our renewed code-signing certificate.
Manage return codes
Idea:
Use a temporary staging directory for binary downloads when processing ConfigMgr applications
Improved handling of the cloud connection.
Improved how ConfigMgr content is resolved to ensure we choose non-retained applications if present.
The tooltip and icon for Manage Conflicting Processes suggested configurations are now more contextual.
Fixed a bug that caused the ‘Prevent the end-user from opening an application while the application is updating’ feature to not work for ConfigMgr or Intune applications in some instances.
If a product is renamed, the requirement rules for Intune Updates may not update as expected. This applies to custom applications and Patch My PC catalog applications. The old requirement rule for an Intune Update would be left behind. The requirement rules should now be maintained as expected when a product is renamed.
If the temporary file location configured in the Publisher does not exist, we now fall back to the system temporary directory. Previously, if this directory did not exist the PatchMyPcService would fail to start.
Fixed a bug where the secrets, such as the Intune application registration secret, would not be saved in the correct format on the first UI open for a new install.
Support for ‘Allow available uninstall’ in Intune
Idea:
Implement coexistence
Coexistence ensures the customer is aware when a product is already managed by Intune Apps for Patch My PC Cloud.
Improve our regex usage in the detection of applications published by Patch My PC.
The regex string is now stored in base64 in the PowerShell script to prevent Intune from clobbering UTF8 characters.
Enable the ‘‘ option at the root of Customer Apps if at least one product supports it.
Enable the ‘‘ option for Custom apps on the ConfigMgr tab.
Fixed a bug that caused custom applications with a main file larger than 2GB to fail to process.
Fixed a bug that caused a circular reference when processing Intune dependency relationships with greater than 2 layers.
Fixed a bug that caused ConfigMgr applications to be copied for retention even if the current version fails to download.
Ensure proper wildcard support for ? in detection.
It is now possible to adjust the chunk size used for uploading chunks to Azure. It can be .
PowerShell detection scripts no longer call whoami. This resolves issues where the PATH environment variable may have conflicting whoami processes.
The ‘‘ right-click option can be used to generate new scripts with this change. Otherwise, products will have the script updated when a new version is released.
Product selections are stored and matched based on a product Id
A message box will appear when a ‘
Fixed a bug that caused a null reference exception if a recommended pre script, and a recommended post script were configured on a product.
The configured proxy will be used to get an access token during cloud connection creation.
Disconnecting from the cloud tab did not save to settings.
Cloud features were not using the configured proxy. The proxy configured in the Publisher will now be used.
Update Patch My PC TOS
Custom apps
Idea:
Improve how the list of custom products is queried from the cloud.
Improve the cloud connection flow to account for the EU region.
Various typo corrections in the UI and in the log.
Improve logging for retained ConfigMgr applications.
Fixed a bug that made connecting to an EU Patch My PC cloud customer inconsistent.
Fixed a bug causing the copy between tab options not to work as expected when custom applications are configured.
Fixed a bug where ESP associations would copy between the Intune Apps and Intune Updates tab.
Improved how .intunewin files are handled to ensure we can process large files.
Ability to create Custom App updates and base installs (Public preview)
Idea:
The Publisher must have ‘‘ checked in the About tab.
*** Report lines have been updated.
As the catalog grows and the number of syncing products increases, our *** report line has gotten too long! CMTrace does not parse the line, and it will not show it. To prevent this, we have split up the report line into one line per type. Below is an example.
Implement certificate pinning. All requests to Patch My PC domains will have the certificate validated.
Fixed a dead ‘More Info’ link for WSUS certificate management.
Fixed a bug causing dependencies to be removed from an Intune Win32 application when republishing.
Fixed a bug where publish now and delayed ConfigMgr apps did not work as expected.
Fixed a bug that caused a new install of Patch My PC Publisher to be in ‘Intune Only Mode’ regardless of the checkbox state.
Sync only selected apps/updates during a sync
Idea:
Allow the management of Delivery Optimization configuration for Intune assignments.
Idea:
Implement a new download engine across all components.
Detection method improvements.
Support parsing version numbers that use – or _ instead of .
Improved logging regarding installer downloads and sourcing.
Fixed a bug where the wrong ID property was shown in the ‘‘ tool for the update ID.
Fixed a bug where Manage Conflicting Processes may be enabled if is enabled. This is unexpected behavior that will no longer occur.
Fixed a bug where multiple threads could access some components of settings at the same time, causing a race condition.
Fixed a bug where the ‘Change Visibility’ option for WSUS updates would not work if the WSUS DB is called something other than SUSDB.
General security fixes and improvements
Update the Intune to use the for both the collection of applications, as well as application extended info. This prevents a 429 when retrieving the data.
Updated Publisher to reflect changes in Graph API schema. This should resolve issues with the .
Add support for .cmd files in pre/post-scripts.
Idea:
The Update ID is now an available column in the tool.
Updated some graph calls to use a smaller page size. This reduces the chance of receiving a 429 or 503 response from graph.
The page size is configurable from 20-999 in the Advanced tab of the Publisher.
The product treeviews are now sorted by Vendor and then Product Name automatically.
Fixed a bug where a ConfigMgr application’s supersedence relationship was lost when the application was upgraded in place.
Fixed a bug where the sorting of products in the email report was in reverse alphabetical order.
Adjusted log levels of some lines to assist with troubleshooting.
Update context menu items to reflect new labels in ConfigMgr for featured apps.
Update several labels in the UI to be more clear on their functionality.
The ability to set ‘Prevent the end-user from opening an application while the application is updating’ is now only allowed at the per-product level. This setting is only needed in specific scenarios, and enabling it for all products can be problematic.
Fixed a bug where Intune device counts are not reporting properly.
Email and Webhook notifications now include information about delayed ConfigMgr applications during each sync.
Idea:
Add support for creating an Available assignment for All Devices. This was previously not supported by Intune. Support has been added, and the Patch My PC UI now allows it as well.
Added the option to import CAB files when importing tenants.
Email and Webhook notifications are now sent when a delayed ConfigMgr application fails to download. Previously a notification would only happen if the Publishing failed after the delay.
Improved the cleanup of registry keys related to ‘Prevent the end-user from opening an application while the application is updating’ in .
Fixed a bug where PowerShell scripts for Intune were created with an encoding of UTF8 with BOM. They are now encoded as UTF8 without BOM, which is the recommended encoding based on Microsoft documentation.
Fixed a bug where a malformed ConfigMgr folder item (SMS_ObjectContainerItem) would be created the first time the Publisher moved a ConfigMgr application. The result was a folder that could never be deleted.
Fixed a bug where having a product marked with exclude from auto-publishing rules and a custom naming convention or pause set would cause invalid XML to be generated.
Enable for MSP-based updates
Idea:
Intune option added to ‘’ for Intune products. This can be configured globally, per vendor, or per product.
If a PMPC-defined pre or post-script is missing from the content source for ConfigMgr applications, then the Publisher will redownload it during a sync or republish.
The expected and actual hash of files found in the local content repository is now added to the log in debug mode. This has always been the case for files downloaded from the internet.
Fixed a bug where non-Windows devices may show up in the drill-in.
Fixed a bug where republishing an Intune product would cause the application to be deleted from Intune if retention was also enabled and set to zero.
Fixed a bug where the Publisher would not check the WSUS certificate validity unless at least one WSUS update was selected.
Fixed a bug where the requirements for Workstation or Server OS would not be set for postponed ConfigMgr applications.
Improved the content of alerts when additional files or folders are missing when Publishing a product
The ‘Configure SMS Provider connection’ button is no longer highlighted if unconfigured in WSUS Standalone Mode.
Improved the logging for SMTP initialization and error handling.
All titles in the email report now link to release notes if available.
Fixed a bug where the Publisher would not add a PMPC-defined script to an existing product.
Fixed a bug where Scriptrunner did not append the provided Silent Uninstall Arguments to MSI uninstalls.
Fixed a bug where some UI listviews had a broken filter.
Fixed a bug where the Manage Conflicting Process window may be offset from the bottom right corner.
Added a filter for Superseded to the .
Adjusted some log levels and log text to be clearer.
Added additional logging when the proxy settings are loaded in the event of a failure.
Add the ability to limit the number of threads used during the upload of Intune packages.
Fixed a bug where whitespace at the beginning or end of the Organization Name for would cause the property to fail to parse correctly.
Fixed a bug where old setting backups would not rename properly, causing an error during settings backup in some cases.
Fixed a bug where some network operations would not use the configured proxy.
Fixed a bug where the code signing of ConfigMgr detection scripts may fail to validate the digital signature on the endpoint.
Fixed a bug where selecting Intune Standalone Mode during the initial installation of the Publisher would not hide the Updates and ConfigMgr Apps tabs.
Fixed a bug that caused a failure to rename legacy settings backup CAB files.
Fixed a bug where Scriptrunner would fail to parse the registry when searching for Uninstall keys if there is an empty string in the SystemComponent property.
Fixed a bug where may unexpectedly match against all selected updates.
Improve speed of creating .intunewin files for Intune package creation
Fixed a bug where ConfigMgr applications would fail to install with error code 0x80070057 or “The parameter is incorrect ” during the installation.
If an existing application has this problem in your environment you will need to the affected application.
The trigger for this bug is having the ConfigMgr option set to ““
This bug was introduced in preview version 2.1.6.35 and carried through to production version 2.1.7.0.
This release contains a variety of features, improvements, and fixes, as noted below.
This will be made available via the self-update channel over the next 2 weeks. You can upgrade in place now by downloading the latest .
ConfigMgr and Intune scan wizard allow drilling into list of devices where the software was detected.
Idea:
Ability to enforce timestamping, making it a terminating error for the publishing of a product
Idea:
When exceptions are thrown in the Manage Assignments form, they are now handled better by presenting a popup with the exception and a link to related documentation.
Main form accessibility has been improved.
Accessibility names are assigned to many controls to provide context
Alt-codes are added to most buttons that did not have them before
Fixed a bug that caused the Paused products section in the email alert to be empty.
Fixed a bug where we would not put back the version on retained applications if the configuration was set to remove the version from application names and update existing application metadata.
Fixed a bug in the tool that caused an unhandled exception if you attempted to edit an assignment with a deadline in the past.
Fixed a bug where the settings backups were stored in a non-sortable format. This bug was introduced in preview 2.1.6.1 and would only impact customers who opted into preview.
Setting or at the vendor level will now display the list of affected products similar to when these selections are made at the All Products level.
Updated language in the Update Republish message box to reflect new UI changes for Advanced WSUS options.
Fixed a bug where a sync may run multiple times back to back.
Fixed a bug where Intune authentication did not use the configured proxy.
Fixed a bug where an Intune application or update would not update the code signing configuration of the detection script. Republishing an Intune application or update will now update the detection and requirement scripts and code signing configuration as needed.
Include server name in Publisher upgrade notification email and Teams/Slack notification.
Idea:
Adding German and Dutch translations to
Intune Filter viewing and configuration is now available in all instances of managing Intune Win32 assignments in the Publisher.
All setting backups are now in a .CAB format. The import setting option now allows for .XML or .CAB import to ensure we support importing older setting files.
The right-click option now removes shortcuts from the user desktop for user-based applications.
Fixed a bug where scriptrunner may fail to find the uninstall string in the registry for some products.
Fixed a bug where scriptrunner may fail to validate an installation after the installer completes causing a 3-minute delay after the installation completes.
Fixed a bug where does not account for postponed binaries. If there is an existing postponed binary it will publish even if a pause is set.
Fixed a bug where some publishing summarization info was miscounted in the PatchMyPC.log file.
Add Intune multi-tenant support
Idea:
Requires MSP license
Dynamic Assignments for Intune
CSV files are now saved with UTF-8 formatting.
PatchMyPC.log file now includes the timestamp for the catalog that is processed.
When a download happens we now write the redirected URL to the PatchMyPC.log as well as in the PatchMyPC-DownloadHistory.csv.
The Publisher will now retry every 10 seconds up 12 times when saving Package.xml for ConfigMgr applications. This helps account for file locks caused by antivirus.
Fixed a bug where Intune ADR would publish both an Application and an Update.
Fixed a bug where we might fail to match a running process with Manage Conflicting Processes if the case of the process name did not match.
Fixed a bug where illegal characters were allowed in file paths, such as a custom log path.
Fixed a bug where an application may report being automatically enabled during every sync in some scenarios.
Support for maintaining application dependencies in Intune
Checkbox added to Intune Options window: “Update application dependencies from previously created applications when an updated application is created”
Idea:
When republishing an Intune application or update there is now a prompt asking if assignments should be recreated. The newly recreated assignments would have a deadline and available time relative to the sync when the republish happens.
Fixed a bug where republishing a ConfigMgr application would remove existing application dependencies, supersedence, and requirements the customer may have added.
Fixed a bug where the Manage Conflicting Process option to use the ConfigMgr application max run time for the notification timeout would not work for a republished ConfigMgr application.
Fixed a bug where republishing an Intune application or update might remove existing assignments.
Fixed a bug where we may fail to put back the version on the name of retained ConfigMgr applications in some scenarios.
Collect Logs button added to the Publisher. Will create a .zip file of files useful for troubleshooting.
Idea:
If the ConfigMgr applications are configured to remove the version from the name, and there is application retention configured we will now append the version to OLD versions of the app. This is to ensure that there is only one application with the same name.
Improved the initial configuration process for adding Patch My PC Software Updates to an environment. This involves attempting to restart the WCM component after an initial Patch My PC update is published. This expedites getting the Patch My PC category into ConfigMgr so it can be selected.
The Publisher will send an alert if the catalog failed to download.
Fixed a bug where the Republish feature may cause multiple republish actions to occur if the customer performs the operation on multiple tabs.
Fixed a bug where ‘disabling’ a tab with the checkbox at the top would cause the settings to be lost if the Publisher was closed.
Fixed a bug where the alert webhooks may be duplicated during a setting import.
Fixed a bug where some unsupported right-click options might be enabled by the auto-enable product’s rules.
Allow customized popup notifications, including support for localization.
Idea:
Clicking a ‘localhost’ download URL in will validate the local content.
It is now possible to ‘Manage ESP assignments’ from within the .
ConfigMgr database scan button is now available on the ConfigMgr apps tab as well as the Updates tab.
ScriptRunner will always use Intune-based folders when executing from an Intune app installation.
ScriptRunner will now monitor for child processes during the uninstall of software. This ensures that uninstalls which spawn child processes do not exit immediately and cause a detection error.
Fixed a bug where the Publisher would fail to parse a command line that had a parameter that occurred more than once. This would cause a content update every sync.
Fixed a bug where Recreate Detection Script option for ConfigMgr would cause the wrong ‘Installation Behavior’ to be set for user-based apps.
Fixed a bug where the Publisher and ScriptRunner would fail to parse a parameter with nested quotes and spaces.
Fixed a bug where PreventStart UI would fail to be bypassed when a SYSTEM launched a conflicting process potentially leaving behind Image File Execution Option registry keys.
Improve conflicting process timeout options
ConfigMgr and Intune timeout increased to their respective maximums, minus a 15-minute buffer.
ConfigMgr App Max: 705 minutes
Intune Max: 45 minutes
Text boxes within the UI now implement an autocomplete for file paths and URLs.
The notification will now display ‘update’ based language for an Intune Update. For example, the button will say ‘Close and Update’ instead of ‘Close and Install.’
Fixed a bug where the Publisher would throw an exception if a ConfigMgr scope is deleted, but still associated with a product in the Publisher.
Fixed a bug where Intune email reports would not include the warning regarding missing local content for applications
Fixed a bug where the ConfigMgr would perform a partial match, such as \\server\source_apps being considered a conflict for \\server\source. We now append a trailing slash to the comparison.
Fixed a bug where the ‘Prevent Start…’ option for
Double-clicking a product in the Publisher will now bring up the ‘‘ tool.
Idea:
The Publisher will now check the permissions associated with the token for the Azure App Registration and provide more specific errors and logging. Additionally, the ‘Test’ button now presents a more information UI for permission validation.
Added tooltips to fields in the scan wizards to improve accessibility.
The Publisher will not delete the local content for a product if the publishing of the product failed.
The Publisher will automatically revise an update if the applicability rules or description is updated in the catalog.
The Publisher now supports log rollover of up to 10 log files. Previously we would only retain one rollover log. This is configurable in the General tab of the Publisher above the max log size.
Fixed a bug where the Manage Conflicting Process window may not show the proper process name in the list of conflicting applications.
Fixed a bug where the Publisher did not respect the ConfigMgr app retention settings when the delay in-place upgrade feature was also in use.
Fixed a bug where Intune apps and updates would not use the temp content download directory specified in the advanced tab.
Fixed a bug where the Publisher would revise ConfigMgr apps every sync in certain cultures (The known issue was with Russian, but could impact others).
Manage Conflicting Process ‘Close and Update’ button will now call the CloseMainWindow first. If the conflicting application is still running after 20 seconds we fall back to the Kill method.
This gives the user 20 seconds to respond to any ‘save’ prompts or other app-closing windows.
Idea:
Pre/Post scripts for uninstall
If publishing an update fails with timestamping then we will attempt to publish again without timestamping.
Improved connection testing to patchmypc.com:443 during publisher sync.
During Publisher sync the WSUS cleanup for ‘Unneeded update files’ will now run.
Manage Conflicting Process UI should now scale better vertically.
Fix user validation of the input fields for pre/post script when the file does not exist.
Fixed Intune detection script which was looking for a non-existent ‘dn’ property.
Fixed Intune detection script so that it will parse invalid version parts that exceed a 32-bit signed integer.
Fixed ConfigMgr detection script so that the RegKeyDetection work as expected for enhanced detection based on additional registry key values.
Allow the
Idea:
Fill out ‘Disk Space Required’ for Intune apps.
Idea:
Further improvements to CM log format for culture compatibility.
Add support to re-sign updates.
Idea:
Doc:
Use windows native methods for signing PowerShell scripts.
PowerShell detection scripts will use regex to extract the version from the displayVersion field to account for vendors that put more than the version in the field.
Set ErrorAction to SilentlyContinue for extra regkey validation checks to suppress errors in the event the key does not exist.
Add a delay in Scriptrunner if the main installer exits in less than 2 seconds. This is to account for installers that spawn child processes.
Fixed a bug where a ‘Security Error’ may occur when signing PowerShell scripts and a PowerShell Execution Policy is set via GPO.
Add option to update Intune assignments on sync.
New checkbox at the bottom of the Manage Assignments wizard to ‘Override manual assignment changes…’
Idea:
Add the title of the application or update to the Manage Assignments wizard.
When a product is double-clicked in the tool the applicability rule will be shown.
Improve the message which displays when an incorrect configuration is saved.
Code changes in preparation for user-based applications.
Publisher SMTP alerts for the creation of ConfigMgr apps, Intune apps, and Intune updates will all now show the CVE information. Previously only the WSUS updates would show this information.
Fixed a bug where the Manage Conflicting Process window would not appear when a ConfigMgr application was deployed as required and the checkbox for ‘Allow user interaction…’ was not checked.
Fixed a bug where Intune role scope tags would not be updated on sync for Intune Updates.
Fixed a bug where the configured proxy may not be used for the Intune connection during publisher sync.
Fixed a bug where software may be marked for revision during every sync of the Publisher. This would occur when PreventConflictingProcessRestart was in use and the KillProcess was set instead of Notify.
Adding a right-click context menu to the Intune App Manager allowing you to navigate to the MEM portal to view some application information.
Fixed a bug where ConfigMgr applications would not populate in the Publisher if a scope was set at the All Vendors or the Vendor level.
Added the Usage Statistics group in the General tab that will show usage statistics
Idea:
Changed the license input to display only the 20 character license id and not the full license URL
Define ConfigMgr scopes inside the Publisher service
The Intune and ConfigMgr scan wizard ‘Export’ buttons now prompt for whether the filter should be applied to the export.
Improve how Timestamping is handled in some scenarios.
Improved the speed of Intune application deletion by using batch calls to Microsoft Graph
Options related to WSUS have been moved from the Advanced tab to the Options button in the Updates tab
The classification field in the Intune Apps Manager is not populated for Updates
Update revision doesn’t take account of republished updates
Connections to Intune may not respect the proxy configuration set in the Publisher.
‘Show Package Details…’ right-click option would not load as expected.
ConfigMgr right-click option to set OS type requirement – client vs. server
Idea:
Intune Scoping Support
There is a for Intune applications and updates which lets you ‘Manage scope tags.’
Scriptrunner will now automatically prompt for elevation when executed.
Improve how settings are saved to prevent losing your Publisher configuration in some scenarios such as no disk space.
The UI Notification feature for conflicting processes will now exit with an exit code 1602 if the installation is snoozed or a timeout occurs. Previously it was 1618 which could cause very frequent reevaluation.
Wait to delete local content repository files until the end of the Publisher sync if the option to ‘Delete the update file in the local repository after publishing’ is selected.
Fixed a bug where we may fail to parse a package.xml file that contains special characters such as an ampersand.
Fixed a bug where the DownloadUrl and MoreInfoUrl columns were not sortable in the ‘Show Package Info’ UI.
Fixed a bug where the UI may crash if there is a large number of Azure AD Groups being retrieved and the UI is closed before the query completes.
Fixed a bug where some right-click options such as Manage Categories, Manage ESP profiles and Manage Naming Convention may not propagate from the root, or vendor level to a newly enabled product.
Interactive user notifications that allow the user to be prompted to close conflicting software
Has a range of options for customizing the deferral options. See the for more information.
Idea:
Delete N-# applications / updates in Intune
Only one instance of the Publisher is allowed to run at a time. If a second user runs the Publisher they will receive an error message and the Publisher will close.
Intune Application Manager button is now available in the Intune Apps and Intune Updates tab directly, as well as in the Intune Options.
ConfigMgr detection scripts now validate the architecture and installation type of the software being detected.
This feature was in place for Intune scripts and has been integrated into the ConfigMgr scripts.
Fixed a bug where adding file-based right-click option to a ConfigMgr application would not trigger a revision in some cases.
Examples: MST, Pre/Post Script, Additional files
Fixed a bug where the Intune detection and requirement script might fail to work as expected if there are invalid registry properties on an object in the registry.
Fixed a bug where the new Conflicting Process settings may not be saved for ConfigMgr applications.
This version of the publisher will be rolled out over the coming week. If you would like to upgrade now you can download the latest MSI .
Modify Autopilot Enrollment Status Page profiles.
Update ESP profiles when an application is updated. This will ensure the latest application version is associated with your ESP.
New to enable.
Select profiles an application should be assigned to with a new .
PatchMyPC-ScriptRunner has improved logic for UninstallPackage.
Now factors in SystemComponent and QuietUninstallString when searching the registry.
Intune Scan Wizard updated to match the ConfigMgr scan wizard.
Can include zero-count applications in results and export.
Fixed a bug where the certificate option would be enabled while in
‘Intune Only’ mode.
Fixed a bug where the Intune Graph token used by features such as Intune App Category selection would expire if the Publisher UI was open for a long time.
Fixed a bug where unnecessary calls were made to renew the Graph API token when performing Graph Batch queries.
Product selections made in the Intune Scan Wizard did not persist after clicking Save & Close or Apply in Publisher UI.
Ensure we populate the list of configured Distribution Point Groups within the ConfigMgr options.
Ensure that when the treeview refreshes, cached product selections are updated, and the filter-to-selected-products checkbox is correctly reset to avoid confusion.
Update exception handling when a connection to ConfigMgr fails to ensure it halts application processing.
Updated the temporary location of the settings.xml file during import to allow it to overwrite the current settings properly.
settings.xml is read or write-locked and provides better visibility for test webhook notificationsProduct export CSVs include more detailed data
Better handling for postponed apps that fail to copy to the target directory
The %Version% variable always applies if configured, regardless of global override.
Publisher email reports and logs now highlight when local content is outdated
When opening the UI, logs indicate whether the Publisher service is running
Added selective sync support at the “All Products” level, showing tenant and app type in the pop-up
Improve how we gather ScopeId for migration
Flags like Republish and SelectiveSync update safely without overwriting settings.xml
CVE links in reports now point to www.cve.org
Selective sync behavior for vendor-level and all-vendor selections is more predictable
Intune Scan CSV exports use consistent column headers with the Scan Wizard
Migration logs now identify which app is being processed
Refined wording in the Pause Product Updates popup
Added an event handler enabling full migration resync from the Cloud
Migration tracking now includes the Publisher version used for inventory
Improved phrasing in the Intune App Manager window
UI layout and spacing received general polish for smoother navigation
Teams webhook notifications now use consistent column widths
Increased text size in Publisher email reports for readability
ScriptRunner now removes desktop shortcuts only when explicitly requested
Manage Assignments group selector sorts by date more accurately
Added a tenant column to the webhook page for better visibility
Prevented WSUS updates from being enabled without a valid WSUS connection
Fixed a logic error where Publisher selected the wrong SMS_Content instance
Corrected AllUsers and AllDevices status showing as “excluded” in Teams alerts
Logs now correctly record when SMS provider credentials are supplied
Eliminated exceptions when opening the UI during an active sync due to settings.xml access
Automatically creates postponed binaries folders when configured
Fixed Intune app export behavior
Newly selected scan wizard products now appear correctly when filtered to enabled products
Blocked saving SMS Provider credentials when the provider is the local machine (WMI limitation)
Accept localhost, 127.0.0.1, and . as valid SMS Provider values
Stopped telemetry from querying WSUS configuration when WSUS isn’t set up
Resolved issues where deleted ConfigMgr apps weren’t fully cleaned up
Prevented sync operations from running on expired licenses
Fixed sorting by Created date in the Intune Filters view
Eliminated hangs in the Intune App Manager when editing ESP assignments
Log entries now capture missing local content errors accurately in patchmypc.log
Restored the ability to copy and click links/data in the Package Details view
Fixed MSI icon extracting to C:\Temp\Icon.ico - This no longer happens
Publisher now handles ConfigMgr apps with zero-byte content instances
Corrected read-only column states in the Intune App Manager
Properly initialized the Migration SignalR hub to ensure metadata processing
Date sorting in Intune Application Manager now produces consistent results
Fixed ConfigMgr app copy errors: “Uninstall Content not found in Contents collection”
Resolved install failure in preview build 2.1.50.2 for WSUS-disabled environments
Add a progress bar to the Publisher UI - displays the current application or update being processed
Add a filter button to only show products that are selected in the Publishers UI
Improved how Publisher displays information around misconfigured items and items that require manual content to ensure the warning does not consume the entire screen
Trigger search in Entra ID Group Search window when pressing Enter key
Present a warning when importing a code signing certificate if ConfigMgr is set to automatically manage your code signing certificate
Add additional fields, related to user install statistics, to the Intune Application Manager
Modernised the icons in the Publishers UI
Ensure the scrollbar on the Intune application scan wizard only shows when needed
Improve the logging of PowerShell-based detection and requirement script signing
On new installs the PatchMyPC.log file is stored in the Logs subfolder of the installation directory
Write the name of the account used to run PatchMyPCService to the publishers log file
Amended the rolled over log file extension from .lo_ to .log
Log username of active user when using Manage Conflicting Processes to kill processes
Improved logging when ScriptRunner calls PowerShell scripts
Add an IntuneReportsRequestTimeout registry option to set the timeout for Intune reports (default: five minutes)
Update tooltips in the Publisher UI for Manage Conflicting Process timeouts to reflect Intune changes
If the code signing certificate is not found, then WSUS updates will not process
If the code signing certificate is not found and ConfigMgr detection script code signing is enabled, then ConfigMgr apps will not process
Improve the handling of UINotificationSettings.xml for Manage Conflicting Processes - now generated per session to prevent access denied errors
Fixed the URL for the Patch My PC logo in webhook alerts
Fixed a bug that would allow a configuration of maximum application runtime that conflicted with the Manage Conflicting Process notification runtime
Fixed a bug that caused the filtering of Intune groups to hang the UI
Fixed a bug where rolled over log files were not cleaned up according to retention settings
Fixed a bug where the Publisher may select the incorrect SMS_Content instance in some cases when searching for a previous ConfigMgr application
This fix addresses the alert "Unable to process <Application Name>. PackageId… does not find an application with a matching content source path…"
Fixed a bug that caused customers to see an error message if ScriptRunner tries to display a notification while Focus Assist is enabled
Fixed a bug that caused Postponed binaries to fail to process when custom applications are enabled and the PostponedBinaries folder does not exist.
Fixed a bug where the option to select the ConfigMgr folder within the ConfigMgr application creation options was not available.
Stop processing a ConfigMgr application if the copy operation for retention fails. This ensure we do not edit an existing app unless the copy succeeds.
Added the total sync time to the PatchMyPC.log
Improved logging when there is a cloud connection, but no Intune deployments in the cloud.
Fixed a bug causing scriptrunner not to expand placeholder arguments such as %CURRENTDIR% when parsing command line arguments.
Fixed a bug causing errors similar to ‘Mutex access requested by GetIntuneAppProductFlags but a timeout occurred while waiting for mutex to be released’
Fixed a bug that caused custom applications to fail if they had two files with the same name inside their content.
Fixed a bug that caused email reports to erroneously indicate a pause product for tenants that do not have the product enabled.
Add support for Patch My PC to configure the ‘Run installation and uninstall program as 32-bit process on 64-bit clients’ option within ConfigMgr. This will not be a customer exposed option in the Publisher, but something that Patch My PC can set to ensure applications install as expected.
Improve the product search function in the Publisher to keep the search box open when no match is found.
Scriptrunner has improved logic for handling the log location for user-based installations. If the default values are left in the Publisher, the log path will be updated to a user-writable location. This includes the scriptrunner log and the installer log.
Updated Publisher settings backup retention to retain settings from previous weeks and months.
Update the Swedish translation for Manage Conflicting Processes based on customer feedback.
The search functionality in the product treeviews now consider custom applications. Previously the list of custom products would not be included in the search.
Improved logging during a Publisher synchronization for products that are marked end-of-life by Patch My PC.
Update some labels and logging to be in line with the latest terminology used in Intune.
The Update ID and Update Title are now written to the PatchMyPC-Scriptrunner log file.
The username of the user who performed a save in the Publisher is now written to the event log, and to the PatchMyPC log file. Additionally an empty file with a GUID name is included in the CAB so the save event can be matched to CAB file.
The test email for SMTP configuration had a blank subject and body.
Fixed a bug causing the Manage Assignments form to hang while resolving Entra group names in some scenarios.
Fixed a bug where the Publisher would include non-Windows applications in the scan results for Intune auto publishing.
Fixed a bug that caused webhook summary notifications not to respect the tenant filter.
Fixed a bug that caused the Publisher to attempt to code sign Patch My PC defined scripts when the code signing option was disabled in the Publisher.
Fixed a bug that caused the install time offset for Intune assignments to be displayed incorrectly in some cultures.
Fixed a bug where cloud Product Selections were only displayed in the Publisher if the product was both deployed in the cloud, and selected in the Publisher. Products which are not selected in the Publisher will now properly show as managed by the cloud if a deployment exists.
Removed the references for the SSRS reports and replaced them with Advanced Insights.
The Win32AppId is now included in the PatchMyPC-PublishingHistory.csv file.
Improved the handling of signed scripts when publishing. Sometimes, the Publisher would fail to replace a file and throw an exception. We now ensure the destination file is deleted before moving in the updated file.
If configured to Kill or Notify, the tooltip and icon are removed
If configured to Skip, the icon is shown, and the tooltip says, “Manage Conflicting Processes is recommended for this product and will be configured to Skip by default”
If configured to ‘Perform the installation,’ the icon is shown, and the tooltip says, “Manage Conflicting Processes is recommended for this product but is currently not configured”
Fixed an incorrect translation for Manage Conflicting Processes. The default English text had the word ‘Applications’ translated.
Improve how we search for ConfigMgr application content.
When creating the cloud connection in the Publisher, the System Default browser will now be used.
If needed, the embedded web browser can still be used with a registry flag.
The ‘Collect Logs‘ button now collects all PowerShell detection scripts modified within the last 7 days. The scripts are renamed to have a .txt extension before being added to the zip file.
Additional default translations added to Manage Conflicting Processes
Added German, Danish, Norwegian and Swedish
Fixed Dutch translation
Icons in the product treeview now indicate if the product requires local content, or is configured to skip the install if running by default.
Expand out aggregate exceptions when they are logged.
Improved user experience both for a disconnected cloud configuration and an empty custom app list.
Use less memory when uploading .intunewin files to Intune.
Improve the user experience when the ConfigApi is not available
The UI can now start without the ConfigApi being available. A popup message will still appear indicating it cannot be reached.
When this is not available, the cloud features of the Publisher will be disabled.
Fixed a bug that caused some right-click options to not clear their state as expected for custom apps.
Editing Manage Conflicting Process options did not light up the Apply button.
Fixed a bug that caused the Publisher to fail to retry when uploading chunks to Azure.
Fixed a bug where a custom application download may compare hash against an older version of the custom application’s hash.
Fixed a bug that caused the treeview to have a yellow background, as if no products are selected, even when products were selected.
Custom Applications are supported in the ConfigMgr apps, Intune apps, and Intune updates tabs.
A license with one of the below subscription levels is required.
Enterprise Plus
Enterprise Premium
MSP
Implement Publish Now for Custom Apps
Support detecting software that translates DisplayName
Idea: PATCHMYPC-I-1335
Add support for configuring Win32 application max runtime in minutes
Implement a safety check prior to deleting a ConfigMgr application. In some instances, the SMS provider returns an empty list of apps instead of a connection exception. To account for this, we ensure at least one Site is returned by the SMS provider prior to application deletion.
ConfigMgr script size is reduced. No functional changes. This should help with metadata download issues over CMG.
Add support for the ? wildcard character in detection.
Improve some popup notifications to direct the user to the correct tab.
Improve cleanup during service shutdown.
Update the default login authority for Intune. It is now https://login.microsoftonline.com
This will not affect existing Intune configurations. It is only a change to the defaults for a new connection.
Implement an attempted reconnect when a WMI query fails against the SMS provider.
Improved scriptrunner logic for finding uninstall strings. DisplayVersion will now have any “-” or “_” replaced by a “.” when searching for uninstall strings. This matches the behavior of our script based detection.
Servers are no longer included in Intune device counts.
Resolved a race condition which caused the additional webhook filtering options to be unavailable in some instances.
Improved download engine logging to include the URL when the download fails. This was a regression that is now resolved.
The logging path for Intune Manage Installation Logging incorrectly defaulted to the ConfigMgr path. It is now corrected to the Intune default path for logging.
For some sync schedules, the ‘Next Sync’ time displayed in the General tab was in UTC instead of local time. The correct time should now be displayed.
Fix logging during the creation of Intune products when local content lookup fails. The Publisher would incorrectly log that the existing application would be deleted.
Fixed a bug causing Enforced Uninstall Arguments to be ignored for ConfigMgr apps. This resulted in some ConfigMgr apps being created with an uninstall that may not work as expected. The next sync after the Publisher is updated will fix these products’ uninstall configuration.
The connection name is now required in the Cloud tab.
Fixed a bug that caused a Null Reference Exception when exiting the Manage Conflicting Processes configuration in the Intune apps or Intune updates tab.
This was a regression that only impacted preview builds
Fixed a bug that caused the custom naming convention for ConfigMgr applications to be overwritten during a sync in some cases.
Fixed a bug where the authorization token can expire when connecting to Custom Apps, requiring a service restart.
Fixed a bug where Right-Click selections for “All Products” on the “Intune Apps” tab would be lost when custom apps was enabled.
This was a regression that only impacted preview builds
Note: Existing DO configuration on an assignment will also carry forward now when a new version of the software is Published.
The Intune Application Manager Utility now has some multi-select bulk options.
Use CSV-based reporting endpoints for detected software per-computer.
This should prevent 429 responses when getting the list of devices with an application.
WMI connection test to SMS provider prior to deleting ConfigMgr content.
Improve cleanup of files during the synchronization of Intune.
Updated the “Enabled” header of CSV exports in scan wizards to be less specific.
OK button has been changed to ‘Save and Close’
Open to feedback on this change. We have received a fair number of reports that it is unclear the ‘OK’ button will close the UI.
Fixed a bug that caused the right-click menu at the root to sometimes not display correctly.
On the ConfigMgr Apps tab, if the option «Add the executable name in the deployment type’s install behavior» is enabled, the Manage Conflicting Process is automatically enabled to kill processes.
Fix crash when sorting some columns in the Manage Assignments tool.
Fixed a bug that would cause a republished Intune product to have the content for the latest version and the metadata for version n-1.
This would occur if the republish flag is set and there is a new version of the application in the catalog.
The list of Intune assignment filters is now filtered to Windows.
Fixed a bug where in some scenarios, the republish flag would not be removed after a sync.
Fix a possible null reference exception when loading assignments for bulk delivery optimization edits.
Fixed a bug where the custom logging path may be reset to defaults instead of inheriting the expected value.
Fixed a bug where PatchMyPC Scriptrunner logging did not use an invariant datetime format. This could cause CMTrace to fail to parse the logs.
Fixed a bug where an exception may occur if deleting a large number of Intune Applications using the Intune Application Manager Utility
Fixed a bug where some data exports would result in malformed date time strings. This occurred if a culture used the same character for the number group separator and for time parts.
Fixed a bug where ConfigMgr detection script logging did not use an invariant date-time format. This could cause CMTrace to fail to parse the logs.
Fixed a bug where Manage Conflicting Process logging did not use an invariant date-time format. This could cause CMTrace to fail to parse the logs.
Fixed a bug where the option to abort an uninstall if the prescript failed caused an argument parsing exception.
Fixed a bug where the automatic backup of setting changes would fail in certain cultures due to a date-time parsing issue.
Fixed a bug where custom naming conventions were copied between tabs. We no longer copy naming conventions when copying products between tabs.
Recreate Detection right-click option for Intune
Idea: PATCHMYPC-I-2605
Fixed a bug where the Pause was never removed from Intune applications.
Fixed a bug where the Publisher would check for the WSUS code signing certificate even if updates were disabled in some scenarios.
Fixed a bug where the DateTime formats in the Usage Statistics section of the Publisher were inconsistent.
Fixed a bug where some temporary folders were not cleaned up by the Publisher. These will be retroactively cleaned up once this build is installed and running.
Scriptrunner will now log out a comma-separated list of all public desktop shortcuts if the installing product is configured to delete desktop shortcuts.
This is to help troubleshoot when icons for applications are not deleted.
Improved how running processes are enumerated for Manage Conflicting Processes making the popup more responsive.
Implemented a ‘retry’ in the event of failure for many critical interactions with Azure via Microsoft Graph.
The Publisher will delete files from the download cache if there is a hash mismatch for the file. This makes the root cause of Publishing failure easier to identify.
Fixed a bug where the UseGSInstalledSoftware registry option would cause the ConfigMgr database scan to never perform a query.
Fixed a bug where a failure to download an icon would cause a product to fail to publish.
Fixed a bug where the ‘Republish…‘ option is not unchecked on Intune products if the UI is left open while the synchronization runs.
Intune package extraction
It is now an option to store the encryption keys used to create the Intune package files (.intunewin). This is configurable in the Advanced tab of the Publisher.
With the keys stored, you can use the Intune Application Manager to download and extract the content of the Patch My PC published Intune applications and updates.
Webhooks can now be granularly scoped based on several criteria listed below. (Requires Enterprise+)
Idea: PATCHMYPC-I-1871
Webhook Provider:
Slack or Teams is now selectable per webhook allowing the customer to send notifications to both based on their needs.
Notification Level:
All
Error
Success
Notification type:
Update notifications
ConfigMgr app notifications
Intune app notifications
Specific product
Scope a webhook to a specific product, such as notifying the network team of VPN application updates being published.
Specific tenants
If using multi-tenancy, you can specify the tenant a webhook is scoped to.
Allow variables to be used to customize the ConfigMgr application name and localized application name. This provides parity with the Intune feature for customized names. The variables available are below.
%VendorName%
%ProductName%
%Version%
%OriginalName%
ConfigMgr application retention now has the option to remove Administrative Categories from retained ConfigMgr applications.
Idea: PATCHMYPC-I-2181
ConfigMgr security scopes now have the option to enforce the selected scopes. The Publisher will remove all non-selected scopes from the application when Publisher.
Idea: PATCHMYPC-I-2328
Allow any product to have Manage Conflicting Processes configured
Idea: PATCHMYPC-I-1699
Allow the same Azure group to be assigned multiple times for Intune assignments. This allows a group to be used as both an include, and an exclude.
Idea: PATCHMYPC-I-2322
Pass variables into pre and post-scripts.
Note: the %ProductName% and %VendorName% variables are Base64 encoded when they are passed to the pre and post-scripts. It will need to be decoded. Patch My PC will provide a sample PowerShell snippet to decode the resulting parameter.
Idea: PATCHMYPC-I-1348
Extract content from ConfigMgr applications.
Extract content from WSUS updates.
Azure app registration secret or certificate expiration is now shown in the Intune Options form.
Alerts are now sent via email and webhook when secret or certificate expiration is near.
Right-click options are now accessible via the Apps keyboard button or shift-F10
When a default Patch My PC provided translation exists for a language selected in Manage Conflicting Processes it will now automatically populate the text upon adding the language.
Intune synchronizations will now happen in parallel for multi-tenancy. Up to 20 tenants synchronize at a time for this build.
Improve the speed of uploading packages to Intune.
Refactor email report template.
The background is now transparent so that it will match the theme of the email client it is opened in.
The code used to generate the template has been refactored to simplify future changes.
PatchMyPC-Scriptrunner will now factor in the major version filter when available when searching for uninstall strings. This improves the accuracy of uninstalls in some cases.
Added tooltips to some right-click options that describe why they are disabled in some cases.
Improved the error handling within the Intune Assignments forms regarding permissions for managing Assignment Filters.
Format the dates using ISO 8601 formatting when doing the Intune App export for PowerBI reporting. This improves international support.
Improved the accessibility of the WSUS Options form.
Improve error messaging and logging for unhandled exceptions.
Improved child-form handling in some cases, so they now open in the center of the parent form.
Multi-selection views, such as selecting application scopes or categories, now use a consistent form that allows filtering.
Fixed a bug where the filters were not applied in the scan wizards when filtering the data. This bug was introduced in preview 2.1.6.1 and would only impact customers who opted into preview.
Fixed a bug where the ConfigMgr database scan may throw an exception due to a malformed query. This bug was introduced in preview 2.1.6.1 and would only impact customers who opted into preview.
Fixed a bug where the logging option to copy failed logs to a share was not retained. This bug was introduced in preview 2.1.6.1 and would only impact customers who opted into preview.
Fixed a bug where failing to copy additional files did not cause an Intune product to fail to publish.
Fixed a bug where localization files for Manage Conflicting Processes may not be copied correctly in some cases.
Fixed a bug where the WSUS Options window was not scrollable.
Fixed several UI navigation bugs on the main form.
Adjusted encoding of detection and requirement scripts to use UTF8. Some scripts were failing to sign with the previous encoding.
Fixed a bug where the Manage Conflicting Process Organization Name was not retained when republishing a ConfigMgr application.
Fixed a bug where the wrong URL was used for Microsoft Graph batch requests in some cases.
Fixed a bug where the buttons in Managed Conflicting Process may not fit the text in some translations.
Fixed a bug where the ConfigMgr app options window is not resizable.
Fixed a bug where the Manage Conflicting Process Organization Name would not be set when a ConfigMgr application was revised.
Fixed a bug where settings could not be saved if the internet was unreachable.
Fix some typos 🙂
The SMS provider button is now highlighted in the WSUS options if the SMS provider is not configured.
Updated default Manage Conflicting Processes banner.
ConfigMgr operating system requirements are now recreated when an application is updated. This ensures new operating systems such as Windows 11 or Server 2022 are added as applications are updated in place.
Fixed a bug where the Publisher would leave behind an empty folder when Publishing a ConfigMgr application and the download fails.
Fixed a bug where a version number would be appended to the current ConfigMgr application instead of the retaining application if the download fails. This bug affected customers who had the ‘Do not include version…’ option configured as well as the ‘Retain…’ option.
Fixed a bug where an empty Intune tenant is written to settings causing errors when the Publisher attempts to query the invalid tenant.
Fixed the layout of the Add MST transformation file form.
Fixed a bug where we may fail to query for Distribution Point groups if the name or description is DBNull instead of an empty string.
Fixed a bug where the ConfigMgr SUP sync would not start after a Patch My PC Sync if only updates using local content were published.
Fixed a bug where the Intune auto-publishing may fail in some cases when right-click options are configured.
Idea: PATCHMYPC-I-1433
Requires Enterprise Plus
Allow Intune assignment and ESP options to be set per product to override global options.
Idea: PATCHMYPC-I-1831
Per product retention setting for Intune Apps and Updates
Idea: PATCHMYPC-I-1568
Validate the hash of pre/post scripts on sync as well as during a republish.
Idea: PATCHMYPC-I-1946
Collect Logs button now prepends the file name with the company name from the license.
Idea: PATCHMYPC-I-1904
The email report now converts size to a readable format such as MB or GB instead of bytes.
Idea: PATCHMYPC-I-1331
Support for Intune Filters
Idea: PATCHMYPC-I-1434
Requires Enterprise Plus
Certificate Authentication for Azure App Registration
Idea: PATCHMYPC-I-1540
Option to pause creation of updates or applications for specific products
Idea: PATCHMYPC-I-1554
Requires Enterprise Plus
Allow per-tenant branding for Manage Conflicting Process
The email report has been updated (dark mode)
Add an operator dropdown in the filter options for Intune and ConfigMgr scan wizards
Improve Manage Conflicting Process configuration window to better support scaling
Fixed a bug where the Manage Conflicting Process UI would not show up for a user-based application.
Fixed a bug where the Manage Conflicting Process UI would not show for an Intune application when the user is not an Administrator.
Fixed the Collect Logs button so it takes into account custom log paths as defined in the Publisher.
Fixed a bug causing enter to close the group search form for Manage Assignments when in the group input textbox.
Fixed a bug where PatchMyPC-Scriptrunner may throw an exception during log cleanup if the folder does not exist
Fixed a bug where the publishing summary in the PatchMyPC.log would not include products published from the local content repository
Fixed a bug where changes to Intune assignments are applied even if the assignment form is cancelled
Fixed a bug where the Manage Conflicting Process window would not show up when the product install is triggered via Company Portal as a non-admin user
Fixed a bug where ConfigMgr app retention setting right-click option is not checked when configured
Fixed a bug where the Updates (WSUS) tab could be used while on an Intune license
Fixed a bug where the Manage Conflicting Process UI may fail to identify conflicting processes causing it not to show.
Fixed a bug where the Manage Conflicting Process UI may default to a 5-hour timeout for ConfigMgr applications in some scenarios.
Fixed a bug where delayed ConfigMgr applications may publish one day early.
Fixed a bug where the IsFeatured flag would not be set for a republished Intune application.
Fixed a bug where the Publisher would fail to validate a ConfigMgr source path if there were Deployment Packages with an empty source path.
Fixed a bug where the Publisher may delete a content folder during republishing if the binary was missing from the local content repository.
Fixed a bug where the Manage Conflicting Process UI notification would fail to display if the user DateTime format and the system DateTime format were conflicting, causing DateTime parsing failures.
Fixed a bug where the Manage Conflicting Process notification timeout setting may not be read correctly from settings.xml.
Updated to the latest Patch My PC logo.
Fixed a bug where conflicting process notification timeout setting was not being read properly from settings.xml causing the setting to not apply.
Fixed a bug where the /SyncNow switch for the Publisher would not work if an instance of the Publisher was already running.
Fixed a bug where multiple assignments for the same group may attempt to be created in Intune.
Fixed a bug where the Organization Name specified for the Manage Conflicting Process window would not be populated for ConfigMgr applications.
Fixed a bug where the icon would not be set for a republished Intune application.
Fixed a bug where the republish ConfigMgr application feature would not validate the hash of existing additional files which caused edited files to not be copied during a republish.
Fixed a bug where republish ConfigMgr application would not set the expected OS requirements.
Fixed a bug where ‘Override manual assignment changes’ is checked for an Intune product, and there is an ‘exclude’ assignment which would cause the Publisher to fail to process all assignments.
Option to “Republish” ConfigMgr and Intune Applications
Idea: PATCHMYPC-I-1353
Prevent using a ConfigMgr source path that could cause paths to exceed the 256 windows path limit.
Fixed a bug where publishing would proceed even if a custom script failed to be processed.
Fixed a bug where retained applications may be updated unexpectedly when both postpone app and retain app are configured.
Fixed a bug where the Publisher would run a sync every time ‘Apply Changes’ is clicked and the schedule is set to hourly.
New option to use ‘maximum run time’ from the respective update or app.
ConfigMgr Update Max: Will use configured update ‘max run time’ as configured in ConfigMgr for the update.
Note: Update max run time must be edited before the update is deployed for a client to recognize the change.
ConfigMgr App Max: Will use the configured deployment time ‘max run time.’
Intune App/Update Max: Will use the maximum run time of an Intune Win32 app (60 minutes minus the 15-minute buffer).
Idea: PATCHMYPC-I-1516
Send an alert if the Publisher failed to auto-update.
Idea: PATCHMYPC-I-1254
Send an alert when the Publisher is updated
Idea: PATCHMYPC-I-791
Add time zone to Teams/Slack Webhook notification
Idea: PATCHMYPC-I-856
Split out notification settings to allow Error notifications and Information notifications to go to different webhooks
Idea: PATCHMYPC-I-1536
Fixed a bug where assignments would be copied from Intune app to Intune updates when the copy between tabs is used.
Fixed a bug where custom return codes set in the catalog were not processed for updates by the Publisher.
Fixed a bug where ConfigMgr applications would be revised every sync when the Manage Conflicting Process option is set to an option other than ‘Notify’
Log current working directory in PatchMyPC-ScriptRunner.log
Idea: PATCHMYPC-I-1504
Export the list of enabled products and their right-click configurations to a CSV. This option is available in the Advanced tab of the Publisher. Only enabled products are exportable.
Publisher will validate the ConfigMgr application source path. A path is considered invalid if it is not a UNC path, or if the path is in use by a Software Update Deployment Package. Existing invalid configurations will not be impacted, but there will be an alert via email or Teams if alerts are enabled.
Idea: PATCHMYPC-I-1299
Fixed a bug where the alert webhook configured for Slack may revert to a Teams webhook causing malformed messages.
Fixed a bug where the Manage Conflicting Process UI may continue to append text instead of having a countdown when it is set to ‘Do not allow user deferral…’
Fixed a bug where pre/post uninstall scripts would only copy into the ConfigMgr source during a new application publisher. Scripts will now be copied into the source during the sync after the configuration change.
Fixed a bug where the Intune Assignment UI would allow an invalid grace period/restart/snooze configuration.
Fixed a bug where PatchMyPC-ScriptRunner would create an invalid command line for an MSI uninstall in some cases.
Fixed a bug where the Manage Conflicting Process UI would fail to enumerate some properties of the blocked processes causing it to close the blocking process before the user can interact.
Idea: PATCHMYPC-I-550
Manage Conflicting Process settings also apply to uninstall. This ensures that a user will be prompted to close software for the uninstall as well.
Idea: PATCHMYPC-I-1430
Allow multiple webhooks so alerts are posted to multiple endpoints.
Idea: PATCHMYPC-I-1301
MSI uninstall performed by Scriptrunner will append REBOOT=ReallySuppress to the uninstall command.
MSI uninstall performed by Scriptrunner will generate an MSI log file if logging is configured for the application in the Publisher.
Idea: PATCHMYPC-I-1492
The Show Package Info wizard will now show the file size from the catalog.
Idea: PATCHMYPC-I-1461
Script Version: 3.1
Fixed a bug where double-clicking an item in the Intune App Manager would cause an ‘Index out of Range’ unhandled exception. This now opens the Manage Assignment wizard as expected.
Fixed a bug where ConfigMgr applications with only user-based deployment types would have the checkbox set to allow installation during a task sequence, which is not allowed.
Fixed a bug where the UI notification log file may not be created if the folder does not exist.
Fixed a bug where user-based ConfigMgr applications may not have the Application Experience configuration properly configured.
Intune app manager will filter by PMPC published apps by default, providing a drop-down to select non-PMPC or all apps.
Idea: PATCHMYPC-I-1460
Within the ‘Show Package Info‘ window, you can now right-click on any cell to copy the cell data or the row data to your clipboard.
Idea: PATCHMYPC-I-1468
Can be disabled with a registry key as noted here.
Idea: PATCHMYPC-I-1420
Notifications are presentation mode aware
Idea: PATCHMYPC-I-1248
View and customize Conflicting Processes list
Idea: PATCHMYPC-I-1382
The UI notification for Conflict Processes now lists all processes which are conflicting in a dropdown. This is to make it more clear what software will be closed.
Send alerts to Slack
Idea: PATCHMYPC-I-684
Note: Slack notifications are a work in progress.
Reverted a Scriptrunner change which flagged the exe to always run as Administrator. This is in preparation for supporting user-based applications in Intune and ConfigMgr.
Added notes to the pre/post script window to help clarify the feature functionality.
Fixed a bug where the 'Exclude from Auto-Publishing' option for Intune apps and Intune updates may not work as expected causing excluding software to still be published if found.
When a user or admin category was selected on a ConfigMgr application the Publisher would create a revision of the application every synchronization. Now a revision will only be created if a user or admin category needs to be added.
Improved logging when checking access to timestamp.digicert.com if a proxy is defined
Idea: PATCHMYPC-I-962
Note: This requires updated permissions. The ‘Import Role’ option in the Publisher will import the role with proper permissions or you can refer to this article.
CVE Wizard would not load as expected.
SSRS dashboards would report a negative % for compliance in some scenarios. The reports can be reinstalled if you are affected by following the same process as the initial install which will overwrite the reports.
Scope tags will be copied from the previous PMPC application or update to the new version during Publisher sync.
Requires new permission to be added to the Azure App Registration
DeviceManagementRBACRead.All
Idea:PATCHMYPC-I-1029
Change description text and icon for Intune Win32 applications
Idea:PATCHMYPC-I-1158
Retain N-X apps in ConfigMgr when set to ‘Create a new application…’ is enabled.
Idea:PATCHMYPC-I-1266
Retain N-X apps in ConfigMgr when set to ‘Update existing application…’ is enabled.
Idea:PATCHMYPC-I-1265
In some cases, customers had the same binary needed for two different publish actions, and the second publish would fail because the binary had been deleted.
In the DownloadHistory.csv file, we now include the purpose of the download and the port.
The scan wizard found application count is now updated to reflect applications found with the specified filter.
Scriptrunner will now clean up leftover ‘Image File Execution Options’ registry keys. This helps prevent unexpected blocking of application launch in the event scriptrunner crashes and leaves behind some of these keys. We have also update the Manage Conflicting Processes docs to provide additional information for this scenario.
Updated the ConfigMgr detection script to cast the DisplayVersion to a string before trimming in the event a vendor has created DisplayVersion as a DWORD and not a REG_SZ
Script Version: 2.9
The ‘Purpose’ field will now be cleared in the Intune App Manager when all assignments are removed.
Fixed a bug where assignments may not be added to an existing Intune Win32 application during Publisher sync.
Fixed a bug where the Publisher UI would crash if the ‘Modify Updates Wizard’ was launched on a computer that does not have the WSUS role.
Fixed a bug where only the first 1000 Intune applications are returned which can cause Application lookup failures via Microsoft Graph.
There are new settings available in the ‘Intune Options’ which allows you to specify retention for Intune Applications and Intune Updates. The valid values are between 0 and 10.
Idea: PATCHMYPC-I-967
InstallPackage as the default behavior for ScriptRunner
When the PatchMyPc-ScriptRunner.exe is double-clicked it will default to searching for package.xml in the same directory and performing /InstallPackage which allows PMPC application install to be launched without running them from the command line.
Idea: PATCHMYPC-I-1170
Apply Intune naming convention to existing applications and updates during a Publisher sync
Idea: PATCHMYPC-I-1175
Set ‘Featured App’ flag on Intune apps via right-click options
Idea: PATCHMYPC-I-1188
Use Scriptrunner to uninstall MSIs
Idea: PATCHMYPC-I-1083
Use MainFile to uninstall software
Idea: PATCHMYPC-I-991
Increase the max delay for the ConfigMgr delay application creation feature to 32 days.
Idea: PATCHMYPC-I-914
Script Version: 2.8
Fixed a bug where the company logo may not show in the Conflicting Process UI for Intune clients.
Fixed a bug where the Conflicting Processes deferral count would allow more than the configured number of deferrals.
Requires updated App Registration Permissions.
DeviceManagementServiceConfig.ReadWrite.All
Idea: PATCHMYPC-I-673
Support for MSP Patching via Intune.
Idea: PATCHMYPC-I-1147
ScriptRunner will use QuietUninstallString when found for application uninstallation.
Idea: PATCHMYPC-I-930
Add an additional Right-Click option for x86 OS requirement for x86 application installers
Idea: PATCHMYPC-I-779
Sign PMPC provided pre/post scripts with local WSUS Code Signing certificate
Idea: PATCHMYPC-I-959
ScriptRunner now deletes log files older than X days according to the setting in Advanced Tab.
Idea: PATCHMYPC-I-1105
Filtering options updated.
The ‘Exclude from auto-publish…’ option now exists for Intune Apps and Intune Updates.
Scan Wizards will now automatically allow vertical scrolling if needed.
Improved vertical scrollbar behavior for Scan Wizards
Implement a retry when performing some ‘POST’ operations to Microsoft Graph to improve Intune Win32 app creation reliability.
The warning message box that pops up if the Enrollment Status Page right-click option is invoked without proper Azure App Registration Permission now has a ‘Help’ button that links to the permission KB article.
The pre and post script ‘browse’ buttons now will open to the location of the currently selected script if found.
Update right-click option text to accurately reflect functionality.
Exclude from being enabled during automated SCCM/Intune inventory scans
Renamed to: Exclude from auto-publishing rules
Add/Manage pre/post update installation scripts
Renamed to: Add/Manage pre/post scripts
Patch My PC defined pre/post update installation scripts
Renamed to: Patch My PC defined pre/post scripts
Fixed a bug where the ConfigMgr ‘Recreate Detection’ option would not set the VersionInclude for the newly generated script.
Fixed a bug where an Enrollment Status Page may have a mobileAppId listed twice when making the Graph PATCH API call. This would cause a 400 status code, and cause the API call to fail.
Fixed a bug where the Intune Scan or ConfigMgr Scan would happen if the respective ‘Auto-Enable’ option was enabled, but the feature itself, such as Intune Updates, was disabled.
Fixed a bug where the Teams notifications for auto-enable would not contain details regarding the software.
Fixed a bug where the auto-enable feature of Intune Scanning may cause duplicate Win32 apps to be published within Intune.
Fixed a bug where conflicting right-click options could be selected in the scan wizards.
Fixed a bug with the new Log Retention feature of Script Runner where it may unnecessarily trigger an ‘Update Content’ on ConfigMgr applications.
Alert notifications
Low disk space, certificate expirations, license expirations etc.


Applies to: Patch My PC Publisher
Details the production release history for Patch My PC (PMPC) Publisher, for version 1.0.0 - 1.9.9.
for Intune Applications
Idea:
Improved the updating of supported products metadata during Publisher synchronization.
Adjust certificate signing validation for Patch My PC signed files.
Fixed an issue where for MSI-based applications would not populate some variables in the script.
Manage categories for Configuration Manager applications
User Categories: Viewable to users in Software Center
Admin Categories: Viewable to administrators in the Configuration Manager Console
Idea:
During a Publisher sync, the Settings.xml will be automatically updated according to SupportProducts. This improves the experiences when Patch My PC makes metadata changes that impact some of the application configurations such as detection.
The Intune Application Manager now has a button for ‘Manage Assignments’
Improve how ScriptRunner handles version parts that exceed the 32 bit signed integer max.
Improve CVE-ID matching
Manage Intune categories for created and updated Intune applications and updates.
Note: Currently, existing applications/updates in Intune will not have their categories removed but new categories will be added for existing Win32 applications.
Idea:
Clicking a ‘digest’ in the Modify Published Updates Wizard, or the Package Details wizard will now open the respective VirusTotal page.
Sorting by ‘Selected’ in Modify Published Updates Wizard now sorts by the checked state.
The Configuration Manager detection script now handles invalid version parts better. Some vendors use DateTime stamps in their version. This can end up being a value larger than a 32-bit integer causing the version cast to fail.
Fixed an issue where copied Intune Assignments for newly published Intune software would not have their custom available time, and deadline time adjusted relative to the new publish date.
Fixed an issue where Intune Assignments would be created without a deadline or available time if the ‘copy assignment’ option was not configured.
Fixed an issue where the maximum value for restart notification would not allow a value greater than 201.
Fixed a bug where the console version check for UninstallContent setting was incorrect.
New feature that allows .
Idea:
The below information can be viewed for the currently synchronized catalog.
Title (Including version)
Improved the speed at which the catalog is processed. This will improve the loading speed of the CVE Import Wizard, the new Package Details Feature, and the Modify Updates Wizard.
Improved the speed at which the catalog is extracted for the CVE Import Wizard.
Win32 Intune applications will no longer be created as featured by default.
Existing Intune applications will not have their ‘featured’ state changed. The Publisher will retain the currently configured ‘featured’ setting for any given application.
Fixed a bug where new Intune assignments may not be created.
The first release of our CVE import/matching features based on UserVoice
You can launch the CVE import feature in the Updates tab by clicking the new document lock icon
If you have any feedback on the first release, leave a comment at
Updates published via the CVE Import Wizard will have a Teams and Email alert if enabled.
Certificate selection for Intune code signing will now additionally search the WSUS store if it is found.
The Product Name has been added to the PatchMyPC-DownloadHistory.csv generated in the installation directory of the publisher.
Improved the method used to gather PackageID from newly published Applications.
Fixed a bug where an application may fail to publish on versions of Configuration Manager older than 1706.
Fixed a bug where the publisher would fail to find applications published to a folder containing square brackets
For Example: \\server\sources\[PMPC]Applications
Fixed a bug where the TLS port for SMTP alerts may show as 587 in the UI, even when a custom port is set. The port in the UI will now accurately reflect the saved settings.
Application update in-place vs. create new application configurable at the individual product level.
Idea:
Support for user-based installations for Configuration Manager applications, as well as Intune Applications and Intune Updates.
Log out the in-progress count of updates and applications as they are processed.
Previously the in-progress count was only logged if the log level was set to debug. It is now logged with informational level logging.
Improve the PatchMyPC-ScriptRunner.exe to have better logic when searching the registry for uninstall strings
The PatchMyPC-ScriptRunner.exe will retry MSI based operations if a 1618 exit code is returned by the installer. The result is a reduction in failed installs due to Windows Installer being unavailable.
Configuration Manager application detection script fixed to supported PowerShell 2.0.
Fixed an issue where republishing a WSUS update would also cause the equivalent Intune Update to republish as well.
Publisher code changes to better support our program
Fixed an issue where the would throw a terminating error if Intune applications were found with an empty ‘Notes’ field.
Added an option to disable WSUS publishing using a checkbox at the top of the 'Updates' tab. This allows the Update publishing feature to be disabled while still retaining all products and settings. This can be helpful if you need to sync only Applications, Intune Applications, or Intune Updates, but don't want to lose your selected Updates and configurations.
Added a right-click option to open the help page that details the right-click options.
During synchronization, the Publisher will check if the WSUS code signing certificate is expired or near expiration and add a message in the email report.
Add additional known errors in the log, providing a link to a KB article that may assist with solving the known error.
Display additional info in the Certificate information wizard on whether the certificate is found in the expected Windows Cert stores.
SMTP port default to 25 instead of 587 when the feature is in a non-configured state.
The Publisher will retry several times when the rename of a folder during an SCCM application upgrade fails. This should help prevent
Fixed an issue where, sometimes, the SupportedProducts.xml file cannot be read during a synchronization.
Fixed an issue where a machine with a large number of CPU cores may experience high CPU load when running the Intune Scan Wizard.
Fixed a bug where if the is enabled and an update contains spaces in the file name such as Firefox, it may download with an incorrect file name.
This would cause the following error in appenforce.log:
**fails to install error code Looking for exit code
-2147467259 in exit codes table**
The Publisher now has a 'Recreate Detection Script' right-click option. When this is selected, the specified products will have their Detection Scripts recreated during the next Publisher synchronization.
Idea:
The Modify Updates Wizard now has a checkbox to 'Show Only Updates for Not Enabled Products'
Intune Application and Update detection script now has improved version string parsing
Intune Application and Update detection script will only parse DisplayName for a version if the DisplayVersion is empty
SCCM Application detection script will only parse DisplayName for a version if the DisplayVersion is empty
VLC is now split into an EXE and an MSI
Fixed an issue where the Publisher was unable to get the list of published Intune applications.
Fixed an issue where a republished WSUS update may be republished multiple times if the Publisher was left open during synchronization and settings were changed after the initial republish completes.
Fixed a bug where certain detection scripts generated for Intune Applications and Intune Updates would not detect as expected.
Improved the copying of right-click options from the Updates tab, to the ConfigMgr Apps tab, or the Intune Apps tab.
Fixed an issue where the Publisher would falsely report that it was not installed on a Software Update Point in some scenarios.
Fixed an issue where the Intune Updates product list was not reloaded during publisher sync in some scenarios.
Fixed an issue where Intune Applications would not detect appropriately for certain applications. OneDrive was a known affected product, but others may have been included.
Fixed an issue where the Intune Connection Options would log out an error state 'Invalid Uri.'
Fixed a bug where the publisher would report ‘Cannot get available disk space’ when validating there is enough free disk space for deferred application publishing.
Fixed a bug where the publisher would fail to parse the Proxy URL, reporting the following error.
An error occurred while converting the provided Proxy URL to a URI for use by the Web Client…
See for remediation steps if you are affected.
You can now for allowing the publishing to create Configuration Manager applications.
Within the ‘Manage Assignments’ page for Intune Applications and Updates the cells now have a clickable link to open up the form for managing available dates, deadlines, and restart behavior. Previously this link was only on the application name.
Fixed an issue where SMTP settings were not properly translated when the new Anonymous authentication option was added.
Fixed an issue where right-click settings from the “All Products” level may not be applied when copied to another tab.
Support for Intune Updates
Add Anonymous authentication method to send emails.
User voice
Add a button to export data in the Intune Apps Manager.
Add a column to show Classification in the Intune Apps Manager.
Allow to show «Applications only», «Updates only» are «All» in the Intune App Manager.
Display the Publisher service's status on the 'About' tab.
Fixed an issue where custom options are not correctly copied between two tabs when copying enabled products from one tab to another.
Fixed an issue where reserved characters were not working as expected when searching for Azure AD Groups
Fixed an issue where the Publisher may display a warning that the certificate is incorrect or missing when it's within 30 days of the expiration date.
Changed how Unreferenced Package Folders are found. If third party updates are set to display in WSUS, then they might show up as 'Unreferenced' by the WSUS content cleanup tool. The publisher now correctly display the list of unreferenced contents.
Available date and deadline date for Intune assignments are not properly displayed in the assignment setting wizard
The Publisher may crash when trying to check for a new release on Intune only installation where only RSAT:Windows Service Update Services is being used. If you are affected by this issue, please perform an in-place upgrade of the publisher using
.
Add an Intune Scan Wizard allowing you to auto-enroll applications based on Intune App scanning.
Add all options available in the 'User Experience' for Applications to a new context menu option for base installs.
Add more logging to the application update and creation processes to assist with troubleshooting.
Code optimization and cleanup for applications.
Detection script now accounts for user-based installs when needed.
Detection script checks if running as SYSTEM using the SID instead of the username.
Fixed a bug where the Publisher service would never timeout during content downloads in some scenarios, causing the service to hang.
See the for more information regarding the timeout. The default value is a 15-minute download timeout.
Fixed a bug where some system cultures would result in incorrect command-line parsing.
Fixed a bug where an application's content would not be updated when a right-click option was selected in some scenarios.
Fixed an issue where the admin comment field of a dependent application would be updated to say the application was created by Patch My PC
Fixed an issue where the republish updates right-click menu may exist in the ConfigMgr Apps and Intune Apps tab
Settings tool can crash when copying enabled products from the WSUS tab to another tab if the «All Products» node is not displayed
Teams notifications are malformed if they contain a file path.
Add button to restart the service
Added support for Server 2019 in the
Cache binary for postponed updates allows postponed updates to be published after the download link has changed.
applied at the All Products level are now retained when the UI is closed, and future products are enabled. UserVoice Idea:
Allows creating a self-signed certificate with the private key marked as non-exportable.
Added new subscription state reporting using Teams or SMTP emails
Added 'Like,' 'Dislike', and 'Feedback' button in the title bar of the settings tool.
Fixes
List unreferenced package folders did not list any folders in some WSUS configurations
Added a workaround to handle SCCM apps published with an unsupported language
Resolved incorrect summarization within the SCCM Scan Database tool
Intune assignments created during an application creation or update are now reported in Teams notifications and email alerts
(Idea:
)
Adds a line in the log to specify Intune AppIDs (old and new release) during an application updating (Idea:
)
Improves how Azure AD groups are retrieved (Set page limit to 999). We will also now display O365 groups. Adds the ability to search a group based on the group name starts with (Idea:
An error message is logged out if a device collection attribute is not configured in the SCCM application scan feature
Intune assignments referring to another a customer Azure AD group may be lost from the settings. Previous Intune assignments could be restored by importing a settings backup from the
\\backup folder in the advanced tab.
Mistakenly notify a success when a hash validation failed during an SCCM application in-place upgrade
Added the ability to edit assignments for already published Intune applications using the Intune application manager
Added a column in the Update Modification Wizard to show supersedence based on
Added a right-click option to open Local Content Repository
You can now limit the SCCM application database scan to a specific collection based on
Fixed an issue introduced in build 1.7.3 where assignments for Microsoft Intune applications created directly within Microsoft Intune may be removed if they are not assigned within the Patch My PC Publisher.
We will now create assignments in Intune even if the Intune application was already created before adding the assignment
Fixes
Snooze duration in Intune assignments can be set to an invalid value when the restart grace period and restart countdown are also enabled
SCCM Applications may fail to be created on older SCCM builds with error "An error occurred while creating an application in SCCM: Could not load type
'Microsoft.ConfigurationManagement.ApplicationManagement.ProcessDisplayName' from assembly
Retain Deployment type dependencies during application in-place update
Changes
Changed the behavior of the Scan SCCM Database wizard, add an Ok button, and rename the Close button to Cancel.
Remove «Full Content» mention on Intune and SCCM TreeViews
Fixes
Fix an issue where if there's a WIn32 application larger than 1.95gb, you would receive the following error:
An error occurred while connecting to Intune: JSON integer 2242219440 is too large or small for an Int32. Path
'value[75].size', line 1, position 118932.
Microsoft Intune production release.
This update contains backend changes to prepare for production support for Microsoft Intune in an upcoming release.
Fixed an issue where the code-signing certificate may not save correctly in the Microsoft Intune options.
Improved the Microsoft Intune options. The options are now available in the Intune Apps tab and not the Advanced tab.
Improved the installation options for enabling Microsoft Intune only publishing.
Features
Display application dependencies in the SCCM application manager.
Enhancements to prepare for Microsoft Intune support
Adds a new application management tool for SCCM in the application options menu. You can now bulk delete applications created from Patch My PC or bulk delete deployments for applications
Changed title format for republished updates to be more granular
Included updated DLLs for Compression.cab from Wix
When an update is republished, all previous republished updates can be superseded by the new update that is republished
Fixed an issue where updating MSI based applications may result in an error: An error occurred while updating a package in SCCM: Access to the path \ is denied.
Added the Intune bulk editor in the Advanced tab
Fixes
Fixed an issue where custom files and folders defined, may not be included in a software update cab file
Added a new right-click option in the Applications tab to display an application as featured in company portal.
Fixed an issue where you may receive an error: An error occurred while signing the PowerShell detection script, but there is no error message to display.
Applications will no longer be duplicated in the event the deployment type's source folder was deleted.
You can now trigger a full and delta software update point synchronization from the advanced tab
Microsoft Intune (Release Candidate)\
You can now automate Win32 application management in Microsoft Intune
You can now trigger a full and delta software update point synchronization from the advanced tab
You can now set a custom folder for temporary downloads of the software update and application content
You can now set a custom folder for the log save location
You can now browse to UNC paths when adding a custom folder in scripts dialog
Fixed an issue in version 1.5.7 where youo may receive the following error when an application is updated in-place
An error occurred while updating a package in SCCM: Invalid property: object Application(ScopeId_*) property DisplayInfo.DisplayInfo.DefaultLanguage: Language En does not match any data in the set
You can now right-click an individual product in the application tab and choose to move it to a custom folder in the console
You can now create new folders in the applications node of the console directly from the folder browse dialog
You can now refresh folders in the applications node directly from the folder browse dialog
Improvements
You can now send Microsoft Teams publishing alerts using a webhook
Improvements
The software update point synchronization will be triggered after the update synchronization task rather than waiting for the updates and applications sync.
Improved the accuracy of the SCCM application scan feature to better differentiate between x86 and x64 products based on UserVoice
Fixes
Add support to auto-popular the uninstall command line for 50+ applications in SCCM
Allow searching backward for products and vendors when clicking
(Shift+F3)
Preserve User Categories when updating Apps in SCCM
Preserve Admin Categories when updating an SCCM application
Set default download timeout to 100 seconds from 30 seconds.
Fixes
Fixed an issue where a custom command line may not be processed if it contained double quotes and a space
Fixed an issue where the UI may crash when enabling a large number of products
Improved logging for varias actions including download percentages
Improved logging
Remove leading and trailing spaces in catalog URL, sms provider server name, application source folder path, and timestamp server URL
Create a CSV file at the end of each synchronization with a summary of what was published, revised, created
You can now set the max log size between 1-10 MB
Added an option to show and delete unreferenced WSUS folders in the UpdateServicesPackages folder
Added an option to show/hide already enabled products in the SCCM scan
Added the ability to delay updating applications in-place between 1-14 days after release.
Display the count of updates and selected updates in the update modification wizard
You can choose a custom folder in the applications node of the console to move applications to upon creation or updating automatically.
You can now include custom folders for updates and applications.
You can now configure any custom pre-update script to run before checking any processes to close or skip
Improvements
Improved logging
If SMTP emails are enabled, we will now include any newly enabled products from the automated SCCM inventory scans.
If there are pending settings changes unsaved, you will be prompted if you want to save the settings when performing a synchronization.
You can now automatically enable products to be enabled based on them being detected in the SCCM database.
Added options to Kill or Skip installations when auto-enrolling new products.
Application names are now clickable for applications published, and links to the vendors release notes.
Added right-click option for products to be excluded from being automatically enabled during automated SCCM inventory scans.
New right-click option for applications to Add the Executable Names(s) in the Deployment Type's Install Behavior
New right-click option for applications to Set the max and estimated run times
Logging improvements
Any application created by Patch My PC will now contain and administrative comment of "Created by Patch My PC Version
\"
Fixes
Fixed a bug in version 1.4.7 and 1.4.8 where the application detection script may fail to evaluate when the application is deployed to a user collection as available, and a non-admin user initiates the installation. Note: this was a regression bug from version 1.4.1.
PowerShell detection scripts can now be saved in an additional folder using a registry value. Based on UserVoice item:
Settings file can now be saved in an additional folder from the advanced tab. Based on UserVoice item:
Add an option to always check the local content repository to update content prior to downloading from the internet. Based on UserVoice item:
Powershell detection method scripts are now saved in the
\\Detection Method Scripts folder.
Set requirements to prevent the installation of Flash Player ActiveX on Windows 10 and Windows Server 2016 and 2019 and higher.
Fixes
Products that don't support the application model would be created as a package even if the option to not fall to a package is enabled.
Fixed an issue where application update drop-down menu wouldn't be retained.
The right-click context menu item checkbox will now be checked for the pre/post scripts feature when only addition files are added in the pre/post script dialog window.
If an application is deleted from the SCCM and the content source folder still exists, the application will be re-created during the next sync schedule if it's enabled.
If the application deployment type is set to Allow users to view and interact with the program installation, you will no longer see a dialog window for PatchMyPC-ScriptRunner.exe.
We now handle the non-standard exit codes for Adobe Digital Edition and Evernote so the installation will report successful.
Email reports for publishing updates and applications will now be listed alphabetical order.
Fixes
Fixed an issue where if multiple certificates exist in the WSUS certficaite the detection method script may not get code-signed.
Fixed an issue wherein a small number of cases applications may fail to install with the following error "An error occurred while preparing the installation of the application: Illegal characters in path." in PatchMyPC-ScriptRunner.log
Improved detection for CutePDF Writer and Allway Sync
Changes
Updates and applications will now timeout after thirty minutes
Added an option to include abitrary files in the pre/post script dialog box.
Added an option to copy the installation log to a secondary folder on installation failure.
Fixes
Updated the detection method script for applications to resolve the following error (Access to the path
'C:\Windows\CCM\Logs\PatchMyPC-SoftwareDetectionScript.log' is denied.) that would occur in AppDiscovery.log in certain builds of Configuration Manager.
The base installation feature now creates applications in SCCM rather than legacy packages. Based on customer idea:
Improvements
You can now configure an offset (in days) for the sync schedule. Based on customer idea:
When using a custom pre/post update script, it will be run before any Patch My PC defined script. Based on customer idea:
This update contains improvements to help support the future release of the application creation feature.
The installed version of the publishing service and whether you have opted into the preview channel will be reported.
Fixed an issue where if you switch from the general tab to the update rules tab very quickly the products enabled may reset and the Settings.xml would need to be restored from the
\\Backup folder.
Improvements
Added an option to prefix the computer name to the installation log file name to allow you to use a shared path and receive unique log file names for each device.
Improved publishing for products that use special characters in their install command line.
Fixed an issue where up to 5 products may continually be detected as being revised during publishing syncs.
During the first publishing sync after this update, you may see up to 40 products say that where revised and this can be safely ignored.
Fixed an issue where the "Automatically create installation packages in SCCM for initial installation." in the Package Rules tab would become un-checked when in trial mode.
Added a new right-click context menu item to add MST transformation files for MSI based product installers.
Right-clicking on a product will now display the installer technology the product uses (MSI, EXE, or MSP)
Added support for customer SSRS folder names for the report installer
Fixes
Bug fixes
You will no longer receive an invalid license ID on start in the event no license ID was defined previously.
Added support for required Pre/Post-Scripts
Added support for recommended Pre/Post-Scripts
Improvements
We will now cache the list of supported products, so in the event, the settings tool can't download the latest products, it will use the last cached copy.
When the settings tool is opened, if any products are previously enabled that now have a Patch My PC defined recommended and required Pre/Post script(s) those scripts will be saved in the settings.xml automatically.
Added a section in email report for updates published with Local Content Binary
Improvements
Better handling of situations where SupportedProducts.xml fails to download
3010 is considered as a success code by for pre-scripts when the option to bypass update installation when pre-script fail, is enabled
The option to scan SCCM for applications will now be more accurate for products split by major versions.
You will now receive an email notification if your subscription is expired causing synchronizations to fail to run.
Improved error messages in logs and emails.
Updated the PatchMyPC.chm documentation included in the MSI installer.
Added the new option to enable the creation of base installation packages in SCCM.
Other feature improvements and bug fixes
Disabled the delete option for published updates in the modify published updates wizard.
To enable the Delete button, create a new DWORD registry value: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Patch My PC Publishing Service:EnableDeleteUpdates = 1. We only recommend using this option when working with our support team.
Added an option in the About tab to opt-in to the preview channel.
Increased the number of backup settings files saved from 5 to 50
Fixes an issue where MSI logging options may be removed from a previously published update
Improved logging
Fixes
The Local Content Repository textbox is now read-only
Note: Build 1.2.4 was re-released on 2019-03-07 to resolve an issue where the license validation may fail after the initial installation.
Added the ability to provide custom arguments to pre/post scripts
Added support to run EXE or MSI binaries in the pre/post scripting feature
Added a new option in the right-click context menu in the product rules to republish update(s)
Improved the auto kill/close feature for applications where the process name may change between different versions
Added option to "Un-Decline" updates in the "Modify Updates Wizard"
Added new right-click action in the "Product Rules" tab to allow you to enable installation logging for updates and choose a standard path for the installation logs.
The option to "Scan SCCM for Managed Applications" will now list all products available in the catalog even when the publishing service is in trial mode.
Added filter textbox to allow free-form typing to filter updates in the "Modify Updates Wizard"
Added option in the Pre/Post Script dialog to not attempt an update if the pre-update script returns an exit code other than 0.
Right-click custom actions on the "All Products" in the "Product Rules" tab will be retained when the Publishing Settings tool is re-opened.
Added filtering options in the "Modify Updates Wizard"
Added CC field in the SMTP Settings
Added common SMTP providers in the SMTP Settings
Added last day of the month and last week of the month options in the "Sync Schedule"
Added "About" tab that shows version information, release notes, support options, and how to request new products.
Added "Local Content Repository" option in the
"Advanced" tab. This feature is used if there are licensed products that don't allow for public download in the future. For more details, please see
Fixed a scheduling issue where you may see higher than average CPU utilization if the schedule was set to the Second Tuesday of the month.
Fixed an issue where updates may fail to publish on WSUS 3.0 SP2
(Windows Server 2008 and Windows Server 2008 R2)
HTML email improvements
Update title is now clickable and will link to the vendor's release notes for the update
Added Classification tab to the report
Added Severity tab to the report
Within the "Product Rules" tab, we have added a new option called "Disable self-updater". For applications that support this feature, we will automatically disable the self-update feature for the product after applying any new update. This option is available on the All Products, Vendors, and Product level in the Product Rules treeview.
When custom actions are enabled for a product, the PatchMyPC-ScriptRunner.log will save to %WinDir%\CCM\Logs by default rather than %WinDir%\Temp on the client side for logging custom actions.
Added the ability in the product rules tab to connect to the Configuration Manager database to scan for supported products from our catalog and enable detected products for publishing.
Enabled the kill and skip process option for almost all products
Added a new right-click context menu option for deleting the public desktop shortcut when applicable
Added support to use patchmypc.com in the catalog subscription URL. Previously, you could only use patchmypc.com for your subscription URL.
Added an option to define your own custom pre/post update scripts in each products right-click context menu.
Added an option to open the wsyncmgr.log in the General Settings tab.
Added the ability to change published updates visibility in the WSUS console from the Modify Published Updates wizard in the advanced tab
Added a column to show declined updates in the modify updates wizard
Auto-refresh display in the modification updates wizard when
«Declined» or «Delete» button is pressed
Added a checkbox in the scheduling tab to synchronization the Software Update Point after the publishing services completes and any updates are published or modified
Added the ability to customize the certificate expiration length and key strength when generating a self-signed certificate.
Emails will now use an improved HTML format instead of plain text.
We added a new option to expire all or specific published third-party updates from the Advanced tab.
Added a new tab called Advanced
New option in the Advanced tab named "Standalone WSUS Mode".
When enabled, third-party updates published from the publishing service will be visible and available to deploy directly in the WSUS console. This option shouldn't be enabled if Microsoft SCCM is being used to deploy updates.
Moved the option "Defer Expiration of Updates" from the Scheduling tab to the Advanced tab.
Added the ability to delay the re-publishing of expired updates.
The "Product Rules" tab now supports a semi-checked mode. The semi-checked will appear when only some products under a vendor are enabled.
You can now schedule the scheduler to when every X (1-4) week of the month on a specific day.
We added a right-click context menu for vendors and products in the Product Rules tab.
We added two new options that allow you to kill an applications process before performing an update or skipping the update install if conflicting processes are running.
Added a new checkbox in the "Product Rules" tab "Use a single vendor name (Patch My PC)". This option will publish all updates under a vendor named "Patch My PC" and product named "SCUP Updates". This options will allow a single vendor to be enabled in the Software Update Point "Products" tab, and any new products enabled in the publishing service will show up in the next SCCM sync and won't require additional products to be enabled in the Software Update Point. This option will be enabled during a clean install of the publishing service. If you had a previous version and upgrade, you would need to enable this option and save your settings.
Fixed a proxy password issue. If the password was 16 characters or a multiple of 16x, it wouldn't save correctly in the Settings.xml file.
Initial Release
ScriptRunner now has a new custom variable, %CurrentDir%
This variable may need to be put in double-quotes or the entire parameter may need to be in double quotes depending on the application. Examples of this are below.
Config=”%CurrentDir%\Config.ini”
“Config=%CurrentDir%\Config.ini”
Idea:
Improve logging associated with delayed application publishing
The SSRS report dashboards now include a parameter for Deployed.
Improved catalog parsing when there are a large number of CPU cores on the machine running the publisher.
File Name
Command-line
Download URL
Digest
Scan Configuration Manager Database wizard updated.
Supports Filtering
Can optionally show, and export, applications whose count is zero.
Idea: PATCHMYPC-I-828
General UI improvements such as tooltips, alt-shortcuts, empty field validation.
Fixed an issue where Intune assignments may not set the correct delayed deadline
Fixed an issue where older versions of the ConfigMgr console may receive error: Method not found: ‘Void Microsoft.ConfigurationManagement.ApplicationManagement.MsiInstaller.set_UninstallSetting(Microsoft.ConfigurationManagement.ApplicationManagement.UninstallContentSetting)’.
Note: We still need to add user-based software to the catalog, but the publisher now has support for this so that we can begin adding some user-based software.
Option to not append the republished date tag to republished updates.
Idea: PATCHMYPC-I-876
This is now a configurable checkbox in the advanced tab.
Intune Scan Wizard now has the option to automatically enable Intune Updates based on scan data.
Update the PatchMyPC-ScriptRunner.exe to use the CCM client log directory defined in the registry by default
Check
“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\Logging\@Global”
> LogDirectory, and fallback to “%windir%\ccm\logs”
Idea: PATCHMYPC-I-911
Maximum three retries, with 1 minute in between.
Updated the PowerShell script for Intune applications and updates to improve compatibility with constrained language mode.
Optimized icon resizing for ConfigMgr applications.
MSI based ConfigMgr applications will now have 'No uninstall content' set for the uninstaller, as we directly call msiexec, no content is needed.
SMTP port automatically set to 587 when 'Use TLS' is selected, and to 25 when 'Use TLS' is unselected. The port can still be manually edited to account for any port, but the common port for the protocol is set by default.
Unmatched exit code (2147500037) is considered an execution failure.
The existing selection of VLC will be converted to the EXE version of the application. The MSI can now also be selected and published.
Pre/Post Script form now validates that Pre-Update Script and Post-Update Script exists before allowing you to press OK.
Fixed an issue where ConfigMgr Base Applications were created with a detection script that did not specify a version to search for. All base applications created with **Publisher Version 1.8.4 or newer
(released 2020-07-22)** would always show as detected if any version was installed on the endpoint. The version was not being validated.
The affected detection method would show version 2.2 in the logs, and in the script itself.
Applications created after 2020-07-22 by the Publisher should be deleted and recreated to ensure the proper detection method script is used.
Intune updates use the description in the SDP for the title.
User voice idea
Split the «Delete Intune Application when a new release is published» option to allow to choose the behavior for Apps and Updates independently.
User voice idea
Download timeout is now logged out in minutes and seconds, instead of milliseconds.
Implement log rollover for Intune detection and requirement scripts.
Send an MS Teams message and add a line in the Email report if the server runs low on disk space on the PMPC installation or the Wsus Content drive.
Support for the Contains string operator when searching for an AAD Group.
The Publisher will notify the user if the installation drive is running low on disk space.
The Publisher will notify the user if the Publisher is installed on the Site Server, and the server is not also a Software Update Point.
Tooltips added to buttons on Intune Apps and Intune Updates tabs.
When several files with the same name are found in the Local Content repo, and subdirectories, we try to identify the right one with the expected digest before falling back to downloading.
User voice idea
Add a new known error to assist with identifying and resolving TooManyCategories for WSUS.
Enabled CTRL+F functionality in the Intune tab.
Product download will fallback to the Internet in case of a digest mismatch in the local content repository.
User voice idea
Display third party vendor/product count in the Update Modification Wizard.
Deprecate WSUS v3
We now use a FIPS compliant algorithm when creating Intune applications
Fixed a bug where the 'exclude from autoenrollment' option was unable to be changed on a product when the setting was configured at the vendor level.
Fixed a bug where the publishing service could not publish a postponed application if it contained an HTML escaped character.
Fixed a bug where the Intune Scan Wizard was overwriting the Intune Authentication URL
Fixed an issue where the checkbox in the MSI installer to enable Intune only mode may not be applied after the installation
Fixed an issue where the republish option no longer showed for
"All Products" and Vendor nodes
Fixed an issue where incorrect workstation counts were shown on certain SSRS reports
SCCM Database Scan now has an option to "Auto-enable products as 'Metadata Only' if found, but threshold is not met"
Fixes
Fixed bug where some SSRS report links did not function as expected
Fixed an issue where a customer with an expired Intune only license could get stuck in a message box loop.
Improvements
Enhances the display in the Update modification wizard when there is a lot of updates.
Sort SCCM folders when choosing a folder to move new newly created applications to. UserVoice Idea: Fix sorting in Console Folder Browser
Improvements
Web domains of downloaded icons are listed in the DownloadHistory.csv file.
Added several help links in the UI.
Improved logging for known errors linking to KB articles
Changes
The option to fallback to ConfigMgr package publishing when an application can't be published as an SCCM application has been removed in the UI due to not being needed.
SQL query default timeout is now 90 seconds from 30 seconds.
Removed from the UI the option to generate a CSV file with publishing info. The option is always enabled, and the file path can be configured with the registry setting : HKEY_LOCAL_MACHINE\SOFTWARE\Patch My PC Publishing Service:PublishingHistoryCSVFolder
Adds a new column, UpdateEnabled, to the resulting CSV from the SCCM Scan Database Wizard -
(Idea: PATCHMYPC-I-645)
UI improvements to the Base Install options
Generates a CSV file (PatchMyPC-DownloadHistory.csv) that includes the vendor name, protocol, web domains, and download status for downloaded binaries. (Idea:
Fixes
Fixed an issue where the WSUS Maintenance for unreferenced updates would not return folders when the name is longer than 80 characters
Fixed an issue where file coping during publishing would fail when a file is referenced more than once (e.g., in additional files and pre-command script)
Fixed an issue where adding multiple Intune assignments with customer deployment deadlines may cause the publisher UI to crash
Fixed an issue where double quotes in the command line argument for software updates would not be retained.
Improvements
Adds logging for a new known error when access is denied to the application source.
Improved documentation for different areas of the Publisher UI.
When a TRANSFORMS command is added in the additional arguments, we will automatically add the full relative path at execution based on UserVoice 668
Install times are now expressed as time offset starting from the publishing date when an application is published for the first time
When an Intune application is updated, if assignments are not copied from a previous version, new assignment(s) are created based on the right-click assignment options
Displays a warning message if the Local Content repository path is empty, and the option to look into this directory first is enabled
We made significant performance improvements for our SCCM database scanning for application detection
Microsoft Intune application may fail to be created with error
"An error occurred while processing an Intune application: Unrecognized Guid format."
Log the ApplicationID of the Intune app that is updated instead of the Intune App ID (reported by Jan Ketil Skanke)
We would always log 0 requirements carried from the previous version even if more than 0 requirements have been carried over
PowerShell detection method script wouldn't be signed if the filename contained a single quote
Intune assignments are not always carried during an upgrade
Advanced
Added a new advanced option enable via a registry value
Add the ability to parse the catalog using a sequential method instead of parallel (UseSequentialMethod = 1)
Add email, teams, and logging notifications when an update cannot be revised
Added a more details button in the modify published update wizard that will show important details about updates published to WSUS
Improved success and failed icons for Microsoft Teams alerts
Fixes
Fixed an issue where the right-click option for manage logging may display the correct information
You can now create assignments for Win32 applications in Microsoft Intune
The authority URL for Microsoft Intune will be prepopulated
You can now select a custom code-signing certificate from the computer's personal certificate store. A full WSUS installation is no longer required for code-signing the detection method script used for Intune.
The publishing service can now be installed on Windows 10 (x64) for a Microsoft Intune only setup.
Improvements
Use env variables instead of hard-coded path in PowerShell detection script.
No longer perform WSUS service checks when the WSUS publishing is disabled for Intune only scenarios.
You can now test the SMS Provider connection under SYSTEM-level context
Other fixes and improvements.
Fixes
Bug fixes and other improvements
Fixed an issue where you may receive an error: An error occurred while updating a package in SCCM: OpenDatabase,DatabasePath,OpenMode
Changes
Rename Intune preview to Intune Release Candidate.
You can now change the folder location for the generated CSV file
Improvements
You can now test the SMS Provider connection under SYSTEM-level context
Support to publish applications in other languages than en-US
Minor bugs fixes
You can now configure a custom application name, localized application name, localized application description, and icon
You can now increase the HTTP download timeout
You can now enable your software update point to sync when updates are published when your software update point is on a remote site system.
You can now exclude products at the vendor level from being enabled in automatic scanning
You can now press F4/Shift+F4 keys to go to the next/previous when searching products or vendors
When disabling updates, we will now create a RegKey is it doesn't exist to disable self-updates
Added the ability to start a sync by running the PatchMyPC-Settings.exe with argument /SyncNow (the UI is not displayed)
Log events in the Windows event log (Starting/ending sync, success/fail publishing updates)
Improvements
Add several log entries when sync fails
Add new advanced options to improve SQL queries for large organizations.
Improve the version comparison in the PowerShell detection method script
Fixes
Distribution point groups containing apostrophe were ignored during distribution
Improved the PowerShell detection method scripts to handle invalid DWORD entries better fixing a "Specified cast is not valid." error message
Various bug fixes
You can now specify the subject name when creating a self-signed certificate.
You can now Import/Export settings from the advanced tab.
Improvements
PatchMyPC-ScriptRunner.exe files are updated when SCCM applications are upgraded.
Fixes
Fixed an issue where application detection method scripts may fail on devices with PowerShell version 2. The following output error would be logged to appdiscovery.log
Unexpected token '.0' in expression or statement.
CategoryInfo : ParserError: (.0:String) [], ParseException
FullyQualifiedErrorId : UnexpectedToken
CScriptHandler::DiscoverApp failed (0x87d00327).
Deployment type detection failed with error 0x87d00327.
You can now view applicability rules from the modify published updates wizard.
Fixed an issue where applications may fail to install on Windows 10 when using Latvia language.
Fixed an issue where you may get an email about the license being expired when in trial-mode.
Fixes
Fixed an issue where the detection method script may show invalid signature on the client-side.
MSI based applications will now have the repair command line configured in the deployment type.
Fixes
Fixed an issue where the detection method PowerShell script may not be code-signed if there was more than one certificate in the WSUS certificate store.
Fixed an issue where applications may fallback to the package model when a publishing sync if performed at the same time the SMSProvider DLL's are being registered during a site upgrade.
Fixed an issue where the uninstall command line may be empty after an MSI based product performed an in-place upgrade to a newer version.
If timestamping is disabled for update publishing, the detection method PowerShell script will now not be timestamped
When there is a product enabled that requires a manual content download the product name(s) will be included in the prompt.
Fixes
Fixed an issue where the UI may show not responding for a short period of time on initial open.
Fixed an issue where you may receive a prompt saying some settings are missing when clicking apply when using trial mode when all relevant settings are correct.
Added an option to disable timestamping. We generally do not recommend using this unless there is a specific use case. To disable timestamping you can create a DWORD registry value:: HKEY_LOCAL_MACHINE\SOFTWARE\Patch My PC Publishing Service:DisableTimestamping = 1
Added an option in the About tab to opt-in to the preview channel.
Added subscription level and licensed device count based on feedback in the SCCM slack group.
Improvements
We removed the two columns displaying the distribution point group and description in the base installation options dialog.
Change the error return for 404 download errors.
Changes to improve the performance of the license validation check.
Revisions to packages are now included in email reports.
When using the Scan SCCM for Managed Applications feature, the database server, database name, and connection account details will be retained after a successful query.
Split our the following products to be major version specific to allow more specific selection.
ESET Endpoint Security
ESET File Security
Royal TS
SketchUp
Skype
TeamViewer
Telerik Progress TestStudio Ultimate
VMware Workstation
VMware Workstation Player
VMware Workstation Pro
VirtualBox
WinZip
When a package is created for a 64-bit product, the requirements will be configured on the program to only install on 64-bit operating systems
If a package fails to be created, the distribution attempt to SCCM distribution points will no longer be performed.
Added an option to change the subject name for email notifications
Added an option to include text in the body of the email notifications.
Fixes
Fixed an unhandled exception when you enable base packages when no catalog URL is set.
Fixed an issue where updated installation packages are not added in the email report
Fixed an issue where superseded applications may not publish into SCCM
Fixed an issue where SCCM package creation is malformed when updates are configured to be republished.
Fixed an issue where products are still listed in the SCCM application scan when the Include Products Already Enable in Scan is not checked.
Miscellaneous fixes
Improved the HTML email report format and color
Improved error handling if the WSUSPool or WSUS Service is in a stopped state
When the user triggers a self-upgrade via the about tab, a progress bar is displayed, and the publishing settings UI will reopen after the update.
Fixes
Fixed a bug where the SCCM application scan wrongly displays the Java migration update as being installed
Other minor bug fixes
Improved logging, when there are known publishing error codes, we will now link to any KB articles containing the resolution.
Added option in the "About" tab to "Disable Self-Updates" based on customer feedback.
Added CVE tab to the report
When there is only one CVE, the CVE-ID will be clickable and link to https://cve.mitre.org
We will now retain on previous version PatchMyPC.log and rename it to PatchMyPC.lo_ when the max log size is reached.
If a product doesn't support pre/post update scripts, the option will no longer be visible in the right-click action
Changes
Changed the PatchMyPC.log from 10MB to 2MB
Added the size of the downloaded file in the log file
Improved performance when reading the settings file

Applies to: Patch My PC Cloud
Details the production release history for Patch My PC (PMPC) Cloud, the most recent release being shown first.
Portal
Multiple Domain Support– that allows you to configure multiple Entra ID custom domains for your PMPC Cloud company.
Multi-Language Support improvements – For those apps that provide multi-language installers, we’ve now updated the metadata for those apps in our App Catalog instead of defaulting the language to en-US.
PSADT Branding – A new notification style now in Public Preview that uses Fluent UI dialogs.
Portal
Resolved an issue with Discovery showing incorrectly some apps deployed by Publisher as Unmanaged.
Resolved an issue where if you applied filters in the Events node and close them, when you re-open the filters the applied filters are no longer present.
Intune Apps
Resolved an issue where, for some apps, there was a difference in versions between the UI and the PatchMyPC.xml (cab file).
Resolved an issue when deploying an app and selecting the Skip installation when conflicting processes are in use setting, which was ignored, and the app was installed.
Resolved an issue where if a macOS LoB PKG was created with Install as managed disabled, the deployment failed.
Managed Service Provider
Resolved an issue where Premium subscription features were displayed for MSP license holders.
Resolved an issue where a user invited to a company gets an error when accepting the invitation and creating a new company.
Resolved an issue with App Sets not being shown on the App Sets page.
Migration
Resolved numerous issues as we continue to develop this feature.
Reporting (Advanced/Patch Insights)
Resolved numerous issues as we continue to develop this feature.
No release.
Entra ID Security Groups - The ability to use feature is now generally available (GA).
App Dependencies - The feature is now avialble in Public Preview.
Resolved an issue with the validation for the Additional Argument field of a deployment not working correctly.
Resolved an issue where an error was displayed when a user with the Read-only Admin role enables Pause Updates.
Create a Deployment with No Assignments - has now been released.
Entra ID Security Groups - The ability to use feature is now in Public Preview.
Extra Files - The feature (also known as Deployment configuration files) is now in Public Preview.
Resolved an issue with the portal not auto-refreshing the Status when creating a new deployment.
New Visual Indicator for Public Preview Features – If you have in your PMPC Cloud company, we now show you how many and which Public Preview features you have enabled.
Support for Role Scope Tags - We now support
Ability to enable auto-updates for an app – If an app supports auto-updates, you can now choose whether to enable this behavior.
Script name auto-populated – Now when you now import a script to a deployment, the Script Name field is auto-populated with the script’s name.
Resolved an issue where Webhook notifications were not sent for some Update Rings.
Restriction on M365x Tenants Starting a Trial - We no longer allow customers whose Entra ID domain starts with m365x to start a Patch My PC (PMPC) Cloud trial. Such customers will not see the option to start a PMPC Cloud Trial and will either need to enter a PMPC Cloud license key or activate their license using their on-premises Publisher license key.
Resolved an issue with Custom Apps becoming “stuck” or taking a long time to be created.
Resolved an issue with old versions of apps not being deleted from Update Rings.
Resolved an issue with being unable to connect to Intune after deleting the connection for a linked MSP company.
New service unavailable notification – If one of our regional services is unavailable, you will now see a banner notification informing you of this.
Resolved an issue where enabling email notifications resulted in the first email showing all historical information, not just the relevant notifications.
Resolved an issue with webhook notifications not being received if the payload exceeds 28kb.
Various improvements to the daily update report email.
Resolved an issue with the Install and Update App no assignment type being available incorrectly when deploying a .MSP file.
Resolved an issue with icons not appearing in AppCat after adding an app.
Resolved an issue where the Add Assignment button is unavailable if the Entra group for an existing assignment has been deleted from Entra. We now display an error and force you to remove the assignment in this scenario.
Maximum delay for an Update Ring has been increased to 180 days.
Improved overall
Resolved an issue where the email and webhook notifications were not received after creating a deployment with no assignments.
New .MSP Installer Type added to AppCat – We now support the .msp installer type in AppCat.
New “Read-Only Admin” user role – This new role can view all pages in the portal but cannot make any changes. This role is intended for audit purposes.
New “Tenant Recovery” option – If enabled, prevents a PMPC Company from being recovered using the process. [NOTE: You will need to contact support to get this feature enabled due to the potential consequences of enabling it.]
Warning when changing from Daily Sync Schedule – We now have a new warning when changing your Sync Schedule from Daily as this can affect how Update Rings work.
Update Rings Deployment Summary warns if you are not using a Daily Sync Schedule – When creating or editing a deployment that uses Update Rings, the Deployment Summary popup includes a warning against using anything but a Daily Sync Schedule with Update Rings.
Update Rings now detects the Sync Schedule – If the Sync Schedule is configured to run on anything but a Daily schedule, Update Rings now forces the delay between Update Rings to align with the Sync Schedule.
Resolved an issue with the user’s first name and last name fields not being automatically populated on sign-up.
Resolved the Unable to deploy. Product data was not found error.
Deployments without assignments – You can now create a deployment without assignments [Note: You need to be using the Update Rings Feature currently in Public Preview to be able to use this functionality].
Update Rings can now be updated at the Ring level – You can now update a ring to any available version that is higher than the current version.
Discovery now shows the icon for an app – now shows the relevant icon for each app that’s managed/unmanaged.
Daily Updates Email Report includes newly created Deployments – The daily Updates Report now includes the details of any new deployments created in the previous 24 hours [Note: You need to be using the Update Rings Feature currently in Public Preview to receive the report with these improvements].
Discovery now shows Publisher apps – The Managed tab of now includes apps deployed by our on-premises Publisher.
Recommended default name for the Branding App – We now provide a recommended default name for the branding app, which you can override.
Update Rings [PUBLIC PREVIEW] - The feature of Patch My PC (PMPC) Cloud allows you to deploy apps and updates in a phased manner across your Intune estate.
Increased number of characters for Additional Arguments - The maximum number of characters you enter in this field has been increased to 500.
Resolved truncating issue with App Cat app names – When opened, apps with long names are no longer truncated but are displayed in full on the app’s properties page.
Resolved “No Files Added” bug – After uploading a new version of the app.
Discovery – The feature is now available in Public Preview. This feature lets you see which apps in our App Catalog are installed in your environment, including any Binary Free Apps or Custom Apps you may have added.
Folder installation log now shown – We now show the path to the installation log in the new Installation Logging section of the Summary tab. We currently do not support changing this.
Sync Schedule – GMT is no longer shown in the UI of the to avoid confusion.
Company ID shown during recovery – When you , we now include the company ID as well as the name of any companies you can recover in the Company to Claim dropdown.
Vendor Verbose Logging enabled – Resolved an issue with vendor verbose logging not being enabled by default for IntuneSync.
On Restart Notifications incorrectly configured – Resolved an issue where if the notifications for a deployment are configured for On Restart, the Show All option is actually selected on the dropdown, and not On Restart.
Recover Your Company – We now provide a facility for you to regain access to your company by using the new process.
Latest Version added to app properties – Now when you open an app’s properties, we show the latest version number.
Link to vendor download – When you upload the installer, we now provide a link to the official vendor’s website to ensure you download the most recent and official version.
Notifications – Resolved an issue with emails not being sent for some apps after the daily sync job ran.
Users – Resolved an issue where changing a user’s role resulted in several notification emails being sent instead of one.
Naming Conventions – Resolved an issue where any tag added after a string was not recognized.
Link to product documentation added to the support menu.
Users – The portal now displays a confirmation if you try deleting yourself.
Improved App Icon UI – We now show the supported file types in the UI for the App Icon.
Improved language support - English variants are now exposed. Previously, we only exposed English as a language for apps. We now expose all available variants such as English - Canada, English - United Kingdom, English - United States, etc.
Update-only assignments for user-based apps – You can now create update-only assignments/packages with Intune Apps in the same way as you can with our OnPrem Publisher.
Resolved an issue with Silent Install Parameters not being copied over when adding a new version of an app.
Sync Schedule changed to UTC – To help avoid confusion, the Sync Schedule time is now based on .
Customer Support – Resolved an issue with being unable to edit a timer with less than 4 hours remaining.
Deployments – Resolved an issue with some Custom Apps being stuck with the status of Retrying.
Ability to opt-in to Preview Features – You can now opt-in to automatically gain access to pre-release features we mark as Public Preview.
Customer Support feature re-designed – You can now set a timer to limit the amount of time Patch My Support has access to your environment and the level of access.
Test buttons for Notifications – New buttons to allow you to send test notifications/emails when setting up Notifications to check they are configured correctly.
Allow Available Uninstall – You can now configure a deployment to allow an app installed by the Company Portal to be uninstalled by Intune Apps.
Increased upload limits for pre/post scripts – Previously, the total size of all pre/post scripts for a deployment was limited to 1 MB. This has now been increased to 1 MB per script, with a total size limit of 4 MB.
Deployments – Resolved an issue with the Edit button not being displayed if an app has already been successfully deployed.
Resolved an issue with the MSI Product Code being displayed for a Custom App created with an EXE as the primary installer file.
Improved sorting by column – Columns can be sorted by more headings in various nodes when working in the portal.
Improved user access requests — Users can now enter a message giving more information about why they are requesting access to a company.
Improved access denied flow – Admins can now provide a reason for declining a user's access request.
Revoking Access Management rights warning –
Branding – Resolved an issue where uploading a new logo with the same name as the existing one shows the old logo.
Notifications – Resolved an issue with Teams and Slack notifications cutting off CVE data and not containing release notes.
Update reports – Resolved an issue with the formatting of file sizes on the deployment email report.
Users – Now you cannot remove the Access Management right for the last admin user in your company. This prevents you from locking yourself out of the portal. If you are the last user and there is at least one other account with this right, if you try revoking it from your account, you are prompted to confirm because of the consequences.
Users – The Application Deployment Admin user role has been renamed Intune App Admin.
Naming Conventions - You can now use the new feature to configure custom naming conventions for all deployments created in Intune Apps for Cloud. This allows you to standardize the naming convention across all your Intune deployments.
Deployments – Resolved an issue with two Update-only apps being created in Intune if the first one fails. Now, if an app fails to be created in Intune, we delete it.
Onboarding – Resolved a sign-in issue when a user accepts an invitation.
Resolved an issue with the Naming page not being accessible.
New user role added.
General – Clicking our logo in the top left-hand corner of the portal returns you to the App Catalog and forces a refresh.
App Catalog – If the name of an app is truncated, hovering over it now shows the full name as a tooltip.
Contact Form – Resolved a memory exception error when sending attachments to us through the Contact Form in the portal. You can now send up to 25 MB of attachments when using this form.
Deployments – Resolved issues :
Resolved an issue with the user being able to add the same conflicting process multiple times when creating a Custom App. We now do validation to prevent this.
Contacting Support – You can now modify the From email address when using the form.
Environments node – New button added under the Intune connection.
Licensing – If you already have an active license with us and click Start Trial, we detect this and use your existing license to activate your portal.
Various improvements to notification messages and tooltips to improve readability.
The “Prevent from opening an application while the application is updating” checkbox is no longer checked by default on the Conflicting Processes settings pop-up.
Resolved an issue with the configuration of Conflicting Processes not being honored.
Various other bugs.
Moved to Public Preview.
Reporting (Advanced/Patch Insights)
Moved to Public Preview.
Resolved an issue where clicking Edit to edit a deployed App Set resulted in an error.
Migration
We no longer show apps that are retired in the list of unsupported apps.
Reporting (Advanced/Patch Insights)
Resolved an issue where the Reporting node would disappear at the end of a trial.
On the sync of a new version with Copy Forward enabled, all assignments for the previous version are removed and re-added to the new version.
When a deployment is recreated with Copy Forward disabled, all assignments are deleted.
When a deployment is recreated with Copy Forward enabled, all assignments are copied.
Resolved an issue for macOS deployments where you could add macOS scripts even when uninstall assignments were present, leading to invalid deployment configurations.
Managed Service Provider
Resolved an issue with some App Sets being stuck In Progress.
Intune Apps
Resolved an issue with PSADT scripts being incorrectly available for macOS apps.
Managed Service Provider
Resolved an issue with the Enable PSADT Module checkbox being unavailable when editing an App Set.
Resolved an issue where the Subscription node was still showing in the portal after the user accepted an invite from an MSP.
Migration
Resolved numerous issues as we continue to develop this feature.
Reporting (Advanced/Patch Insights)
Resolved numerous issues as we continue to develop this feature.
Resolved an issue where unsupported Return Codes were shown on the Summary tab of a macOS deployment.
Resolved an issue where the OS Architecture Requirements tool was shown incorrectly for a macOS deployment.
Managed Service Provider
Resolved an issue where, after a child company is unlinked from the parent, it is still listed at the parent.
Resolved an issue where a Validation error is returned for an App Set after a child company that the App Set is targeted to is removed.
Resolved an issue where an error notification was returned when attempting to downgrade from an MSP license, instead of the expected Downgrading from an MSP Plus license is currently not supported notification.
Resolved an issue where the Invitations tab could not be opened when inviting users to an MSP company.
Migration
Resolved numerous issues as we continue to develop this feature.
PSADT
Resolved an issue where the PSADT module was displayed incorrectly for a macOS app, as macOS does not support PSADT.
Managed Service Provider
Resolved an issue when inviting a user failed with An error occurred while processing your request error.
Migration
Resolved numerous issues as we continue to develop this feature.
Resolved an issue with App Sets where if the assignments for an app were set to All Users and All Devices for one company, these same assignments couldn’t be used in different companies for the same deployment.
Migration
Resolved numerous issues as we continue to develop this feature.
Resolved an issue where the Upload app button was not shown after receiving a notification that a new version was available.
Managed Service Provider
Resolved an issue where if an MSP uses an email address that doesn’t exist to send an invite, the event is recorded incorrectly in the Events section.
Resolved an issue with null being added to the Install Parameters field when adding an app to an App Set.
Migration
Resolved numerous issues as we continue to develop this feature.
Resolved numerous issues as we continue to develop this feature.
Resolved an issue with an app being removed from an App Set still showing as being managed.
Migration
Resolved an issue with a .exe ConfigMgr App with an MSI product code detection rule not being detected.
Managed Service Provider
Resolved an issue where Entra ID Groups were not displayed when creating an App Set using an invitation link for a Child Company.
Resolved an issue when adding assignments for Branding with the “All Users” and “All Devices” groups not being shown.
Intune Apps
Editing a Deployment to use Update Rings – Now, when you edit an existing deployment and configure it to use Update Rings, we show the start time for the Update Rings.
Resolved an issue where if a vendor changes an installer’s architecture (e.g., from x86 to Unspecified) in a new revision of their app, the system fails to match existing deployments for that app, which remain stuck on the old version.
Managed Service Provider
Resolved an issue where accepting an MSP invite link did not show the list of Custom Apps relevant to the Child Company.
Managed Service Provider
App Set Details – You can now expand an App Set to see a list of the apps it contains and summary information for each app within the App Set.
Intune Apps
Resolved an issue where attempting to add an assignment to an existing deployment failed with a 400 Bad Request error.
Managed Service Provider
Resolved an issue where adding a Child MSP company to an App Set containing a Custom App resulted in the app being stuck with a status of In Progress on the Child Company.
Resolved an issue where adding a Child MSP company generated a Bad request error.
Resolved an issue with a Discovery data failing to load, sometimes with a TypeError: Failed to fetch error.
Custom Apps
Resolved an issue with Custom Apps getting stuck at stage of 3/3 after editing.
Managed Service Provider
Resolved an issue with assignments not being shown correctly for MSP App Sets.
Resolved an issue where if you had the Remember my Selection checkbox checked on the sign in page, then signed out, and selected a different company to sign into, you were signed into the company that was remembered, not the new one you selected to sign into.
Custom Apps
Resolved an issue with an app’s icon not being displayed in a webhook when the deployment of a Custom App is updated via the Sync Schedule.
Intune Apps
Resolved an issue when running Discovery for a new PMPC Cloud Company generating an error, which was resolved by clicking Refresh.
Resolved an issue with the sorting of apps in Discovery not working correctly.
Resolved an issue with excluding an Entra ID group from Branding now working.
Managed Service Provider
Resolved an issue with adding a scripts and arguments to an MSP App Sets not being saved, as when you edited the App Set, the script and it’s arguments were missing.
Install Parameters Additional Argument
Silent Install Parameters
Additional Silent Uninstall Parameters
Custom Apps
Version number replaced with “%” – Now, when you add a Primary Install File that is an MSI, when populating the various properties, if we detect a version number in the Apps & Features Name field, we replace it with a "%".
Resolved an issue with a Custom Apps icon not being shown in a webhook when its deployment is updated via Sync Schedule.
Managed Service Provider
Resolved an issue with an MSP not being able to unlink a child customer if their license had expired.
New default variant logic – We’ve now replaced our existing language-only priority when creating a deployment with logic based on language, installation context, architecture, and installer type.
Resolved an issue with Exclude filters configured on a deployment actually being applied as an Include filter.
Intune Apps
Resolved an issue with Scope Tags manually added in Intune not being copied forward.
New Update rings start time dropdown – Previously, when creating a deployment, on the Assignments page, after clicking Enable Update Rings you had the choice of choosing to create either Delayed or Immediate rings. We’ve now moved the choices under a new Update rings start time dropdown, recommending Delayed and including tooltips to help guide you.
Resolved an issue with two deployments being created in Intune after a deployment with No Assignments is recreated.
Various bugs squashed to resolve issues with deployments getting stuck.
Resolved an issue with failed deployments not being shown in the Updates Report.
&Resolved an issue with email addresses being displayed incorrectly when a deployment has a large number of update rings.
Resolved an issue when uploading extra files with the same name but in different folders, the UI didn’t process the folder structure and instead uploaded all of the files as independent files.
Native Detection Rules – Patch My PC (PMPC) Cloud deployments now support Native Detection Rules.
Pre/Post Scripts now support Arguments – Our Pre and Post Scripts now support additional arguments.
New “Product Docs” and “Release Notes” options added to the support menu – Now when you click the Support Menu (?) you’ll see links to both the PMPC Cloud Product Docs and Release Notes to help you find the information you need to work with and keep up-to-date on what we’re doing with PMPC Cloud.
Changing certain settings on a deployment now warns you we are resetting other values – Now if you change settings such as the installer type, architecture or installation context, you’ll be warned that doing so will reset all configurations from the other tabs because some settings are only available for specific options.
Resolved an issue with a Reload site prompt being displayed in error when saving a Custom App.
Resolved an issue when uploading Extra Files using the Add Folder option, where if multiple files exist in any subfolder and they have the same hash, you see Error File with the same hash already exists.
You can no longer add an ESP Profile containing 100 or more apps to a deployment.
If you and a single Update Only assignment to a deployment configured to use ESP Profiles, the Configurations tab is marked with a red “X” to indicate there is an issue.
Improved retry mechanism for deployments
Resolved an issue with a user assigned the Custom App Admin role receiving a Validation Error when logging into an MSP Customer.
Prevent an app deployment from being deleted from a parent MSP company if it is deployed at any child companies.
Resolved an issue with Custom Apps being unavailable in the App Catalog with users assigned the Custom Apps Admin role.
Context Sensitive Searching is now supported in Scope Tags – You can now type in the Profile Name field and we’ll automatically return a list of matching Scope Tags.
Resolved an issue with Events not being written when pausing a deployment.
Resolved an issue where if the EnforcedUninstallArgument was saved in the App Catalog, it was not used when creating an uninstall in a deployment
Resolved an issue with not being able to upload extra files with no name and just an extension.
Deployment method icon shown in Discovery – When you view the Managed tab of Discovery, we show the method used to deploy the app i.e. PMPC Cloud, on-premises Publisher, or both.
Cooldown Timer for Company Recovery – Recovering a company is now limited to three attempts every 12 hours.
Search – General improvements to search.
Sync Schedule – The new Sync Schedule feature allows you to set a different time and frequency for the sync job to run.
when editing a deployment, any required assignments with an availability date set to ASAP are not modified until the next day at 12 AM.
Deployment Filters – When adding a deployment filter to an app deployment, we now only show filters for the Windows 10 and later platform, instead of all filters.
Various improvements to notification messages and tooltips to improve readability.
Primary buttons in the UI re-designed based on user feedback.
Applies to: Patch My PC Publisher
Details the production release history for preview versions of Patch My PC (PMPC) Publisher, the most recent release being shown first.
Update the way that Scriptrunner executes PowerShell scripts to improve compatibility with WDAC.
Optimize the payload sent up to Patch My PC Cloud for Migration.
In some cases, the in-memory instance of settings would become corrupted. Restarting the service would resolve the issue.
This resolves issues with syncing Intune products. The bug showed in several ways, but the log lines include an "Object reference not set to an instance of an object"
Fixed a bug where the Preview version of the Publisher would not install if the WSUS feature was not installed.
WSUS Updates can no longer be enabled when no connection to WSUS is available.
In ConfigMgr, some OS requirements instances did not have a CI_UniqueId for some customers. This caused ConfigMgr applications to fail to create.
Fixed a bug where processing an MSI would extract the MSI installer icons to C:\Temp\Icon.ico.
Ensure Scriptrunner only deletes the desktop shortcut if requested.
The Publisher allowed you to save an SMS Provider configuration where the SMS Provider was the local machine, and credentials were provided. You cannot use credentials to connect to a local machine via WMI.
Performing a full resync of Migration data from Patch My PC Cloud would cause Publisher's service to crash unexpectedly.
Fixed a bug causing ConfigMgr console folders to fail to create from within the Publisher UI.
Fixed a bug where apps would have assignments be listed multiple times when opening DO priority editor with multiple apps selected.
Publisher would try to connect to WSUS if Publishing WSUS Updates was Disabled.
Fixed the URL for some of the More Info links on the Advanced Tab.
The copy button now shows as expected in the Intune Updates tab when there are no WSUS Updates selected.
The Publisher will now correctly query the configured SMS Provider, with credentials if provided, when retrieving the list of available SMS Providers.
Added validation back to Advanced Tab folder fields.
Fixed a bug where installing the latest Publisher preview build, 2.1.50.2, would fail when WSUS was not installed on the device - This would affect Intune only and ConfigMgr only customers.
Azure secret expiration alerts now display the date, time, and timezone.
The Manage Conflicting Process branding banner is handled more consistently during a ConfigMgr application sync, with the logo updating for each application if it has changed.
Validation on the Manage Conflicting Processes globalization form has been enhanced.
Right-click options no longer appear when interacting with an empty All Custom Products treeview node, as no actions are applicable.
The Migration feature no longer extracts the MSI installer icon to C:\Temp\Icon.ico.
Connecting to the cloud or enabling migration without a configured SMS Provider no longer causes a crash.
Improved how Publisher handles multiple ScopeIds when querying SMS_Application.CI_UniqueID
Improved how Publisher handles updating flags for things like Republish and SelectiveSync to ensure that settings.xml does not get overwritten / reset to default.
Updated CVE links in Publisher reports to link to the new CVE website,
Improve how selective sync handles selections at the vendor and All Vendors level.
Fixed a bug where Publisher would fail to create a ConfigMgr app if the app had previously been deleted but not fully cleaned up by ConfigMgr.
Fixed a bug where Publisher would still perform a sync if the license had expired in some scenarios.
Fixed a bug where sorting by Created date in the Intune Filters view did not work.
Fixed a bug that caused the Intune App Manager window to hang when editing ESP assignments.
Improved column header names in Intune Scan CSV export to match Intune Scan Wizard headers.
Improved publisher logging for Migration feature to be clearer which application is currently being processed.
Improved English in Pause Product Updates popup.
Added additional event handler for Migration to allow full resync to be initiated from Cloud.
Fixed a bug where certain columns in the Intune App Manager window were not read-only.
Fixed a bug where Migration SignalR hub was not correctly initialized in Migration Helper causing Publisher to not correctly process metadata for ConfigMgr apps
Fixed a bug where sorting by Date in the Intune Application Manager window would provide inconsistent results with large datasets
Fixed a bug which caused the Publisher to error when copying ConfigMgr applications. This resolves the error 'Uninstall Content not found in Contents collection.'
Resync the list of applications when a user clicks Apply or Sync Now.
Improved handling of missing v_Add_Remove_Programs ConfigMgr view in the ConfigMgr Scan Wizard.
Add an additional SHA1 column that can be added to the Show Package Details window.
Improved logging to be clearer when settings.xml is read or write-locked for varying operations.
Fixed an error relating to default language selection in Manage Conflicting Processes.
Fixed a bug where the column header selection menu would not show for the Webhook list in the Alerts tab.
Fixing UI bug where user couldn't save webhooks without unselecting one of the scope items.
Fixed a bug causing inconsistent column widths for Teams webhook notifications.
Fixed a bug where the list of Non-Migratable Reasons was not correctly initialized, causing the error list sent to the Cloud to be empty.
Fixed a bug where additional files, folders, and Patch My PC defined pre/post-scripts were not processed when updating existing ConfigMgr applications.
Fixed a bug where null objects in Migration metadata were not correctly handled.
Fixed a bug where some Migration file errors were not properly caught and handled.
Added better error reporting for Migration feature when processing ConfigMgr applications.
Enabling publisher to allow users to override win32 app options for intune apps and intune updates.
Updated the process for saving logs to use a SaveAs to allow users to customize the location and filename of the saved logs.
Enhanced the notifications to include included/excluded status.
Fixed a bug where detection scripts some times got stuck processing on ARM devices.
Fixed a bug where publisher did not account for customer publisher license update ring being empty.
Fixed an issue where Selective Sync (Publish Now) would not take into account postponed configmgr app updates, causing all postponed app updates to be processed regardless of Selective Sync enablement.
Fixed a bug where Publisher would leave behind files from older versions of an application.
Fixed a bug that caused ConfigMgr applications to fail to publish if the Publisher does not have permission to read device collection information.
When enabling Migration in Publisher, send ConfigMgr ScopeId to cloud.
Added validation to Publisher to ensure apps with over 16MB of metadata only have top level data sent to cloud for migration. (Content will not be hashed and stored)
Improved new product selection filters performance.
If an application being processed for Migration has more than 1000 files, mark it as not supported as Patch My PC Cloud has a limit of 1000 files per deployment.
Fixed a bug where settings could not be saved if product selection filter was active.
Fixed issue where Migration log file would not incremement in whole numbers. (e.g. 0.1 > 0.2, instead of 1 > 2)
Fixed an issue where ConfigMgr apps could not be published if the device count could not be read from ConfigMgr.
Fixed an issue where UI anchors were not set correctly on new icons, causing them to move around the UI.
Add support for ECDSA code signing certificates.
Add a filter button to only show products that are selected in the Publishers UI.
Trigger search in Entra ID Group Search window when pressing Enter key.
Present a warning when importing a code signing certificate if ConfigMgr is set to automatically manage your code signing certificate.
Improve performance when Publisher is processing ConfigMgr apps for migration.
Fixed issue where ScriptRunner was not correctly appending MSI and MSP installers with /qn (Introduced in Preview release 2.1.36.80)
Migration from ConfigMgr to Patch My PC Cloud.
Read only for Enterprise+ customers.
Read/Write for Enterprise Premium customers.
Add a progress bar to the Publisher UI. It will display the current application or update being processed.
Ensure the scrollbar on the Intune application scan wizard only shows when needed.
Improve the logging of PowerShell-based detection and requirement script signing.
On new installs the PatchMyPC.log file is stored in the Logs subfolder of the installation directory.
Write the name of the account used to run PatchMyPCService to the publishers log file.
Fixed a bug that caused to fail to close running applications in some scenarios.
Fixed the URL for the Patch My PC logo in webhook alerts.
Fixed a bug that would allow a configuration of maximum application runtime that conflicted with the Manage Conflicting Process notification runtime.
Fixed a bug that caused the filtering of Intune groups to hang the UI
Add an to set the timeout for Intune reports. The default value is five minutes.
Update tooltips in the Publisher UI for Manage Conflicting Process timeouts to reflect Intune changes.
If the code signing certificate is not found, then WSUS updates will not process.
If the code signing certificate is not found and ConfigMgr detection script code signing is enabled, then ConfigMgr apps will not process.
Fixed a bug where the Publisher may select the incorrect SMS_Content instance in some cases when searching for a previous ConfigMgr application.
This fix addresses the alert “Unable to process <Application Name>. PackageId… does not find an application with a matching content source path…”
Refer to this for more information.
Fixed a bug that caused customers to see an error message if ScriptRunner tries to display a notification while Focus Assist is enabled.
When processing a ConfigMgr app, the Publisher will validate that the PackageId found in a package.xml maps to an application deployment type with a matching content source path.
If a ConfigMgr application copy fails, the left-behind content is also removed.
Fixed a bug that caused the MCP User Notification Timeout not to be translated from minutes to seconds when written to package.xml. The result is a notification being open for 5 seconds instead of 300 seconds, for example.
Note: To fix existing apps or updates with this issue .
Fixed a bug that resulted in an error when attempting to save a MCP User Notification Timeout Setting.
Allow a maximum run time of 1440 minutes for Manage Conflicting Processes for Intune.
Add the user name, user domain, device name, session ID and Windows OS version to the PatchMyPC-Sriptrunner.log.
Collect additional information regarding certificate validation failures.
Add Japanese localization text for Manage Conflicting Processes.
Fixed a bug that caused some right-click options, such as setting an update to metadata only, to take a long time to apply when set at the ‘All Products’ level.
Fixed a bug that caused the Publisher to fail to load the complete list of selected products from settings.
Fixed a bug causing the Publisher to fail to process selections from the CVE Import Wizard.
Fixed a bug that caused the treeview searchbox not to retain the previous search text.
Scriptrunner will now expand environment variables provided in custom command line arguments and pre-post script arguments. Additionally the below variables are available.
%PRODUCTNAME%
%VERSION%
%VENDORNAME%
The search functionality in the product treeviews now consider custom applications. Previously the list of custom products would not be included in the search.
Improved logging during a Publisher synchronization for products that are marked by Patch My PC.
Update some labels and logging to be in line with the latest terminology used in Intune.
The Update ID and Update Title are now written to the PatchMyPC-Scriptrunner log file.
Fixed a bug that caused the service not to start if no settings.xml file existed.
This only impacted preview builds and did not ship to production.
Fixed a bug where the metadata of the settings backup CAB file was using absolute paths, making the CAB appear empty when viewed through Windows explorer.
Support applications in the catalog that download a zip file.
Idea:
Note: Additional backend and procedural changes are needed before this will be used. The Publisher can consume a catalog with software that downloads a zip file. We will not add any products like this until Q1-Q2 2025.
Improve how the Publisher reads and writes settings.
Prevent the Publisher from overwriting user setting changes while a sync is happening. Previously, if a user was in the UI and clicked save while a sync was running, the user’s changes could be lost.
Prevent the Publisher from losing Intune configuration due to an abandoned mutex.
If found, the ‘Collect Logs’ button will now include the WSUS softwaredistribution.log.
Fixed a bug where Graph queries would fail if they contained a date-time filter and the machine running the Publisher had the OS set to specific cultures.
Fixed a bug where a ‘BaseInstallOnlyNotForUpdating_’ prefix would appear when using the %OriginalName% variable.
Fixed a bug where an invalid logging path was allowed, causing the Publisher not to log anything to disk.
Fixed a bug where canceling out of the Dynamic Assignments form would still apply the settings.
Revert changes in Scriptrunner for the execution of PowerShell scripts. The scripts will be called using the -File parameter.
The changes that improve WDAC support will be re-evaluated for a future release.
Note: Products published with version 2.1.28.6 Scriptrunner may not correctly execute PowerShell scripts with arguments.
Revert the changes for translating Manage Conflicting Process notifications by default. We are returning to the original behavior. It will not be translated if the customer does not include a language in their configuration.
The Win32AppId is now included in the PatchMyPC-PublishingHistory.csv file.
Improved the handling of signed scripts when publishing. Sometimes, the Publisher would fail to replace a file and throw an exception. We now ensure the destination file is deleted before moving in the updated file.
Scriptrunner now calls PowerShell scripts without using the -File parameter. This improves compatibility in environments that use WDAC.
Intune Updates will now have the icon for the product associated with them.
If the customer does not provide translations for a given language and this language is pre-translated by Patch My PC, we use those strings when we display the UI notification for .
This results in the default behavior of the notifications being translated to the locale of the device if Patch My PC provides a translation.
Fixed a bug that caused the synchronization to stop if a tenant failed authentication. This impacted Publisher with an MSP license and a multi-tenant setup.
Fixed a discrepancy between the PowerShell detection scripts and the ScriptRunner detection logic.
Fixed a bug with the filtering options for webhook notifications. The notifications should now be correctly filtered when the summary option and scope are set. For example, ‘Send alerts as each product is published…’ is unchecked, and only ‘Include Intune update notifications’ is checked.
Add support for passing additional headers when downloading binaries. This is metadata maintained by Patch My PC.
Update Intune detection to account for registry detection checking for a nonexistent property. We now allow a NotEquals check for a property that might not exist. Previously, this would cause an unhandled exception.
Added support for Microsoft Teams Workflows as a new webhook provider option. With the announced , we now support the new Workflow options. Our Teams notifications have been updated with new templates.
Configured are updated on sync for ConfigMgr applications, Intune applications, and Intune updates. If there is a mismatch between the settings in the Publisher and the published application, then the return codes from the settings will be applied. It is no longer necessary to republish a product to update the return codes.
Fix a bug that caused republishing a custom ConfigMgr application with additional files to fail in some scenarios.
Fixed a bug where the return codes in settings could be duplicated if the treeview was refreshed, or you switch tenants in a multi-tenant setup.
Manage return codes
Idea:
Use a temporary staging directory for binary downloads when processing ConfigMgr applications
Improved handling of the cloud connection.
Improved how ConfigMgr content is resolved to ensure we choose non-retained applications if present.
The tooltip and icon for Manage Conflicting Processes suggested configurations are now more contextual.
Fixed a bug that caused the ‘Prevent the end-user from opening an application while the application is updating’ feature to not work for ConfigMgr or Intune applications in some instances.
Implement coexistence
Coexistence ensures the customer is aware when a product is already managed by Intune Apps for Patch My PC Cloud.
Fixed a bug that caused a circular reference when processing Intune dependency relationships with greater than 2 layers.
Fixed a bug that caused ConfigMgr applications to be copied for retention even if the current version fails to download.
Ensure proper wildcard support for ? in detection.
Support for ‘Allow available uninstall’ in Intune
Idea:
Improve our regex usage in the detection of applications published by Patch My PC.
The regex string is now stored in base64 in the PowerShell script to prevent Intune from clobbering UTF8 characters.
Fixed a bug that caused custom applications with a main file larger than 2GB to fail to process.
It is now possible to adjust the chunk size used for uploading chunks to Azure. It can be .
PowerShell detection scripts no longer call whoami. This resolves issues where the PATH environment variable may have conflicting whoami processes.
The ‘‘ right-click option can be used to generate new scripts with this change. Otherwise, products will have the script updated when a new version is released.
Product selections are stored and matched based on a product Id
A message box will appear when a ‘
Fixed a bug that caused a null reference exception if a recommended pre script, and a recommended post script were configured on a product.
The configured proxy will be used to get an access token during cloud connection creation.
Disconnecting from the cloud tab did not save to settings.
When creating the cloud connection in the Publisher, the System Default browser will now be used.
If needed, the embedded web browser can still be used with a .
The ‘‘ button now collects all PowerShell detection scripts modified within the last 7 days. The scripts are renamed to have a .txt extension before being added to the zip file.
Icons in the product treeview now indicate if the product requires local content, or is configured to skip the install if running by default.
Cloud features were not using the configured proxy. The proxy configured in the Publisher will now be used.
Use less memory when uploading .intunewin files to Intune.
Improve the user experience when the ConfigApi is not available
The UI can now start without the ConfigApi being available. A popup message will still appear indicating it cannot be reached.
When this is not available, the cloud features of the Publisher will be disabled.
Fixed a bug that caused some right-click options to not clear their state as expected for custom apps.
Editing Manage Conflicting Process options did not light up the Apply button.
Fixed a bug that caused the Publisher to fail to retry when uploading chunks to Azure.
Fixed a bug where a custom application download may compare hash against an older version of the custom application’s hash.
Improve how the list of custom products is queried from the cloud.
Improve the cloud connection flow to account for the EU region.
Various typo corrections in the UI and in the log.
Improve logging for retained ConfigMgr applications.
Fixed a bug that made connecting to an EU Patch My PC cloud customer inconsistent.
Fixed a bug causing the copy between tab options not to work as expected when custom applications are configured.
Fixed a bug where ESP associations would copy between the Intune Apps and Intune Updates tab.
Improved how .intunewin files are handled to ensure we can process large files.
Implement an attempted reconnect when a WMI query fails against the SMS provider.
Improved scriptrunner logic for finding uninstall strings. DisplayVersion will now have any "-" or "_" replaced by a "." when searching for uninstall strings. This matches the behavior of our script based detection.
Fixed a bug that caused a Null Reference Exception when exiting the configuration in the Intune apps or Intune updates tab.
Fixed a bug that caused the for ConfigMgr applications to be overwritten during a sync in some cases.
Fixed a bug where the authorization token can expire when connecting to Custom Apps, requiring a service restart.
Fixed a bug where Right-Click selections for "All Products" on the "Intune Apps" tab would be lost when custom apps was enabled.
Ability to create Custom App updates and base installs
Idea:
The feature is in public preview.
Update the default login authority for Intune. It is now
This will not affect existing Intune configurations. It is only a change to the defaults for a new connection.
Fix logging during the creation of Intune products when local content lookup fails. The Publisher would incorrectly log that the existing application would be deleted.
Fixed a bug causing Enforced Uninstall Arguments to be ignored for ConfigMgr apps. This resulted in some ConfigMgr apps being created with an uninstall that may not work as expected. The next sync after the Publisher is updated will fix these products’ uninstall configuration.
The connection name is now required in the Cloud tab.
Add support for configuring Win32 application max runtime in minutes
*** Report lines have been updated.
As the catalog grows and the number of syncing products increases, our *** report line has gotten too long! CMTrace does not parse the line, and it will not show it. To prevent this, we have split up the report line into one line per type. Below is an example.
Implement certificate pinning. All requests to Patch My PC domains will have the certificate validated.
Fixed a bug that caused a new install of Patch My PC Publisher to be in ‘Intune Only Mode’ regardless of the checkbox state.
Servers are no longer included in Intune device counts.
Resolved a race condition which caused the additional webhook filtering options to be unavailable in some instances.
Improved download engine logging to include the URL when the download fails. This was a regression that is now resolved.
Support detecting software that translates DisplayName
Idea:
Implement Publish Now for Custom Apps
Improve some popup notifications to direct the user to the correct tab.
Improve cleanup during service shutdown.
Fixed a dead ‘More Info’ link for WSUS certificate management.
Fixed a bug causing dependencies to be removed from an Intune Win32 application when republishing.
Fixed a bug where publish now and delayed ConfigMgr apps did not work as expected.
OK button has been changed to ‘Save and Close’
Open to feedback on this change. We have received a fair number of reports that it is unclear the ‘OK’ button will close the UI.
Fixed a bug where multiple threads could access some components of settings at the same time, causing a race condition.
Fixed a bug where the 'Change Visibility' option for WSUS updates would not work if the WSUS DB is called something other than SUSDB.
Improve cleanup of files during the synchronization of Intune.
Updated the “Enabled” header of CSV exports in scan wizards to be less specific.
Fixed a bug that caused the right-click menu at the root to sometimes not display correctly.
Fixed a bug with ‘Selective Sync’ where Intune Apps and Intune Updates were swapped
This would not cause the wrong thing to be published, but it might cause something to not be published at all during a selective sync.
Sync only selected apps/updates during a sync
Idea:
Implement a new download engine across all components.
Detection method improvements.
Support parsing version numbers that use – or _ instead of .
Improved logging regarding installer downloads and sourcing.
On the ConfigMgr Apps tab, if the option «Add the executable name in the deployment type’s install behavior» is enabled, the Manage Conflicting Process is automatically enabled to kill processes.
Fix crash when sorting some columns in the .
Fixed a bug that would cause a republished Intune product to have the content for the latest version, and the metadata for version n-1.
This would occur if the republish flag is set, and there is new version of the application in the catalog.
Update Patch My PC TOS.
Allow the management of Delivery Optimization configuration for Intune assignments.
Idea:
Note: Existing DO configuration on an assignment will also carry forward now when a new version of the software is Published.
The now has some multi-select bulk options.
Fixed a bug where the wrong ID property was shown in the ‘‘ tool for the update ID.
Fixed a bug where Manage Conflicting Processes may be enabled if is enabled. This is unexpected behavior that will no longer occur.
Update the Intune to use the for both the collection of applications, as well as application extended info. This prevents a 429 when retrieving the data.
Updated Publisher to reflect changes in Graph API schema. This should resolve issues with the .
Updated the to use . This will prevent the Publisher from getting a 429 return code when scanning for discovered applications.
The product treeviews are now sorted by Vendor and then Product Name automatically.
Fixed a bug where the sorting of products in the email report was in reverse alphabetical order.
Updated some graph calls to use a smaller page size. This reduces the chance of receiving a 429 or 503 response from graph.
The page size is configurable from 1-999 in the Advanced tab of the Publisher.
Add support for .cmd files in pre/post-scripts.
Idea:
The Update ID is now an available column in the tool.
Fixed a bug where a ConfigMgr application’s supersedence relationship was lost when the application was upgraded in place.
Adjusted log levels of some lines to assist with troubleshooting.
Update context menu items to reflect new labels in ConfigMgr for featured apps.
Update several labels in the UI to be more clear on their functionality.
The ability to set ‘Prevent the end-user from opening an application while the application is updating’ is now only allowed at the per-product level. This setting is only needed in specific scenarios, and enabling it for all products can be problematic.
Fixed a bug where Intune device counts are not reporting properly.
Add support for creating an Available assignment for All Devices. This was previously not supported by Intune. Support has been added, and the Patch My PC UI now allows it as well.
Added the option to import CAB files when importing tenants.
Fixed a bug where an exception may occur if deleting a large number of Intune Applications using the Intune Application Manager Utility
Fixed a bug where some data exports would result in malformed date time strings. This occurred if a culture used the same character for the number group separator and for time parts.
Fixed a bug where ConfigMgr detection script logging did not use an invariant date-time format. This could cause CMTrace to fail to parse the logs.
Fixed a bug where Manage Conflicting Process logging did not use an invariant date-time format. This could cause CMTrace to fail to parse the logs.
Email and Webhook notifications now include information about delayed ConfigMgr applications during each sync.
Idea:
Email and Webhook notifications are now sent when a delayed ConfigMgr application fails to download. Previously a notification would only happen if the Publishing failed after the delay.
Fixed a bug where PowerShell scripts for Intune were created with an encoding of UTF8 with BOM. They are now encoded as UTF8 without BOM, which is the recommended encoding based on .
Fixed a bug where a malformed ConfigMgr folder item (SMS_ObjectContainerItem) would be created the first time the Publisher moved a ConfigMgr application. The result was a folder that could never be deleted.
Fixed a bug where having a product marked with and a or set would cause invalid XML to be generated.
Intune option added to ‘Copy requirements’ for Intune products. This can be configured globally, per vendor, or per product.
Idea:
Recreate Detection right-click option for Intune
Idea:
If a PMPC-defined pre or post-script is missing from the content source for ConfigMgr applications then the Publisher will redownload it during a sync, or republish.
Fixed a bug where non-Windows devices may show up in the drill-in.
Fixed a bug where republishing an Intune product would cause the application to be deleted from Intune if retention was also enabled and set to zero.
Fixed a bug where the Publisher would not check the WSUS certificate validity unless at least one WSUS update was selected.
Fixed a bug where the requirements for Workstation or Server OS would not be set for postponed ConfigMgr applications.
Enable Right-Click Options for MSP based updates
Idea:
Improved the content of alerts when additional files or folders are missing when Publishing a product
The ‘Configure SMS Provider connection’ button is no longer highlighted if unconfigured in WSUS Standalone Mode.
Improved the logging for SMTP initialization and error handling.
All titles in the email report now link to release notes if available.
Fixed a bug where the Publisher would not add a PMPC-defined script to an existing product.
Fixed a bug where Scriptrunner did not append the provided Silent Uninstall Arguments to MSI uninstalls.
Fixed a bug where some UI listviews had a broken filter.
Fixed a bug where Manage Conflicting Process window may be offset from the bottom right corner.
Improved how running processes are enumerated for making the popup more responsive.
Implemented a ‘retry’ in the event of failure for many critical interactions with Azure via Microsoft Graph.
The Publisher will delete files from the download cache if there is a hash-mismatch for the file. This makes the root cause of Publishing failure easier to identify.
Fixed a bug where the registry option would cause the ConfigMgr database scan to never perform a query.
Fixed a bug where a failure to download an icon would cause a product to fail to publish.
Add the ability to limit the number of threads used during the upload of Intune packages.
Adding more logging around proxy configuration and failures.
Scriptrunner will now log out a comma-separated list of all public desktop shortcuts if the installing product is configured to delete desktop shortcuts.
Fixed a bug where some network operations would not use the configured proxy.
Fixed a bug where the code signing of ConfigMgr detection scripts may fail to validate the digital signature on the endpoint.
Added a filter for Superseded to the .
Adjusted some log levels and log text to be clearer.
Added additional logging when the proxy settings are loaded in the event of a failure.
Added the option to customize the number of parallel threads to use when performing an upload of an intunewin file to Intune.
Fixed a bug where whitespace at the beginning or end of the Organization Name for would cause the property to fail to parse correctly.
Fixed a bug where old setting backups would not rename properly, causing an error during settings backup in some cases.
Added a missing tooltip to the ConfigMgr scan wizard button in the ConfigMgr tab.
Added clarity to the ‘copy’ button tooltips in the Publisher.
Fixed a bug where All Devices and All Users assignments created in the Manage Assignments UI could be created with the wrong intent.
Note: If you created any new assignments in the Manage Assignment UI while on build 2.1.6.35 please check that they are correctly configured.
All Devices assignments default to ‘Uninstall’ intent.
All Users assignments default to ‘Required’ intent.
Allow the same Azure group to be assigned multiple times for Intune assignments. This allows a group to be used as both an include, and an exclude.
Idea:
Pass variables into pre and post-scripts.
Note: the %ProductName% and %VendorName% variables are Base64 encoded when they are passed to the pre and post-scripts. It will need to be decoded. Patch My PC will provide a sample PowerShell snippet to decode the resulting parameter.
Improved child-form handling in some cases, so they now open in the center of the parent form.
Multi-selection views, such as selecting application scopes or categories, now use a consistent form that allows filtering.
Fixed a bug where the wrong URL was used for Microsoft Graph batch requests in some cases.
Fixed a bug where the buttons in Managed Conflicting Process may not fit the text in some translations.
Fixed a bug where the ConfigMgr app options window is not resizable.
Fixed a bug where the Manage Conflicting Process Organization Name would not be set when a ConfigMgr application was revised.
Intune package extraction
It is now an option to store the encryption keys used to create the Intune package files (.intunewin). This is configurable in the Advanced tab of the Publisher.
With the keys stored, you can use the to download and extract the content of the Patch My PC published Intune applications and updates.
Webhooks can now be granularly scoped based on several criteria listed below. (Requires Enterprise+)
Intune synchronizations will now happen in parallel for multi-tenancy. Up to 20 tenants synchronize at a time for this build.
Improve the speed of uploading packages to Intune.
Refactor email report template.
The background is now transparent so that it will match the theme of the email client it is opened in.
Fixed a bug where the settings backups were stored in a non-sortable format. This bug was introduced in preview 2.1.6.1.
Fixed a bug where the filters were not applied in the scan wizards when filtering the data. This bug was introduced in preview 2.1.6.1.
Fixed a bug where the ConfigMgr database scan may throw an exception due to a malformed query. This bug was introduced in preview 2.1.6.1.
Fixed a bug where the logging option to copy failed logs to a share was not retained. This bug was introduced in preview 2.1.6.1.
ConfigMgr and Intune scan wizard allow drill into list of devices where the software was detected
Idea:
Ability to enforce timestamping, making it a terminating error for the publishing of a product
Idea:
When exceptions are thrown in the Manage Assignments form they are now handled better by presenting a popup with the exception and a link to related documentation.
Main form accessibility has been improved.
Accessibility names are assigned to many controls to provide context
Alt-codes are added to most buttons that did not have them before
Fixed a bug that caused the Paused products section in the email alert to be empty.
Fixed a bug where we would not put back the version on retained applications if the configuration was set to remove the version from application names and update existing application metadata.
Fixed a bug in the tool that caused an unhandled exception if you attempt to edit an assignment with a deadline in the past.
Setting or at the vendor level will now display the list of affected products similar to when these selections are made at the All Products level.
Updated language in the Update Republish message box to reflect new UI changes for Advanced WSUS options.
Fixed a bug where a sync may run multiple times back to back.
Fixed a bug where Intune authentication did not use the configured proxy.
Fixed a bug where an Intune application or update would not update the code signing configuration of the detection script. Republishing an Intune application or update will now update the detection and requirement scripts and code signing configuration as needed.
Adding German and Dutch translations to
Intune Filter viewing and configuration is now available in all instances of managing Intune Win32 assignments in the Publisher.
All setting backups are now in a .CAB format. The import setting option now allows for .XML or .CAB import to ensure we support importing older setting files.
Fixed a bug where scriptrunner may fail to find the uninstall string in the registry for some products.
Fixed a bug where scriptrunner may fail to validate an installation after the installer completes causing a 3-minute delay after the installation completes.
Fixed a bug where does not account for postponed binaries. If there is an existing postponed binary it will publish even if a pause is set.
Fixed a bug where some publishing summarization info was miscounted in the PatchMyPC.log file.
Include server name in Publisher upgrade notification email and Teams/Slack notification.
Idea:
The right-click option now removes shortcuts from the user desktop for user-based applications.
The SMS provider button is now highlighted in the WSUS options if the SMS provider is not configured.
Fixed a bug where an empty Intune tenant is written to settings causing errors when the Publisher attempts to query the invalid tenant.
Fixed the layout of the form.
Fixed a bug where we may fail to query for Distribution Point groups if the name or description is DBNull instead of an empty string.
Fixed a bug where the ConfigMgr SUP sync would not start after a Patch My PC Sync if only updates using local content were published.
Certificate Authentication for Azure App Registration
Idea:
Option to pause creation of updates or applications for specifics products
Idea:
Add an operator dropdown in the filter options for Intune and ConfigMgr scan wizards
Improve Manage Conflicting Process configuration window to better support scaling
Fixed a bug where PatchMyPC-Scriptrunner may throw an exception during log cleanup if the folder does not exist
Fixed a bug where the publishing summary in the PatchMyPC.log would not include products published from the local content repository
Fixed a bug where changes to Intune assignments are applied even if the assignment form is cancelled
Fixed a bug where the Manage Conflicting Process window would not show up when the product install is triggered via Company Portal as a non-admin user
Validate the hash of pre/post scripts on sync as well as during a republish.
Idea:
The Collect Logs button now prepends the file name with the company name from the license.
Idea:
PatchMyPC.log file now includes the timestamp for the catalog that is processed.
When a download happens we now write the redirected URL to the PatchMyPC.log as well as in the PatchMyPC-DownloadHistory.csv.
The Publisher will now retry every 10 seconds up 12 times when saving Package.xml for ConfigMgr applications. This helps account for file locks caused by antivirus.
Email report has been updated (dark mode)
Fixed a bug where illegal characters were allowed in file paths, such as a custom log path.
Fixed a bug where an application may report being automatically enabled during every sync in some scenarios.
Fixed a bug where the UI would not show up for a user-based application.
Fixed a bug where the UI would not show for an Intune application when the user is not an Administrator.
CSV files are now saved with UTF-8 formatting.
Fixed a bug where Intune ADR (private preview) would publish both an Application and an Update.
Fixed a bug where we might fail to match a running process with Manage Conflicting Processes if the case of the process name did not match.
Fixed a bug where a corrupt backup settings file may cause the Publisher update to fail.
Patch My PC has determined the scope of impact and will reach out to Preview customers who are impacted.
Fixed a bug where the timestamp configuration was reverted to disabled, and the server blank for customers with preview builds enabled. The timestamp configuration will be reverted to the last known good configuration for impacted customers.
Note: If updates or applications were published while on preview 2.1.2.1, or if you are a preview customer on 2.1.3.0, then the updates and PowerShell scripts would not be timestamped during this time. This preview restores a valid timestamp
Support for maintaining application dependencies in Intune
Checkbox added to Intune Options window: “Update application dependencies from previously created applications when an updated application is created”
Idea:
When republishing an Intune application or update there is now a prompt asking if assignments should be recreated. The newly recreated assignments would have a deadline and available time relative to the sync when the republish happens.
Fixed a bug where republishing a ConfigMgr application would remove existing application dependencies, supersedence, and requirements the customer may have added.
Fixed a bug where the Manage Conflicting Process option to use the ConfigMgr application max run time for the notification timeout would not work for a republished ConfigMgr application.
Fixed a bug where republishing an Intune application or update might remove existing assignments.
Fixed a bug where we may fail to put back the version on the name of retained ConfigMgr applications in some scenarios.
Updated to the latest Patch My PC logo.
Fixed a bug where the Republish feature may cause multiple republish actions to occur if the customer performs the operation on multiple tabs.
Fixed a bug where ‘disabling’ a tab with the checkbox at the top would cause the settings to be lost if the Publisher was closed.
Fixed a bug where the alert webhooks may be duplicated during a setting import.
Fixed a bug where some unsupported right-click options might be enabled by the auto-enable product’s rules.
Collect Logs button added to the Publisher. Will create a .zip file of files useful for troubleshooting.
Idea:
If the ConfigMgr applications are configured to remove the version from the name, and there is application retention configured we will now append the version to OLD versions of the app. This is to ensure that there is only one application with the same name.
Improved the initial configuration process for adding Patch My PC Software Updates to an environment. This involves attempting to restart the WCM component after an initial Patch My PC update is published. This expedites getting the Patch My PC category into ConfigMgr so it can be selected.
The Publisher will send an alert if the catalog failed to download.
Fixed a bug where the /SyncNow switch for the Publisher would not work if an instance of the Publisher was already running.
Fixed a bug where multiple assignments for the same group may attempt to be created in Intune.
Fixed a bug where the Organization Name specified for the Manage Conflicting Process window would not be populated for ConfigMgr applications.
Fixed a bug where the icon would not be set for a republished Intune application.
Allow customized popup notifications, including support for localization.
Idea:
It is now possible to ‘Manage ESP assignments’ from within the .
Fixed a bug where the Publisher would fail to parse a command line that had a parameter that occurred more than once. This would cause a content update every sync.
Clicking a ‘localhost’ download URL in will validate the local content.
Idea:
Option to “Republish” ConfigMgr and Intune Applications
Idea:
ConfigMgr database scan button is now available on the ConfigMgr apps tab as well as the Updates tab.
ScriptRunner will always use Intune-based folders when executing from an Intune app installation.
ScriptRunner will now monitor for child processes during the uninstall of software. This ensures that uninstalls which spawn child processes do not exit immediately and cause a detection error.
Prevent using a ConfigMgr source path that could cause paths to exceed the 256 Windows path limit.
Fixed a bug where Recreate Detection Script option for ConfigMgr would cause the wrong ‘Installation Behavior’ to be set for user-based apps.
Fixed a bug where the Publisher and ScriptRunner would fail to parse a parameter with nested quotes and spaces.
Fixed a bug where PreventStart UI would fail to be bypassed when a SYSTEM launched a conflicting process potentially leaving behind Image File Execution Option registry keys.
Fixed a bug where retained applications may be updated unexpectedly when both postpone app and retain app are configured.
Text boxes within the UI now implement an autocomplete for file paths and URLs.
The notification will now display ‘update’ based language for an Intune Update. For example, the button will say ‘Close and Update’ instead of ‘Close and Install.’
Fixed a bug where the ConfigMgr would perform a partial match, such as \\server\source_apps being considered a conflict for \\server\source. We now append a trailing slash to the comparison.
Fixed a bug where the ‘Prevent Start…’ option for would throw an access denied error instead of the desired message box.
Fixed a bug where assignments would be copied from Intune app to Intune updates when the copy between tabs is used.
Fixed a bug where custom return codes set in the catalog were not processed for updates by the Publisher.
Improve conflicting process timeout options
ConfigMgr and Intune timeout increased to their respective maximums, minus a 15-minute buffer.
ConfigMgr App Max: 705 minutes
Intune Max: 45 minutes
Fixed a bug where the Publisher would throw an exception if a ConfigMgr scope is deleted, but still associated with a product in the Publisher.
Fixed a bug where Intune email reports would not include the warning regarding missing local content for applications
The Publisher will not delete the local content for a product if the publishing of the product failed.
The Publisher will automatically revise an update if the applicability rules or description is updated in the catalog.
Fixed a bug where the Manage Conflicting Process window may not show the proper process name in the list of conflicting applications.
Fixed a bug where the Publisher did not respect the ConfigMgr app retention settings when the delay in-place upgrade feature was also in use.
Fixed a bug where Intune apps and updates would not use the temp content download directory specified in the advanced tab.
Fixed a bug where the Publisher would revise ConfigMgr apps every sync in certain cultures (The known issue was with Russian, but could impact others).
Double-clicking a product in the Publisher will now bring up the ‘‘ tool.
Idea:
The Publisher will now check the permissions associated with the token for the Azure App Registration and provide more specific errors and logging. Additionally, the ‘Test’ button now presents a more information UI for permission validation.
Added tooltips to fields in the scan wizards to improve accessibility.
Fixed a bug where the Manage Conflicting Process UI may continue to append text instead of having a countdown when it is set to ‘Do not allow user deferral…’
Fixed a bug where pre/post uninstall scripts would only copy into the ConfigMgr source during a new application publisher. Scripts will now be copied into the source during the sync after the configuration change.
Fixed a bug where the Intune Assignment UI would allow an invalid grace period/restart/snooze configuration.
Fixed a bug where PatchMyPC-ScriptRunner would create an invalid command line for an MSI uninstall in some cases.
Fixed a bug where user-based ConfigMgr applications may not have the Application Experience configuration properly configured.
Manage Conflicting Process ‘Close and Update’ button will now call the CloseMainWindow first. If the conflicting application is still running after 20 seconds we fall back to the Kill method.
This gives the user 20 seconds to respond to any ‘save’ prompts or other app-closing windows.
Idea:
Pre/Post scripts for uninstall
If publishing an update fails with timestamping then we will attempt to publish again without timestamping.
Improved connection testing to patchmypc.com:443 during publisher sync.
During Publisher sync the WSUS cleanup for ‘Unneeded update files’ will now run.
Fix user validation of the input fields for pre/post script when the file does not exist.
Fixed Intune detection script which was looking for a non-existent ‘dn’ property.
Fixed Intune detection script so that it will parse invalid version parts that exceed a 32-bit signed integer.
Fixed ConfigMgr detection script so that the RegKeyDetection work as expected for enhanced detection based on additional registry key values.
Allow the scheduling of the Modify Updates Wizard for Update Cleanup (unreferencedpackagefolders)
Idea:
Fill out ‘Disk Space Required’ for Intune apps.
Idea:
Further improvements to CM log format for culture compatibility.
Add support to re-sign updates.
Idea:
Doc:
Use windows native methods for signing PowerShell scripts.
PowerShell detection scripts will use regex to extract the version from the displayVersion field to account for vendors that put more than the version in the field.
Set ErrorAction to SilentlyContinue for extra regkey validation checks to suppress errors in the event the key does not exist.
Add a delay in Scriptrunner if the main installer exits in less than 2 seconds. This is to account for installers that spawn child processes.
Add option to update Intune assignments on sync.
New checkbox at the bottom of the Manage Assignments wizard to ‘Override manual assignment changes…’
Idea:
Add title of application or update to the Manage Assignments wizard.
When a product is double-clicked in the tool the applicability rule will be shown.
Improve the message which displays when an incorrect configuration is saved.
Code changes in preparation for user-based applications.
Fixed a bug where the Manage Conflicting Process window would not appear when a ConfigMgr application was deployed as required and the checkbox for ‘Allow user interaction…’ was not checked.
Fixed a bug where Intune role scope tags would not be updated on sync for Intune Updates.
Fixed a bug where the configured proxy may not be used for the Intune connection during publisher sync.
View and customize Conflicting Processes list
Idea:
The UI notification for Conflict Processes now lists all processes which are conflicting in a dropdown. This is to make it more clear what software will be closed.
Publisher SMTP alerts for the creation of ConfigMgr apps, Intune apps, and Intune updates will all now show the CVE information. Previously only the WSUS updates would show this information.
Added notes to the pre/post script window to help clarify the feature functionality.
Fixed a bug where software may be marked for revision during every sync of the Publisher. This would occur when PreventConflictingProcessRestart was in use and the KillProcess was set instead of Notify.
Fixed a bug where the 'Exclude from Auto-Publishing' option for Intune apps and Intune updates may not work as expected causing excluding software to still be published if found.
Send alerts to Slack
Idea:
Note: Slack notifications are a work in progress.
Reverted a Scriptrunner change which flagged the exe to always run as Administrator. This is in preparation for supporting user-based applications in Intune and ConfigMgr.
When a user or admin category was selected on a ConfigMgr application the Publisher would create a revision of the application every synchronization. Now a revision will only be created if a user or admin category needs to be added.
Improved logging when checking access to timestamp.digicert.com if a proxy is defined
Added support to add a future Home Lab subscription
Idea:
Added a new context menu in the Intune Application Manager
Improved logging
Added support to add a future Home Lab subscription
Idea:
Added a new context menu in the Intune Application Manager
Improved logging
Added support to add a future Home Lab subscription
Idea:
Added a new context menu in the Intune Application Manager
Improved logging
Define ConfigMgr scopes inside the Publisher service
Idea:
Note: This requires updated permissions. The ‘Import Role’ option in the Publisher will import the role with proper permissions or you can refer to this .
The Intune and ConfigMgr scan wizard ‘Export’ buttons now prompt for whether the filter should be applied to the export.
Improve how Timestamping is handled in some scenarios.
Connections to Intune may not respect the proxy configuration set in the Publisher.
‘Show Package Details…’ right-click option would not load as expected.
CVE Wizard would not load as expected.
SSRS dashboards would report a negative % for compliance in some scenarios. The reports can be reinstalled if you are affected by following the same process as the initial install which will overwrite the reports.
Added the Usage Statistics group in the General tab that will show usage statitics
Idea:
Changed the license input to display only the 20 character license id and not the full license URL
Improved the speed of Intune application deletion by using batch calls to Microsoft Graph
Options related to WSUS have been moved from the Advanced tab to the Options button in the Updates tab
The classification field in the Intune Apps Manager is not populated for Updates
Update revision doesn’t take account of republished updates
Change description text and icon for Intune Win32 applications
Idea:
Retain N-X apps in ConfigMgr when set to ‘Create a new application…’ is enabled.
Idea:
The scan wizard found application count is now updated to reflect applications found with the specified filter.
Scriptrunner will now clean up leftover ‘Image File Execution Options’ registry keys. This helps prevent unexpected blocking of application launch in the event scriptrunner crashes and leaves behind some of these keys. We have also update the to provide additional information for this scenario.
Fixed a bug where assignments may not be added to an existing Intune Win32 application during Publisher sync.
Fixed a bug where the Publisher UI would crash if the ‘Modify Updates Wizard’ was launched on a computer which does not have the WSUS role.
Fixed a bug where only the first 1000 Intune applications are returned which can cause Application lookup failures via Microsoft Graph.
Intune Scoping Support
There is a for Intune applications and updates which lets you ‘Manage scope tags.’
Scope tags will be copied from the previous PMPC application or update to the new version during a Publisher sync.
Requires new permission to be added to the Azure App Registration
Wait to delete local content repository files until the end of the Publisher sync if the option to ‘Delete the update file in the local repository after publishing’ is selected.
In some cases, customers had the same binary needed for two different publish actions, and the second publish would fail because the binary had been deleted.
In the DownloadHistory.csv file, we now include the purpose of the download and the port.
ConfigMgr right click option to set OS type requirement – client vs. server
Idea:
Scriptrunner will now automatically prompt for elevation when executed.
Improve how settings are saved to prevent losing your Publisher configuration in some scenarios such as no disk space.
The UI Notification feature for conflicting processes will now exit with an exit code 1602 if the installation is snoozed or a timeout occurs. Previously it was 1618 which could cause very frequent reevaluation.
Fixed a bug where we may fail to parse a package.xml file that contains special characters such as an ampersand.
Fixed a bug where the DownloadUrl and MoreInfoUrl columns were not sortable in the ‘Show Package Info’ UI.
Fixed a bug where the UI may crash if there is a large number of Azure AD Groups being retrieved and the UI is closed before the query completes.
Fixed a bug where some right-click options such as Manage Categories, Manage ESP profiles and Manage Naming Convention may not propagate from the root, or vendor level to a newly enabled product.
Fixed a bug where some Intune App and Intune Update scripts were missing a parenthesis causing an error during execution.
Fixed a bug introduced in version 2.0.0.1 preview where the ‘Disable Self-Updater’ option would be enabled during a synchronization even if the user has not selected this option.
If you are on a 2.* preview build you will want to review your right-click selections for ‘Disable Self-Updater’.
The backup settings.xml can be used to determine which products had this erroneously enabled. Please contact support if you need assistance in determining what products had this enabled where it previously was not.
Global options for the User Notification now moved into right-click option for Conflicting Processes
Logo
Company Name
WSUS Certificate status now updated when the Show Certificate button is pressed.
Fixed a bug in the ConfigMgr detection script where software may be incorrectly detected in some scenarios.
Only impacted version v2.7 of the script which was available briefly.
Script Version: 2.8
Use Scriptrunner to uninstall MSIs
Idea:
Increase the max delay for the ConfigMgr Apps feature to 32 days.
Intune Application Manager button is now available in the Intune Apps and Intune Updates tab directly, as well as in the Intune Options.
ConfigMgr detection scripts now validate architecture and installation type of of the software being detected.
This feature was in place for Intune scripts and has been integrated into the ConfigMgr scripts.
Fixed a bug where the new Conflicting Process settings may not be saved for ConfigMgr applications.
Fixed a bug where the company logo may not show in the Conflicting Process UI for Intune clients.
Fixed a bug where the Conflicting Processes deferral count would allow more than the configured number of deferrals.
Interactive user notifications that allow the user to be prompted to close conflicting software
Has a range of options for customizing the deferral options.
(Documentation will be released when this feature is in production)
Idea:
Only one instance of the Publisher is allowed to run at a time. If a second user runs the Publisher they will receive an error message and the Publisher will close.
Fixed a bug where adding file based right click option to a ConfigMgr application would not trigger a revision in some cases.
Examples: MST, Pre/Post Script, Additional files
Fixed a bug where the Intune detection and requirement script might fail to work as expected if there are invalid registry properties on an object in the registry.
Update right-click option text to accurately reflect functionality.
Exclude from being enabled during automated SCCM/Intune inventory scans
Renamed to: Exclude from auto-publishing rules
Add/Manage pre/post update installation scripts
Fixed a bug with the new Log Retention feature of Script Runner where it may unnecessarily trigger an ‘Update Content’ on ConfigMgr applications. (actually fixed this time)
The warning message box that pops up if the Enrollment Status Page right-click option is invoked without proper Azure App Registration Permission now has a ‘Help’ button which links to the permission KB article.
The pre and post script ‘browse’ buttons now will open to the location of the currently selected script if found.
Fixed a bug where the Intune Scan or ConfigMgr Scan would happen if the respective ‘Auto-Enable’ option was enabled, but the feature itself, such as Intune Updates, was disabled.
Fixed a bug where the Teams notifications for auto-enable would not contain details regarding the software.
Fixed a bug where the auto-enable feature of Intune Scanning may cause duplicate Win32 apps to be published within Intune.
Fixed a bug where conflicting right-click options could be selected in the scan wizards.
Sign PMPC provided pre/post scripts with local WSUS Code Signing certificate
Idea:
ScriptRunner now deletes log files older than X days according to the setting in Advanced Tab.
Idea:
Add an additional Right-Click option for x86 OS requirement for x86 application installers
Idea:
Improved vertical scrollbar behavior for Scan Wizards
Fixed a bug where an Enrollment Status Page may have a mobileAppId listed twice when making the Graph PATCH API call. This would cause a 400 status code, and cause the API call to fail.
Modify Autopilot Enrollment Status Page profiles.
Update ESP profiles when an application is updated. This will ensure the latest application version is associated with your ESP.
New to enable.
Select profiles an application should be assigned to with a new
PatchMyPC-ScriptRunner has improved logic for UninstallPackage.
Now factors in SystemComponent and QuietUninstallString when searching the registry.
Intune Scan Wizard updated to match the ConfigMgr scan wizard.
Can include zero-count applications in results and export.
Fixed a bug where the certificate option would be enabled while in
‘Intune Only’ mode.
Fixed a bug where the Intune Graph token used by features such as Intune App Category selection would expire if the Publisher UI was open for a long time.
Fixed a bug where unnecessary calls were made to renew the Graph API token when performing Graph Batch queries.
for Intune Applications
Idea:
Adjust certificate signing validation for Patch My PC signed files.
Manage categories for Configuration Manager applications
User Categories: Viewable to users in Software Center
Admin Categories: Viewable to administrators in the Configuration Manager Console
Idea:
During a Publisher sync, the Settings.xml will be automatically updated according to SupportProducts. This improves the experiences when Patch My PC makes metadata changes that impact some of the application configurations such as detection.
ScriptRunner now has a new custom variable, %CurrentDir%
This variable may need to be put in double-quotes or the entire parameter may need to be in double quotes depending on the application. Examples of this are below.
Config=”%CurrentDir%\Config.ini”
The Intune Application Manager now has a button for ‘Manage Assignments’
Improve how ScriptRunner handles version parts that exceed the 32 bit signed integer max.
Improve CVE-ID matching
Improve logging associated with delayed application publishing
Manage Intune categories for created and updated Intune applications and updates.
Note: Currently, existing applications/updates in Intune will not have their categories modified. The categories will only be modified when a new Win32 application is published such as when new software is selected, or a new version is released.
Idea:
Clicking a ‘digest’ in the Modify Published Updates Wizard, or the Package Details wizard will now open the respective VirusTotal page.
Sorting by ‘Selected’ in Modify Published Updates Wizard now sorts by the checked state.
The Configuration Manager detection script now handles invalid version parts better. Some vendors use DateTime stamps in their version. This can end up being a value larger than a 32 bit integer causing the version cast to fail.
Fixed a bug where the console version check for UninstallContent setting was incorrect.
Fixed an issue where copied Intune Assignments for newly published Intune software would not have their custom available time, and deadline time adjusted relative to the new publish date.
Fixed an issue where Intune Assignments would be created without a deadline or available time if the ‘copy assignment’ option was not configured.
Fixed an issue where the maximum value for restart notification would not allow a value greater than 201.
Win32 Intune applications will no longer be created as featured
Improved the speed at which the catalog is extracted for the CVE Import Wizard
New feature that allows .
Idea:
The below information can be viewed for the currently synchronized catalog.
Title (Including version)
Improved the speed at which the catalog is processed. This will improve the loading speed of the CVE Import Wizard, the new Package Details Feature, and the Modify Updates Wizard.
Updates published via the CVE Import Wizard will now have a Teams and Email alert if enabled.
Scan Configuration Manager Database wizard updated.
Supports Filtering
Can optionally show, and export, applications whose count is zero.
Certificate selection for Intune code signing will now additionally search the WSUS store if it is found.
The Product Name has been added to the PatchMyPC-DownloadHistory.csv generated in the installation directory of the publisher.
Improved the method used to gather PackageID from newly published Applications.
Fixed a bug where an application may fail to publish on versions of Configuration Manager older than 1706.
Fixed a bug where the publisher would fail to find applications published to a folder containing square brackets
For Example: \\server\sources\[PMPC]Applications
Fixed a bug where the TLS port for SMTP alerts may show as 587 in the UI, even when a custom port is set. The port in the UI will now accurately reflect the saved settings.
The first preview release of our CVE import/matching features based on UserVoice
You can launch the CVE import feature in the Updates tab by clicking the new document lock icon
If you have any feedback on the first preview release, leave a comment at
Fixed an issue where Intune assignments may not set the correct delayed deadline
Fixed an issue where older versions of the ConfigMgr console may receive error: Method not found: 'Void Microsoft.ConfigurationManagement.ApplicationManagement.MsiInstaller.set_UninstallSetting(Microsoft.ConfigurationManagement.ApplicationManagement.UninstallContentSetting)'.
The PatchMyPC-ScriptRunner.exe will retry MSI based operations if a 1618 exit code is returned by the installer. The result is a reduction in failed installs due to Windows Installer being unavailable.
Maximum three retries, with 1 minute in between.
Update the PatchMyPC-ScriptRunner.exe to use the CCM client log directory defined in the registry by default
Check
“HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\CCM\\Logging\\@Global”
> LogDirectory, and fallback to ‘%windir%\\ccm\\logs’
Idea:
Log out the in-progress count of updates and applications as they are processed.
Previously the in-progress count was only logged if the log level was set to debug. It is now logged with informational level logging.
Improve the PatchMyPC-ScriptRunner.exe to have better logic when searching the registry for uninstall strings
Configuration Manager application detection script fixed to supported PowerShell 2.0.
Fixed an issue where republishing a WSUS update would also cause the equivalent Intune Update to republish as well.
Application update in-place vs. create new application configurable at the individual product level.
Idea:
Support for user-based installations for Configuration Manager applications, as well as Intune Applications and Intune Updates.
Updated the PowerShell script for Intune applications and updates to improve compatibility with constrained language mode.
Publisher code changes to better support our program
Fixed an issue where the would throw a terminating error if Intune applications were found with an empty ‘Notes’ field.
Added an option to disable WSUS publishing using a checkbox at the top of the ‘Updates’ tab. This allows the Update publishing feature to be disabled while still retaining all products and settings. This can be helpful if you need to sync only Applications, Intune Applications, or Intune Updates, but don’t want to lose your selected Updates and configurations.
Added a right-click option to open the help page that details the right-click options.
During synchronization, the Publisher will check if the WSUS code signing certificate is expired or near expiration and add a message in the email report.
Add additional known errors in the log, providing a link to a KB article that may assist with solving the known error.
Display additional info in the Certificate information wizard on whether the certificate is found in the expected Windows Cert stores.
SMTP port default to 25 instead of 587 when the feature is in a non-configured state.
The Publisher will retry several times when the rename of a folder during an SCCM application upgrade fails. This should help prevent
Fixed an issue where, sometimes, the SupportedProducts.xml file cannot be read during a synchronization.
Fixed an issue where a machine with a large number of CPU cores may experience high CPU load when running the Intune Scan Wizard.
Improved the copying of right-click options from the Updates tab, to the ConfigMgr Apps tab, or the Intune Apps tab.
Fixed an issue where the Publisher would falsely report that it was not installed on a Software Update Point in some scenarios.
Fixed an issue where the Intune Updates product list was not reloaded during publisher sync in some scenarios.
You can now for allowing the publishing to create Configuration Manager applications.
Add Anonymous authentication method to send emails.
User voice
Intune updates use the description in the SDP for the title.
User voice
Add a button to export data in the Intune Apps Manager.
Add a column to show Classification in the Intune Apps Manager.
Allow to show «Applications only», «Updates only» are «All» in the Intune App Manager.
Display the Publisher service's status on the 'About' tab.
Fixed an issue where custom options are not correctly copied between two tabs when copying enabled products from one tab to another.
Fixed an issue where reserved characters were not working as expected when searching for Azure AD Groups
Fixed an issue where the Publisher may display a warning that the certificate is incorrect or missing when it's within 30 days of the expiration date.
Support for Intune Updates
Changed how Unreferenced Package Folders are found. If third party updates are set to display in WSUS, then they might show up as
'Unreferenced' by the WSUS content cleanup tool. The publisher now correctly display the list of unreferenced contents.
Add even more logging to the Application update, and creation processes to assist with troubleshooting.
Code optimization and cleanup for Applications
Fixed a bug where the Publisher service would never timeout during content downloads in some scenarios. This could cause the service to hang.
See the for more information regarding the timeout. The default value is a 15 minute download timeout.
Detection script now accounts for user based installs when needed.
Detection script checks if running as SYSTEM using the SID instead of username.
Add additional logging to the Application update, and creation processes to assist with troubleshooting.
Add a new known error to assist with identifying and resolving TooManyCategories for WSUS.
Fixed a bug where some system cultures would result in incorrect command line parsing.
Fixed a bug where an Application's content would not be updated when a right click option was selected in some scenarios.
Add an Intune Scan Wizard allowing you to auto-enroll applications based on Intune App scanning
Add all options available in the 'User Experience' for Applications to a new Context Menu option for base installs.
Enabled CTRL+F functionality in the Intune tab.
Product download will fallback to the Internet in case of digest mismatch in local content repository.
User voice
Fixed a bug where the "Exclude from autoenrollment' option was unable to be changed on a product when the setting was configured at the vendor level.
Fixed a bug where the publishing service could not publish a postponed application if it contained an HTML escaped character.
Fixed a bug where the Intune Authentication URL was being overwritten by the Intune Scane Wizard
Add an Intune Scan Wizard allowing you to auto-enroll applications based on Intune App scanning
Add all options available in the 'User Experience' for Applications to a new Context Menu option for base installs.
Product download will fallback to the Internet in case of digest mismatch in local content repository.
User voice
Display third party vendor/product count in the Update Modification Wizard.
Fixed a bug where the "Exclude from autoenrollment' option was unable to be changed on a product when the setting was configured at the vendor level.
Fixed a bug where the publishing service could not publish a postponed application if it contained an HTML escaped character.
We now use a FIPS compliant algorithm when creating Intune applications
Fixes
Fixed an issue where the checkbox in the MSI installer to enable Intune only mode may not be applied after the installation
Fixed issue where the republish option no longer showed for "All Products" and Vendor nodes
Fixed issue where incorrect workstation counts were shown on certain SSRS reports
SCCM Database Scan now has option to ["Auto-enable products as
'Metadata Only' if found, but threshold is not met"]()
Fixes
Fixed issue where a customer with an expired Intune only license could be stuck in a messagebox loop.
Enhances the display in the Update modification wizard when there is a lot of updates.
Cache binary for postponed updates allows postponed updates to be published after the download link has changed.
applied at the All Products level will now be retained when the UI is closed, and future products are enabled. UserVoice Idea:
Added support for Server 2019 in the
Fixes
Fixed some issues where some links may not work in the SSRS dashboards
Allows creating a self-signed certificate with the private key marked as non-exportable.
Added new subscription state reporting using Teams or STMP emails
Added like, dislike, and feedback button in the title bar of the settings tool.
Fixes
List unreferenced package folders don’t list any folders in some WSUS configuration
Added a workaround to handle SCCM apps published with an unsupported language
Improvements
Adds a new column, UpdateEnabled, to the resulting CSV from the SCCM Scan Database Wizard -
(Idea: )
UI improvements to the Base Install options
Fixes
Fixed an issue where double quotes in the command line argument for software updates would not be retained.
Fixed an issue where adding multiple Intune assignments with customer deployment deadlines may cause the publisher UI to crash
Intune assignments created during an application creation or update are now reported in Teams notifications and email alerts
(Idea:
)
Adds a line in the log to specify Intune AppIDs (old and new release) during an application updating (Idea:
)
Improves how Azure AD groups are retrieved (Set page limit to 999). We will also now display O365 groups. Adds the ability to search a group based on the group name starts with (Idea:
Dropdown filters could be edited in the update modification wizard
Trying to import a KSP CNG based code-certificate leads to an error
OS requirements were added during an SCCM application upgrade even though they were already there
The application deployment type Install behavior was not set during the application publishing if the KillProcess option was not enabled
Improved the Microsoft Intune options. The options are now available in the Intune Apps tab and not the Advanced tab.
Improved the installation options for enabling Microsoft Intune only publishing.
Adds a new application management tool for SCCM in the application options menu. You can now bulk delete applications created from Patch My PC or bulk delete deployments for applications.
Changed title format for republished updates to be more granular
Included updated DLLs for Compression.cab from Wix
When an update is republished, all previous republished updates can be superseded by the new update that is republished.
Fixed an issue where the right-click option for manage logging may display the correct information
Use env variables instead of hard-coded path in PowerShell detection script.
Other fixes and improvements.
Changes
Rename Intune preview to Intune Release Candidate.
You can now select a custom code-signing certificate from the computer's personal certificate store. A full WSUS installation is no longer required for code-signing the detection method script used for Intune.
Applications will no longer be duplicated in the event the deployment type's source folder was deleted.
Fixes
Bug fixes and other improvements
Fixed an issue where you may receive an error: An error occurred while updating a package in SCCM: OpenDatabase,DatabasePath,OpenMode
No longer perform WSUS service checks when the WSUS publishing is disabled for Intune only scenarios.
You can now create assignments for Win32 applications in Microsoft Intune
The authority URL for Microsoft Intune will be prepopulated
The publishing service can now be installed on Windows 10 (x64) for a Microsoft Intune only setup.
Added support for creating Microsoft Intune Win32 applications in preview mode.
You can now set a custom folder for temporary downloads of the software update and application content
You can now set a custom folder for the log save location
You can now trigger a full and delta software update point synchronization from the advanced tab
You can now test the SMS Provider connection under SYSTEM-level context
Files downloaded for publishing updates are now cached and reused for applications within the same sync cycle
Support to publish applications in other languages than en-US
Minor changes to support product renaming for Firefox, Nitro Pro, Nitro Enterprise, and Node.js
Improved the accuracy of the SCCM application scan feature to better differentiate between x86 and x64 products based on UserVoice
You can now send Microsoft Teams publishing alerts using a webhook
Improvements
The software update point synchronization will be triggered after the update synchronization task rather than waiting for the updates and applications sync.
Fixes
Minor bugs fixes
Minor bugs fixes
You can now configure a custom application name, localized application name, localized application description, and icon
Fixed an issue where the UI may crash when enabling a large number of products
You can now exclude products at the vendor level from being enabled in automatic scanning
You can now press F4/Shift+F4 keys to go to the next/previous when searching products or vendors
Improvements\
When disabling updates, we will now create a RegKey is it doesn't exist to disable self-updates
Improved logging
You can now enable your software update point to sync when updates are published when your software update point is on a remote site system.
Preserve User Categories when updating Apps in SCCM
Preserve Admin Categories when updating an SCCM application
Changes
Set default download timeout to 100 seconds from 30 seconds.
You can now increase the
Fixed an issue where a custom command line may not be processed if it contained double quotes and a space.
Create a CSV file at the end of each synchronization with a summary of what was published, revised, created
You can now set the max log size between 1-10 MB
Improvements
Add several log entries when sync fails
()
Added an option to show and delete unreferenced WSUS folders in the UpdateServicesPackages folder
Added an option to show/hide already enabled products in the SCCM scan
Added the ability to start a sync by running the PatchMyPC-Settings.exe with argument /SyncNow (the UI is not displayed)
Log events in the Windows event log (Starting/ending sync, success/fail publishing updates)
Fixed an issue where application detection method scripts may fail on devices with PowerShell version 2. The following output error would be logged to appdiscovery.log
Unexpected token '.0' in expression or statement.
CategoryInfo : ParserError: (.0:String) [], ParseException
You can choose a custom folder in the applications node of the console to move applications to upon creation or updating automatically.
You can now include custom folders for updates and applications.
You can now specify the subject name when creating a self-signed certificate.
Display the count of updates and selected updates in the update modification wizard
Bug fixes
PatchMyPC-ScriptRunner.exe files are updated when SCCM applications are upgraded.
You can now Import/Export settings from the advanced tab.
Added the ability to delay updating an application in-place for 7 days after release.
If SMTP emails are enabled, we will now include any newly enabled products from the automated SCCM inventory scans.
If there are pending settings changes unsaved, you will be prompted if you want to save the settings when performing a synchronization.
You can now configure any custom pre-update script to run before checking any processes to close or skip
Improvements
Improved logging
Added options to Kill or Skip installations when auto-enrolling new products.
Application names are now clickable for applications published, and links to the vendors release notes.
Added right-click option for products to be excluded from being automatically enabled during automated SCCM inventory scans.
You can now automatically enable products to be enabled based on them being detected in the SCCM database.
Fixes
Fixed an issue where applications may fail to install on Windows 10 when using Latvia language.
Fixed an issue where you may get an email about the license being expired when in trial-mode.
Fixed an issue where the option to copy the installation log to a secondary folder on installation failure would not work correctly.
Added an option to copy the installation log to a secondary folder on installation failure.
Updated the detection method script for applications to resolve the following error (Access to the path
'C:\\Windows\\CCM\\Logs\\PatchMyPC-SoftwareDetectionScript.log' is denied.) that would occur in AppDiscovery.log in certain builds of Configuration Manager.
Added an option to include abitrary files in the pre/post script dialog box.
Fixed an issue where the SSRS report RDL files may fail to upload to SQL Server Reporting Services.
This update contains improvements to help support the future release of the application creation feature.
Fixed an issue in build 1.3.9.4 where applications may fail to update with error: property DisplayInfo.DisplayInfo.DefaultLanguage: Language En does not match any data in the set
Added the application option to "Allow clients to use distribution points from the site's default boundary group."
Added support to code-sign the PowerShell detection method script using the WSUS Signing Certificate. This option is enabled by default.
Organized the Base Install Options dialog.
Improved the detection method PowerShell script processing speed for all application deployment types.
The base installation feature now creates applications in SCCM rather than legacy packages.
Improvements
You can now configure an offset (in days) for the sync schedule. Based on customer idea:
When using a custom pre/post update script, it will be run before any Patch My PC defined script. Based on customer idea:
Fixed an issue where if you switch from the general tab to the update rules tab very quickly on open the products enabled may reset and the Settings.xml would need to be restored from the
\\\Backup folder.
Improvements
Added an option to prefix the computer name to the installation log file name to allow you to use a shared path and receive unique log file names for each device.
Fixed an issue where if you are using a 24-hour time format in an EN-US server operating system the saved schedule may not reflect correctly in the sync schedule.
Bug fixes
Added a new right-click context menu item to add MST transformation files for MSI based product installers.
Right-clicking on a product will now display the installer technology the product uses (MSI, EXE, or MSP)
Fixed an issue where the UI may show not responding for a short period of time on initial open.
We will now cache the list of supported products, so in the event, the settings tool can't download the latest products, it will use the last cached copy.
When the settings tool is opened, if any products are previously enabled that now have a Patch My PC defined recommended and required Pre/Post script(s) those scripts will be saved in the settings.xml automatically.
Features
Added support for required Pre/Post-Scripts
When there is a product enabled that requires a the product name(s) will be included in the prompt.
Features
Added support for recommended Pre/Post-Scripts
Added subscription level and licensed device count based on feedback in the SCCM slack group.
We removed the two columns displaying the distribution point group and description in the base installation options dialog.
Change the error return for 404 download errors.
Fixes
Fixed an unhandled exception when you enable base packages when no catalog URL is set.
Changes to improve the performance of the license validation check.
Revisions to packages are now included in email reports.
When using the Scan SCCM for Managed Applications feature, the database server, database name, and connection account details will be retained after a successful query.
Split our the following products to be major version specific to allow more specific selection.
ESET Endpoint Security
ESET File Security
Royal TS
Fixed an issue where updated installation packages are not added in the email report
Fixed an issue where superseded applications may not publish into SCCM
Miscellaneous fixes
When a package is created for a 64-bit product, the requirements will be configured on the program to only install on 64-bit operating systems
If a package fails to be created, the distribution attempt to SCCM distribution points will no longer be performed.
Fixes
Miscellaneous fixes
Added an option to change the subject name for email notifications
Fixes
Fixed an issue where SCCM package creation is malformed when updates are configured to be republished.
Fixed an issue where products are still listed in the SCCM application scan when the Include Products Already Enable in Scan is not checked.
Added an option to include text in the body of the email notifications.
Fixes
Miscellaneous fixes
Disabled the delete option for published updates in the modify published updates wizard.
To enable the Delete button, create a new DWORD registry value: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Patch My PC Publishing Service:EnableDeleteUpdates = 1. We only recommend using this option when working with our support team.
Added an option to disable timestamping. We generally do not recommend using this unless there is a specific use case. To disable timestamping you can create a DWORD registry value:: HKEY_LOCAL_MACHINE\SOFTWARE\Patch My PC Publishing Service:DisableTimestamping = 1
Fixes
Added the new option to enable the creation of base installation packages in SCCM.
Other feature improvements and bug fixes
Ensure the Manage Conflicting Process notification shows the appropriate language for an application update vs. an application install.
Account for ConfigMgr applications that have content instances with a file size of 0.
Ensure that newly selected products from a ConfigMgr or Intune scan wizard are correctly displayed in the treeview when filtered to enabled products.
Ensure that localhost, and similar values such as 127.0.0.1, and . are allowed in the SMS Provider field.
Ensure folder browse dialogs open at the correct path from the Advanced Tab.
Hardware and OS requirements now correctly carry forward for Intune applications and updates, including minimum OS, memory, logical processors, and CPU speed. Patch My PC continues to maintain OS architecture.
Argument validation has been improved in the Add custom pre/post scripts form.
Assignments created in the Intune Dynamic Assignments UI now display correctly without requiring all related forms to be closed.
Rapidly switching filters and toggling expand/collapse no longer triggers unhandled exceptions.
Intune Dynamic Assignment Rules now accept names with a single character.
It's no longer possible to set an Intune naming convention without a token at the All Products or Vendor level, which previously caused all products to share the same name.
Right-click options now apply to the correct treeview, even when filtered to enabled products.
Form validation in the Scan Wizards now behaves as expected.
Return codes for custom applications are now handled consistently within the Publisher UI.
Custom products no longer incorrectly show as having customized return codes in the right-click menu when none are configured.
Fixed a bug where Publisher would not correctly write failures due to missing local content to patchmypc.log
Fixed ability to copy and click links and other data in the Package Details view of applications.
Improved Publisher Migration model to store which version of Patch My PC Publisher inventoried each application.
Improved grammar in Intune App Manager window.
Fixed a bug where sorting by date in the Manage Assignments group selector would provide inaccurate sorting.
Fixed a bug where the Publisher would refresh the UI before saving, causing settings to not save.
Improved logging to be clearer when sending test webhook notifications.
Added additional information in product export CSV.
Improve handling of postponed apps when apps cannot be copied to target directories.
%Version% variable now will be used if configured, regardless of the status of global overrides.
Improved the Publisher email report and logging to better indicate if the local content is outdated and needs to be redownloaded.
Improved logging to show whether or not the Publisher service is running when opening the UI.
Allowing selective syncs at the all products level.
Showing the tenant/app type in the selective sync popup.
Added tenant column to webhook list in the Alerts tab.
Minor UI Enhancements/Fixes.
Fixed a bug where the Publisher may select the incorrect SMS_Content instance in some cases when searching for a previous ConfigMgr application.
Fix bug in teams and email notifications where allusers and alldevices were shown as "excluded"
Fixed bug where Publisher log would suggest connection to SMS provider had no password when one had been provided.
Fixed a bug where opening the UI while a sync was running would throw an exception that indicated an error with reading the Settings file.
Add logic to have Publisher auto-create postponed binaries folders if configured.
Fixed bug affecting Intune apps export in the Intune App Wizard.
Fixed a bug where additional text added to the Publisher's email report was too small to read.
Fixed a bug where new selections from the ConfigMgr scan wizard are not selected in the treeview when you click Ok.
Fixed a bug causing Package.xml to be deleted when updating a ConfigMgr application in place.
You may see an error similar to 'Object reference not set to an instance of an object' or 'Length cannot be less than zero. Parameter name: length'
To fix an affected application, you will need to delete the application and its content, as the Package.xml file is no longer properly populated with a PackageId.
Added a notification to the ConfigMgr scan wizard to notify users when there are SQL errors.
Improved how Publisher displays information around misconfigured items and items that require manual content to ensure the warning does not consume the entire screen.
Fixed an issue where Migration feature could not be enabled.
Fixed an bug where product selections could not be copied between tabs when the new product selection filter was enabled.
Fixed an issue where product selection did not persist after a save when the product selection filter was enabled/disabled.
Add additional fields, related to user install statistics, to the Intune Application Manager.
Modernised the icons in the Publishers UI.
Update to the latest Preview Release (Version 2.1.36.90)
In the Publisher, navigate to the About tab.
You may already have the "Install preview builds" option checked (1)
If the "Currently Installed Version" is 2.1.36.80 (2) and the "Latest Available Preview Version" is 2.1.36.90 (2), click "Upgrade Now" (3) Note: If the "Install preview builds" option is not checked (1), please check it and click "Apply" and version 2.1.36.90 will be offered. You can now select "Upgrade Now".
Roll back to the latest Production Release (Version 2.1.36.0) If you do not wish to remain on the Preview Release channel, uncheck the "Install preview builds" checkbox on the About tab in the Publisher and click "Apply".
Download the latest Publisher production release from https://patchmypc.com/msi
Follow this guide to create a backup the Publisher settings (not required to roll back but recommended)
Uninstall Patch My PC Publisher from Add/Remove Programs (your settings will be preserved)
Install the Publisher production build MSI you downloaded in step 1
Important: Regardless of the option you choose, you will need to re-publish any applications that were published using version 2.1.36.80 to ensure the correct installation parameters are applied.
If you need assistance or have any questions, please visit our Technical Support page at https://patchmypc.com/technical-support/ to open a support case.
Amended the rolled over log file extension from .lo_ to .log.
Log username of active user when using Manage Conflicting Processes to kill processes.
Improved logging when ScriptRunner calls PowerShell scripts.
Fixed a bug where rolled over log files were not cleaned up according to retention settings.
Improve the handling of UINotificationSettings.xml for Manage Conflicting Processes. They are now generated per session.
XML per session prevents access denied errors that can occur when one user creates a file and another non-admin user later attempts to edit it.
Fixed a bug that caused Postponed binaries to fail to process when custom applications are enabled and the PostponedBinaries folder does not exist.
Fixed a bug where the option to select the ConfigMgr folder within the ConfigMgr application creation options was unavailable.
Stop processing a ConfigMgr application if the copy operation for retention fails. This ensure we do not edit an existing app unless the copy succeeds.
Added the total sync time to the PatchMyPC.log
Improved logging when there is a cloud connection, but no Intune deployments in the cloud.
Fixed a bug causing scriptrunner not to expand placeholder arguments such as %CURRENTDIR% when parsing command line arguments.
Fixed a bug causing errors similar to ‘Mutex access requested by GetIntuneAppProductFlags but a timeout occurred while waiting for mutex to be released’
Fixed a bug that caused custom applications to fail if they had two files with the same name inside their content.
Add support for Patch My PC to configure the ‘Run installation and uninstall program as 32-bit process on 64-bit clients’ option within ConfigMgr. This will not be a customer exposed option in the Publisher, but something that Patch My PC can set to ensure applications install as expected.
The username of the user who performed a save in the Publisher is now written to the event log, and to the PatchMyPC log file. Additionally an empty file with a GUID name is included in the CAB so the save event can be matched to CAB file.
Fixed a bug where cloud Product Selections were only displayed in the Publisher if the product was both deployed in the cloud, and selected in the Publisher. Products which are not selected in the Publisher will now properly show as managed by the cloud if a deployment exists.
Fixed a bug causing the CVE Import tool not to load.
This only impacted preview builds and did not ship to production.
Improve the product search function in the Publisher to keep the search box open when no match is found.
Scriptrunner has improved logic for handling the log location for user-based installations. If the default values are left in the Publisher, the log path will be updated to a user-writable location. This includes the scriptrunner log and the installer log.
Updated Publisher settings backup retention to retain settings from previous weeks and months.
Update the Swedish translation for Manage Conflicting Processes based on customer feedback.
The test email for SMTP configuration had a blank subject and body.
Fixed a bug causing the Manage Assignments form to hang while resolving Entra group names in some scenarios.
Fixed a bug where the Publisher would include non-Windows applications in the scan results for Intune auto publishing.
Fixed a bug that caused webhook summary notifications not to respect the tenant filter.
Fixed a bug that caused the Publisher to attempt to code sign Patch My PC defined scripts when the code signing option was disabled in the Publisher.
Fixed a bug that caused the install time offset for Intune assignments to be displayed incorrectly in some cultures.
Fixed Danish translation for Manage Conflicting Processes.
Imported banner images are stored in the installation directory of the Publisher instead of referencing the source file.
Removed the references for the SSRS reports and replaced them with Advanced Insights.
If configured to Kill or Notify, the tooltip and icon are removed
If configured to Skip, the icon is shown, and the tooltip says, “Manage Conflicting Processes is recommended for this product and will be configured to Skip by default”
If configured to ‘Perform the installation,’ the icon is shown, and the tooltip says, “Manage Conflicting Processes is recommended for this product but is currently not configured”
Improve how we search for ConfigMgr application content.
Expand out aggregate exceptions when they are logged.
Improved user experience both for a disconnected cloud configuration and an empty custom app list.
Custom Applications are supported in the ConfigMgr apps, Intune apps, and Intune updates tabs.
The Publisher must have ‘Install preview builds‘ checked in the About tab.
A license with one of the below subscription levels is required.
Enterprise Plus
Enterprise Premium
MSP
Implement a safety check prior to deleting a ConfigMgr application. In some instances, the SMS provider returns an empty list of apps instead of a connection exception. To account for this we ensure at least one Site is returned by the SMS provider prior to application deletion.
ConfigMgr script size is reduced. No functional changes. This should help with metadata download issues over CMG.
Add support for the ? wildcard character in detection.
The logging path for Intune Manage Installation Logging incorrectly defaulted to the ConfigMgr path. It is now corrected to the Intune default path for logging.
For some sync schedules, the ‘Next Sync’ time displayed in the General tab was in UTC instead of local time. The correct time should now be displayed.
Use CSV-based reporting endpoints for detected software per-computer.
This should prevent 429 responses when getting the list of devices with an application.
WMI connection test to SMS provider prior to deleting ConfigMgr content.
The list of Intune assignment filters is now filtered to Windows.
Fixed a bug where in some scenarios the republish flag would not be removed after a sync.
Fix a possible null reference exception when loading assignments for bulk delivery optimization edits.
Fixed a bug where the custom logging path maybe reset to defaults instead of inheriting the expected value.
Fixed a bug where the option to abort an uninstall if the prescript failed caused an argument parsing exception.
Fixed a bug where the automatic backup of setting changes would fail in certain cultures due to a date-time parsing issue.
Fixed a bug where custom naming conventions were copied between tabs. We no longer copy naming conventions when copying products between tabs.
Fixed a bug where PatchMyPC Scriptrunner logging did not use an invariant datetime format. This could cause CMTrace to fail to parse the logs.
This is to help troubleshoot when icons for applications are not deleted.
Idea: PATCHMYPC-I-1348
Extract content from ConfigMgr applications.
Extract content from WSUS updates.
Allow any app to have ‘conflicting processes’ configured
Idea: PATCHMYPC-I-1699
Fixed a bug where settings could not be saved if the internet was unreachable.
Fix some typos 🙂
Idea: PATCHMYPC-I-1871
Webhook Provider:
Slack or Teams is now selectable per webhook allowing the customer to send notifications to both based on their needs.
Notification Level:
All
Error
Success
Notification type:
Update notifications
ConfigMgr app notifications
Intune app notifications
Specific product
Scope a webhook to a specific product, such as notifying the network team of VPN application updates being published.
Specific tenants
If using multi-tenancy, you can specify the tenant a webhook is scoped to.
Allow variables to be used to customize the ConfigMgr application name and localized application name. This provides parity with the Intune feature for customized names. Variables available are below.
%VendorName%
%ProductName%
%Version%
%OriginalName%
ConfigMgr application retention now has the option to remove Administrative Categories from retained ConfigMgr applications.
Idea: PATCHMYPC-I-2181
ConfigMgr security scopes now have the option to enforce the selected scopes. The Publisher will remove all non-selected scopes from the application when Publisher.
Idea: PATCHMYPC-I-2328
Allow any product to have Manage Conflicting Processes configured
Idea: PATCHMYPC-I-1699
The code used to generate the template has been refactored to simplify future changes.
PatchMyPC-Scriptrunner will now factor in the major version filter when available when searching for uninstall strings. This improves the accuracy of uninstalls in some cases.
Added tooltips to some right-click options that describe why they are disabled in some cases.
Improved the error handling within the Intune Assignments forms regarding permissions for managing Assignment Filters.
Format the dates using ISO 8601 formatting when doing the Intune App export for PowerBI reporting. This improves international support.
Improved the accessibility of the WSUS Options form.
Improve error messaging and logging for unhandled exceptions.
Fixed a bug where failing to copy additional files did not cause an Intune product to fail to publish.
Fixed a bug where localization files for Manage Conflicting Processes may not be copied correctly in some cases.
Fixed a bug where the WSUS Options window was not scrollable.
Fixed several UI navigation bugs on the main form.
Adjusted encoding of detection and requirement scripts to use UTF8. Some scripts were failing to sign with the previous encoding.
Fixed a bug where the Manage Conflicting Process Organization Name was not retained when republishing a ConfigMgr application
Right-click options are now accessible via the Apps keyboard button or shift-F10
When a default Patch My PC provided translation exists for a language selected in Manage Conflicting Processes it will now automatically populate the text upon adding the language.
Fixed a bug where the Publisher would leave behind an empty folder when Publishing a ConfigMgr application and the download fails.
Fixed a bug where a version number would be appended to the current ConfigMgr application instead of the retaining application if the download fails. This bug affected customers who had the ‘Do not include version…’ option configured as well as the ‘Retain…’ option.
Fixed a bug where the Intune auto-publishing may fail in some cases when right-click options are configured.
Requires Enterprise Plus
Allow per-tenant branding for Manage Conflicting Process
Applies to Multi-tenant private preview
Fixed a bug where ConfigMgr app retention setting right-click option is not checked when configured
Fixed a bug where the Updates (WSUS) tab could be used while on an Intune license
The email report now converts size to a readable format such as MB or GB instead of bytes.
Idea: PATCHMYPC-I-1331
Support for Intune Filters
Idea: PATCHMYPC-I-1434
Requires Enterprise Plus
Fixed the Collect Logs button so it takes into account custom log paths as defined in the Publisher.
Fixed a bug causing enter to close the group search form for Manage Assignments when in the group input textbox.
Fixed a bug where the Manage Conflicting Process UI may fail to identify conflicting processes causing it not to show.
Fixed a bug where the Manage Conflicting Process UI may default to a 5-hour timeout for ConfigMgr applications in some scenarios.
Fixed a bug where delayed ConfigMgr applications may publish one day early.
Fixed a bug where the IsFeatured flag would not be set for a republished Intune application.
Fixed a bug where the Publisher would fail to validate a ConfigMgr source path if there were Deployment Packages with an empty source path.
Fixed a bug where the Publisher may delete a content folder during republishing if the binary was missing from the local content repository.
Fixed a bug where the Manage Conflicting Process UI notification would fail to display if the user DateTime format and the system DateTime format were conflicting, causing DateTime parsing failures.
Fixed a bug where the Manage Conflicting Process notification timeout setting may not be read correctly from settings.xml.
Fixed a bug where conflicting process notification timeout setting was not being read properly from settings.xml causing the setting to not apply.
Fixed a bug where the republish ConfigMgr application feature would not validate the hash of existing additional files which caused edited files to not be copied during a republish.
Fixed a bug where republish ConfigMgr application would not set the expected OS requirements.
Fixed a bug where ‘Override manual assignment changes’ is checked for an Intune product, and there is an ‘exclude’ assignment which would cause the Publisher to fail to process all assignments.
Fixed a bug where publishing would proceed even if a custom script failed to be processed.
Fixed a bug where the Publisher would run a sync every time ‘Apply Changes’ is clicked and the schedule is set to hourly.
Fixed a bug where ConfigMgr applications would be revised every sync when the Manage Conflicting Process option is set to an option other than ‘Notify’
New option to use ‘maximum run time’ from the respective update or app.
ConfigMgr Update Max: Will use configured update ‘max run time’ as configured in ConfigMgr for the update.
Note: Update max run time must be edited before the update is deployed for a client to recognize the change.
ConfigMgr App Max: Will use the configured deployment time ‘max run time.’
Intune App/Update Max: Will use the maximum run time of an Intune Win32 app (60 minutes minus the 15-minute buffer).
Idea: PATCHMYPC-I-1516
Send an alert if the Publisher failed to auto-update.
Idea: PATCHMYPC-I-1254
Send an alert when the Publisher is updated
Idea: PATCHMYPC-I-791
Add time zone to Teams/Slack Webhook notification
Idea: PATCHMYPC-I-856
Split out notification settings to allow Error notifications and Information notifications to go to different webhooks
Idea: PATCHMYPC-I-1536
Fixed a bug where the alert webhook configured for Slack may revert to a Teams webhook causing malformed messages.
Log current working directory in PatchMyPC-ScriptRunner.log
Idea: PATCHMYPC-I-1504
Export the list of enabled products and their right-click configurations to a CSV. This option is available in the Advanced tab of the Publisher. Only enabled products are exportable.
Publisher will validate the ConfigMgr application source path. A path is considered invalid if it is not a UNC path, or if the path is in use by a Software Update Deployment Package. Existing invalid configurations will not be impacted, but there will be an alert via email or Teams if alerts are enabled.
Idea: PATCHMYPC-I-1299
Idea: PATCHMYPC-I-550
Manage Conflicting Process settings also apply to uninstall. This ensures that a user will be prompted to close software for the uninstall as well.
Idea: PATCHMYPC-I-1430
Allow multiple webhooks so alerts are posted to multiple endpoints.
Idea: PATCHMYPC-I-1301
MSI uninstall performed by Scriptrunner will append REBOOT=ReallySuppress to the uninstall command.
MSI uninstall performed by Scriptrunner will generate an MSI log file if logging is configured for the application in the Publisher.
Idea: PATCHMYPC-I-1492
The Show Package Info wizard will now show the file size from the catalog.
Idea: PATCHMYPC-I-1461
Script Version: 3.1
Fixed a bug where double-clicking an item in the Intune App Manager would cause an ‘Index out of Range’ unhandled exception. This now opens the Manage Assignment wizard as expected.
Fixed a bug where ConfigMgr applications with only user-based deployment types would have the checkbox set to allow installation during a task sequence, which is not allowed.
Fixed a bug where the UI notification log file may not be created if the folder does not exist.
Intune app manager will filter by PMPC published apps by default, providing a drop-down to select non-PMPC or all apps.
Can be disabled with a registry key as noted here.
Idea: PATCHMYPC-I-1420
Notifications are presentation mode aware
Idea: PATCHMYPC-I-1248
Retain N-X apps in ConfigMgr when set to ‘Update existing application…’ is enabled.
Idea: PATCHMYPC-I-1265
DeviceManagementRBAC.Read.All
Idea: PATCHMYPC-I-1029
Script Version: 2.7
There are new settings available in the ‘Intune Options’ which allows you to specify retention for Intune Applications and Intune Updates. The valid values are between 0 and 10.
Idea: PATCHMYPC-I-967
InstallPackage as the default behavior for ScriptRunner
When the PatchMyPc-ScriptRunner.exe is double-clicked it will default to searching for package.xml in the same directory and performing /InstallPackage which allows PMPC application install to be launched without running them from the command line.
Idea: PATCHMYPC-I-1170
Apply Intune naming convention to existing applications and updates during a Publisher sync
Idea: PATCHMYPC-I-1175
Set ‘Featured App’ flag on Intune apps via right-click options
Idea: PATCHMYPC-I-1188
Renamed to: Add/Manage pre/post scripts
Patch My PC defined pre/post update installation scripts
Renamed to: Patch My PC defined pre/post scripts
Fixed a bug with the new Log Retention feature of Script Runner where it may unnecessarily trigger an ‘Update Content’ on ConfigMgr applications.
Requires updated App Registration Permissions.
DeviceManagementServiceConfig.ReadWrite.All
Idea: PATCHMYPC-I-673
Support for MSP Patching via Intune.
Idea: PATCHMYPC-I-1147
ScriptRunner will use QuietUninstallString when found for application uninstallation.
Idea: PATCHMYPC-I-930
Filtering options updated.
The ‘Exclude from auto-enroll…’ option now exists for Intune Apps and Intune Updates.
Scan Wizards will now automatically allow vertical scrolling if needed.
Implement a retry when performing some ‘POST’ operations to Microsoft Graph to improve Intune Win32 app creation reliability.
Fixed a bug where the ConfigMgr ‘Recreate Detection’ option would not set the VersionInclude for the newly generated script.
Idea: PATCHMYPC-I-985
TheSSRS report dashboards now include a parameter for Deployed.
File Name
Command-line
Download URL
Digest
Idea: PATCHMYPC-I-828
General UI improvements such as tooltips, alt-shortcuts, empty field validation.
Idea:
Note: We still need to add user-based software to the catalog, but the publisher now has support for this so that we can begin adding some user-based software.
Option to not append the republished date tag to republished updates.
Idea:
This is now a configurable checkbox in the advanced tab.
Intune Scan Wizard now has the option toautomatically enable Intune Updates based on scan data.
SMTP port automatically set to 587 when ‘Use TLS’ is selected, and to 25 when ‘Use TLS’ is unselected. The port can still be manually edited to account for any port, but the common port for the protocol is set by default.
Split the «Delete Intune Application when a new release is published» option to allow to choose the behavior for Apps and Updates independently.
User voice idea
Download timeout is now logged out in minutes and seconds, instead of milliseconds.
Implement log rollover for Intune detection and requirement scripts.
Send an MS Teams message and add a line in the Email report if the server runs low on disk space on the PMPC installation or the Wsus Content drive.
Support for the Contains string operator when searching for an AAD Group.
The Publisher will notify the user if the installation drive is running low on disk space.
The Publisher will notify the user if the Publisher is installed on the Site Server, and the server is not also a Software Update Point.
Tooltips added to buttons on Intune Apps and Intune Updates tabs.
When several files with the same name are found in the Local Content repo, and subdirectories, we try to identify the right one with the expected digest before falling back to downloading.
User voice
Deprecate WSUS v3
User voice
Web domains of downloaded icons are listed in the DownloadHistory.csv file.
Added several help links in the UI.
Improved logging for known errors linking to KB articles
Changes
The option to fallback to ConfigMgr package publishing when an application can’t be published as an SCCM application has been removed in the UI due to not being needed
SQL query default timeout is now 90 seconds from 30 seconds.
Removed from the UI the option to generate a CSV file with publishing info. The option is always enabled and the file path can be configured with the registry settings : HKEY_LOCAL_MACHINE\\SOFTWARE\\Patch My PC Publishing Service:PublishingHistoryCSVFolder
Fixes
Fixed an issue where the WSUS Maintenance for unreferenced updates would not return folders when the name is longer than 80 characters
Fixed an issue where file coping during publishing would fail when a file is referenced more than once (e.g., in additional files and pre-command script)
Add email, teams, and logging notifications when an update cannot be revised.
Add support to auto-popular the uninstall command line for 25+ applications in SCCM
Improvements
Improved logging for varias actions including download percentages
Allows searching backward for products and vendors when clicking
(Shift+F3)
Remove leading and trailing spaces in catalog URL, sms provider server name, application source folder path, and timestamp server URL
Add newadvanced options to improve SQL queries for large organizations.
Improve the version comparison in the PowerShell detection method script
Distribution point groups containing apostrophe were ignored during distribution
Various bug fixes
FullyQualifiedErrorId : UnexpectedToken
CScriptHandler::DiscoverApp failed (0x87d00327).
Deployment type detection failed with error 0x87d00327.
The select application folder dialog may crash when SmsProvider name is empty are unreachable
The select application folder dialog may try to connect to SMSProvider with a username and password even if the checkbox is unchecked
Added an option to configure the "Install Application Task sequence setting" in the Application Rules options. Based on customer idea: Change Install Application Task sequence setting during creation
Added an option to not include the version number in the application name. Based on customer idea: Application creation: applications without version numbers
Changes
The installed version of the publishing service and whether you have opted into the preview channel will be reported.
SketchUp
Skype
TeamViewer
Telerik Progress TestStudio Ultimate
VMware Workstation
VMware Workstation Player
VMware Workstation Pro
VirtualBox
WinZip
Fixes
Miscellaneous fixes
Miscellaneous Bug fixes
Alert notifications
Low disk space, certificate expirations, license expirations etc.









