• 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)

Hey Gary,

Just tested this in my lab by updating AnyConnect 4.8.0 to 4.10.0 (Latest) using our ConfgMgr Application package which was successful.

I'd be interested to look into the logs and see why this may be failing for you!

If you could please send us the following log files from one of those failed clients. You can email them to [email protected] or [email protected]


Updates: https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#publishing-service-logs
Applications: https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#publishing-service-app-logs


Hey Gary,

Thanks for reaching out here on the forum!

What I can suggest here is adding this uninstall script as a Pre-Script to remove any older versions of AnyConnect before installing version 4.10.


I'll have to test the updates myself to see if there is a better solution, but that should at least help you out when trying to upgrade! 😊

If you have further questions or would like to open a support ticket, please email [email protected] and we can assist further!
Hey Dan,

Thanks for reaching out on the forum!

The way we handle our updates via Intune is by adding a Requirement script that will run first before the update is installed.

That script will first check if the application is installed on the client, and then will look at the version. If the version is less than that of the update then the update will install.

If not, then it will continue on to the next update. Updates that are not applicable on clients will show as such in the Endpoint Console (Intune).

Here is a KB article that will explain how our Intune Packages work in more detail:


As for the deployments, updates can only be deployed as required deployments. So if you wanted to cover your bases, what you can do is deploy all updates to All Users or All Devices and they will only install on clients when needed.

Hopefully that helps you here! However, if you have further questions or need more clarification please don't hesitate to reach back out! 😊
Yep, if you send them to [email protected] that will come through to our internal support email and will be assigned to an engineer! We'll then work with you via email or if needed we can schedule a support call via Teams! 😊
Thanks for reaching out on the forum! If you could please collect the following client side log files and send them to [email protected] we can troubleshoot this further! 😊

When troubleshooting Intune 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 Company Portal.

Note: Some Patch My PC log files listed above may be found in %WinDir%\CCM folder if that folder exists.


Spencer Cruz
Thanks for reaching out on the forum!

I have reached out to our app devs to verify the supersedence chain for Edge. Just for reference, our supersedence chain only covers up to the last 10 versions of the product.

Based on the release notes for stable versions of Edge, version 109.0.1518.55 falls outside of the supersedence chain.

In the meantime, if you would like to decline the older version of Edge you can use the Modify Updates Wizard in the Updates Options menu:


Hey Alex,

I received your email with the logs yesterday and provided an update. Please respond back to that support email if you have further questions or issues! :)


Hey Fabian,

Thanks for the update, glad this issue has been resolved! I will inform our internal engineering team so they can assist other customers who may run into this issue as well.  8)


Hey Alex,

Thanks for reaching out to support!

I tried to repro this issue in my lab, however, was unable to do so. If you can, please send me the following logs from one of the affected clients:

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

- %WinDir%\CCM\Logs\AppDiscovery*.log
- %WinDir%\CCM\Logs\AppEnforce*.log
- %WinDir%\CCM\Logs\AppIntentEval*.log
- %WinDir%\CCM\Logs\CAS*.log
- %WinDir%\CCM\Logs\CIAgent.*log
- %WinDir%\CCM\Logs\DataTransferService*.log
- %WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log
     This may be found in the %ProgramData%\PatchMyPC\ if the Install was initiated by the user from Software Center.
- %WinDir%\CCM\Logs\PatchMyPC-SoftwareDetectionScript.log
     This may be found in the %temp% of the user who clicked 'Install' in Software Center if it was an 'Available' deployment.
- %WinDir%\CCM\Logs\StateMessage.log
- %ProgramData%\PatchMyPC\PatchMyPC-UserNotification.log
- %ProgramData%\PatchMyPC\UISettings\UINotificationSettings.xml

Can you also confirm that those ConfigMgr clients are updated or at least matching that of the Admin Console? You can updload the logs to [email protected] for review.

If you have further questions or issues, please let us know! 😊
Thanks, dhwatts for the info! I'm testing this in my lab now with both the EXE and MSI versions to see if there are any issues with the detection logic.

Please still send logs over for review, I will update with my findings as well!
Thanks for reaching out to Support! I took a look at the MSI log and all i'm seeing is the following:

MSI (s) (1C:84) [08:45:00:504]: Unable to delete the file outside of the engine. LastError = 2

This usually means "File Missing" - This could be a transform file that is in reference in the command line.

To better understand the issue, can you please send the following client-side logs to [email protected]:

Intune Logs:


SCCM Logs:


Once we have them, we'll update you with next steps! If you're unable to send the logs through normal email methods, then please upload them here:

One thing I wanted to add here! When using the following command line (/SKIPSTARTINGPOWERAUTOMATESERVICE) and if you're using Manage Confilicting Processes, please ensure that the option to "Prevent the end user from opening the application." is NOT checked. As this will cause the install to hang and fail.

More informations can be found here: https://patchmypc.com/manage-conflicting-processes-when-updating-third-party-applications

Awesome, glad the manual test proved successful! Once the new version is released (Should be in todays catalog) let us know the outcome! Fingers crossed; it should be the same as running it manually! :)