Messages

Ah I see, I don't believe this is a supported product, is this a Custom App you have created?

We will need a few more things from you so we can troubleshoot this issue.

Can you send the log files listed below to [email protected] with the subject "Charles Proxy install issues"?


    %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

Hi,

Are you referring to installing the Patch My PC tool here? Or is this for an app that was created by our publisher?

We would need some more information here to determine what's going on.

Thanks,
Antony

Hi,

Unfortunately the conflicting processes feature is added into the package and it's not possible to have a silent uninstall if the feature is configured to produce a notification when the process starts.

The only way to do this would be to disable the feature and republish, but then you'd need to re-add it for the notifications to appear again after the uninstalls have been completed.

Let me know if you have any other questions.

Thanks,
Antony

Cisco released a new version of Webex Meetings over the weekend, the same version was actually released at different times for the US and Europe which is why some customers are seeing the hash error.

This will be updated in today's catalogue release.

Thanks,
Antony

Hi Paul,

Thanks for reaching out!

Can you please send the logs listed below over to [email protected] so we can investigate this issue?

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

Once we have these logs, we can look into why this issue is occurring.

Thank you,
Antony

Hey Ben,

Thanks for reaching out. Unfortunately, there isn't anything similar in the works for enterprise environments, this is mainly due to there being no central point to manage the apps and updates. Every device would require their own installation and then it relies on the end-user to keep the machine up to date, which for management and compliance purposes could prove difficult.

I hope this provides some clarity here, please let me know if you have any further questions.

Thanks,
Antony

Good Morning,

Could you please send an email to [email protected] detailing the issue and attaching the logs listed below from an affected device? We can then investigate this issue further.


    %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

Thanks,
Antony

For the apps/updates that failed, can you please confirm you have the latest version of the installer file in your local repository?

These are local repository apps which require you to manually download the installer file and place in your local repo which is specified in the "Advanced" tab of the publisher, more info can be found here - https://patchmypc.com/local-content-repository-for-licensed-applications-that-require-manual-download

Thanks,

Antony

Hi Afeiner,

Could you please provide some more clarity here. Are the applications failing to publish or install?
Also is this for Intune or SCCM?

Thanks,

Antony

Apologies, you will want to choose the options to immediately expire the updates.

Hello,

The automatically decline superseded updates is not something you can configure within the publisher. This can however be set in the Software Update Component Properties within the SCCM console itself, head to the Supersedence Rules tab and configure as shown below in the attachment on my message.

I hope this helps.

Thanks,
Antony

Hi Cliff,

Sorry for the delayed response.

Could you please raise a case to [email protected] and provide the relevant logs from the following link then we can take a look at what might be happening here - https://patchmypc.com/collecting-log-files-for-patch-my-pc-support

Thanks,

Antony

Hi!

Is there any additional command line arguments you use when manually installing which helps retain the settings?

I know the config files are usually stored in this location - C:\Program Files (x86)\Fortinet\FortiClient>. Can you check to see if this file is still present?

Thanks,
Antony

Hi Arjan,

Since you raised the post we found a bug in our detection logic due to FileZilla changing the naming convention of the product in the latest version. This has since been fixed and will now work as intended moving forward.

Have a great day!

Antony

Could you please send the logs listed below from one of the affected devices over to [email protected].


    %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

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