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

Show posts

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

Show posts Menu

Messages - Spencer (Patch My PC)

If multiple products are configured with that setting, then I would check at the top level (All Products) to verify if MCP is enabled there. If so, check to see if "Prevent Start" is enabled and disable it from there.

As for the use of that "Feature", I wouldn't enable it unless you notice a product trying to relaunch itself when the processes are closed. Some VPN clients do this to maintain their client connections. So, to ensure that the process doesn't restart, you can enable that feature.

Otherwise, I wouldn't even touch it as it does tend to cause issues if the PatchMyPC-ScriptRunner.exe process exits unexpectedly or times out and doesn't have enough time to delete that key after the update.

Hey Bugs,

Thanks for reaching out to support!

I would recommend checking the conflicting processes options on that application/update to ensure you don't have the option to "prevent the user from starting the process during installation" selected as that is what is causing these issues.

More information on that option and how to remove that registry key can be found here:

How to remove the registry value: https://patchmypc.com/manage-conflicting-processes-when-updating-third-party-applications#:~:text=by%20another%20process.-,Update%20in%20progress%E2%80%A6,-When%20the%20option

Overall information on MCP options: https://patchmypc.com/manage-conflicting-processes-when-updating-third-party-applications

Hey Matt,

Thanks for reaching out! Usually this is some type of networking issues. I would confirm that the SYSTEM account of the machine hosting the publisher has access through any firewalls or proxies being used.

You can also confirm that those vendor domains are not being blocked by referencing our Firewall list here:

We can also look into the log files from the Publisher. You can collect them from under the General Tab by clicking the "Collect Logs" button and send them to [email protected].

I'll review them and will provide any updates via email! :)
Oh interesting! I'll pass this along internally as it may have gotten lost in translation! We still need to update the msi to the latest version in the publisher to allow for publication, but this should prevent future delays!
Perfect, I'm sending this over to our app team now so they can get this added to the catalog! We should hopefully have it in there today or tomorrow for you!
Hey Rusil,

Thanks for reaching out on the forum and apologies for the delay in response!

In order to get more details on the errors can you please send me the publisher log file bundle by clicking the "Collect Logs"  button under the General tab of the publisher.

You can email them to [email protected] and CC: [email protected]

Once we have the logs we'll provide an update via email!

Thanks for reaching out on the forum! For those still affected by this, have you tried to redownload the latest version of the PMPC Publisher to see if that resolves any issues? Have you also tried running the portable version from another windows 11 device and do you see the same error?

Can you also try to run the DISM command to repair any corrupt files:
DISM /Online /Cleanup-Image /RestoreHealth

Thanks for reaching out on the forum! At the time of updating the EXE versions, the vendor didn't offer an updated MSI installer. If you have access to the installer, can you please upload that to https://patchmypc.com/share?

Once we have the binary we'll test it and upload it to the catalog! :)


Spencer Cruz
Hey Chrispe,

Thanks for reaching out on our forum! When deploying the package are you also including Bonjour as a dependency for iTunes? That is a requirement for our iTunes package and may be the reason for this issue.


If that still doesn't work, please send over the following log files to [email protected]

When troubleshooting ConfigMgr application installation errors on a client, we will need multiple client logs. Please include the following logs:

This may be found in the %ProgramData%\PatchMyPC\ if the Install was initiated by the user from Software Center.
This may be found in the %temp% of the user who clicked 'Install' in Software Center if it was an 'Available' deployment.
Hey Blanzeros,

Thanks for reaching out to the forum! When you enabled the option to "Disable Built-In Updater" did you run a publishing service sync to apply that setting to the application?

You can do this under the Sync Schedule tab in the Publisher by clicking on Run Publishing Sync Service.

If that doesn't work, please send me the following log files - [email protected]:

You're welcome, and glad I could help! Don't hesitate to reach back out if you need anything else! 😊
Hey Kotond,

Thanks for reaching out on our forum!

If you're only looking to update Webex and not make it available or required as an app, then you can just publish the update for Webex.

If you want the update to target all devices, then you can add that group to the Manage Assignments option!

All of our Intune Updates had requirement and detection scripts. So they will only install if the products are installed on the client, and if it's an older version of that product.

More information on the differences between Intune apps and updates can be found here:


Thank you for reaching out to support!

We publish the Enterprise Stable version of Edge and perform the following registry key validations when installing the application packages:

'SOFTWARE\Microsoft\EdgeUpdate\ClientState\{56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}' = 'ap'} = @{Value = '*stable*';WOW6432Node = $True; Operator = '-like'};@{'SOFTWARE\Microsoft\EdgeUpdate\ClientState\{56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}' = 'ap'} = @{Value = '*x64*';WOW6432Node = $True; Operator = '-like'};}

The full detection scripts for applications published by PMPC can be found in the PMPC Installation Directory inside the detection method scripts folder.

I recommend pulling that script and moving it to a client that's failing to apply the application to verify detection.

On that same client, can you also pull the following log files and send them to [email protected] with a description of the issue:

This may be found in the %ProgramData%\PatchMyPC\ if the Install was initiated by the user from Company Portal.

Lastly, can you please run this script on that same client? This will export a csv file containing all install products on that machine. This will also help us determine issues with detection:

Hello and sorry for the delay!

Can you please collect the following log files from one of the failing clients and email them to [email protected]? Once we have the logs, we can investigate why the 5.0 update is failing.

When troubleshooting update installation errors on a client, we will need the following client logs:

%WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log (If exist)
This may be found in the %ProgramData%\PatchMyPC\ if the Install was initiated by the user from Software Center.
You need to run Get-WindowsUpdateLog on Windows 8.1 and newer in PowerShell.

Hey there!

Just got word from our AI devs and this is what they stated:

 At this time there is currently no source of data at the server or way of harvesting from client logs where content came from during OS Deployment. A remote possibility is that the Status Message data may contain location data for downloaded packages/apps/drivers/images. This is something we'll have to look into and see if that data can be accessed.

In the meantime, I urge you to submit a uservoice item so our devs can track this request and keep you and other customers updated on the status! 😊

You can submit the request here: