Messages

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!

Hello,

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

Hello,

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!

Best,

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.

https://patchmypc.com/known-issues-and-considerations-when-using-patch-my-pc#:~:text=by%20another%20process.-,Products%20with%20Known%20Dependency%20Requirements,-The%20following%20products

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:

%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

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]:

%PatchMyPCInstallDirectory%\PatchMyPC.log
%PatchMyPCInstallDirectory%\PatchMyPC*.lo_
%PatchMyPCInstallDirectory%\Settings.xml
%PatchMyPCInstallDirectory%\PatchMyPC-DownloadHistory.csv
%PatchMyPCInstallDirectory%\PatchMyPC-PublishingHistory.csv
%SCCMInstallFolder%\Logs\SMSProv*.log

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:

https://patchmypc.com/intune-apps-vs-intune-updates

Hello,

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:

%ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-ScriptRunner.log
This may be found in the %ProgramData%\PatchMyPC\ if the Install was initiated by the user from Company Portal.
%ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-SoftwareDetectionScript.log
%ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-SoftwareUpdateDetectionScript.log
%ProgramData%\Microsoft\IntuneManagementExtension\Logs\AgentExecutor.log
%ProgramData%\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log
%ProgramData%\PatchMyPC\PatchMyPC-UserNotification.log
%ProgramData%\PatchMyPC\UISettings\UINotificationSettings.xml

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:

https://github.com/PatchMyPCTeam/CustomerTroubleshooting/blob/Release/PowerShell/Export-PMPCInstalledSoftware.ps1

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\CAS*.log
%WinDir%\CCM\Logs\DeltaDownload*.log
%WinDir%\CCM\Logs\DataTransferService*.log
%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.
%WinDir%\CCM\Logs\ScanAgent*.log
%WinDir%\CCM\Logs\StateMessage.log
%WinDir%\CCM\Logs\UpdatesDeployment*.log
%WinDir%\CCM\Logs\UpdatesHandler*.log
%WinDir%\CCM\Logs\UpdatesStore*.log
%WinDir%\CCM\Logs\WUAHandler*.log
%WinDir%\WindowsUpdate.log
You need to run Get-WindowsUpdateLog on Windows 8.1 and newer in PowerShell.
%ProgramData%\PatchMyPC\PatchMyPC-UserNotification.log
%ProgramData%\PatchMyPC\UISettings\UINotificationSettings.xml

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:
https://ideas.patchmypc.com/

Hello, and thanks for reaching out to support! I have forwarded this inquiry to our Advanced Insights team for review. Once they've had a chance to review your request, they will respond with further instructions!

Thanks for your patients!

Got it, thank you for clarifying that! Can you please send me the following log files from that client machine. You can email them to [email protected] if that's easier!

%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


I'll also test this in my lab and see if I can repro this issue.

Are you deploying the update or application package for docker? It sounds like the client is pulling the content from another machine using Delivery Optimization or Branch Caching.

Can you confirm that the WSUS signing cert is not expired and is present in the clients Trusted Root and Publisher machine cert stores?