Messages

Hey Mary,

This issue requires a detailed troubleshooting, and I would suggest you to raise a support case with us :https://patchmypc.com/technical-support

Also, I would also recommend you to review this page that talks around the same issue :https://patchmypc.com/applications-fail-to-install-during-osd-in-sccm-with-error-authorizationmanager-check-failed-0x87d00327

Regards,
Raunak

Hey Alice,

I understand your concern.

Can you please use this link to schedule a 30 minutes call with me so we can discuss this in details and get it sorted for you:https://calendly.com/pmpc-raunak/30-minute-support-session

Regards,
Raunak

Hey Jrapt !

That's definitely a good feature request. I would recommend you to raise it via our ideas page : ideas.patchmypc.com

Regards,
Raunak

Hey Bernard,

Yes, it's true for regular Windows Update Patches as well. You cannot see it in the company portal.

Company portal is just for the application. You cannot replace software center totally.

Regards,
Raunak

Hey Jpratt,

Thank you for reaching out.

The option "Delay the in-place application upgrade by" can only be applied on a Global level, not in app level.

When a new version of an application is released, delay the in-place application upgrade by...
When this option is checked all applications managed by the Publisher will have their creation delayed by the specified number of days. The delayed date is based on the date the new application version was synchronized by the Publisher.

For example, if Google Chrome was synchronized on February 3rd, and this setting was configured for a 3-day delay, you would expect to see the application be updated in Configuration Manager during a publisher synchronization on February 6th.

This feature will result in a logline similar to the below.

The updating of the SCCM Application... is delayed due to settings

Hope this helps.

Hey Watson,

With PMPC database scan wizard, you can scan the discovered app data from Intune and Hardware inventory data from SCCM.

The wizard will show you the list of 3rd party apps already available/installed on your endpoints. You can get details about the endpoints name and the version of app installed.

Note : The database scan wizard will also show the apps that are a part of our supported product.

https://patchmypc.com/supported-products
https://patchmypc.com/scan-intune-for-supported-products

Regards,
Raunak

Hey Rowan,

Let me check this internally with the team, and we will update you on this.

Regards,
Raunak

Hey JJS,

Thank you for reaching out to us.

Can you please confirm if we are talking about the company portal app or Software center.

Because, you cannot see an update entry in the company portal app. The entry you see is for the latest version of the app itself.

I would recommend you to raise a case with us so that we can check this thoroughly. https://patchmypc.com/technical-support

Regards,
Raunak

Hey Jon,

Thank you for reaching out to us.

PatchMyPc will be able to address those vulnerabilities and make sure that you devices are upto date with the latest version of the software.

I would recommend you to schedule a demo call with us and we will guide you with the entire process and how it benefits your environment and organization.

https://patchmypc.com/schedule-live-demo

Regards,
Raunak

We are looking for a long-term fix from our perspective, but I'd recommend keeping an eye on it after your subsequent monthly Microsoft OS cumulative updates.

Hey Will,

Recently, we have had a few customers reach out with the same issue you are experiencing.

We believe the issue comes from a Microsoft patch, released in October, that hardens Kerberos within your environment. Ultimately, when the Patch My PC service authenticates, it is likely receiving a ticket from a non-hardened DC.

I suggest reviewing all your domain controllers to ensure they are updated with all the patches released in October. Reviewing the Windows security logs on your SMS Provider will likely highlight this issue.

There are some helpful links related to this issue, which you can find here:

https://techcommunity.microsoft.com/t5/windows-it-pro-blog/latest-windows-hardening-guidance-and-key-dates/ba-p/3807832
https://support.microsoft.com/en-us/topic/kb5008383-active-directory-permissions-updates-cve-2021-42291-536d5555-ffba-4248-a60e-d6cbc849cde1
https://support.microsoft.com/en-us/topic/kb5020805-how-to-manage-kerberos-protocol-changes-related-to-cve-2022-37967-997e9acc-67c5-48e1-8d0d-190269bf4efb#registry5020805

Regards,
Raunak

Hey Trevor,

Thank you for reaching out.

For a test: Could you try to recreate the application to see if you have the same result?

If you receive the same behavior, please share the logs from one of the affected machines.

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

%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.

Regards,
Raunak

There is an on-going issue with Adobe's CDN where the following URL downloads a different file in some parts of the world:

https://ardownload2.adobe.com/pub/adobe/acrobat/win/AcrobatDC/2300620380/AcrobatDCx64Upd2300620380.msp

Analysing the files downloaded in the US compared with the UK seems to suggest both files are identical, however the non-US .msp file has an invalid digital signature.

They're both signed with the same code signing certificate by Adobe, so we don't believe there is cause for concern and it is likely a mistake in Adobe's release pipeline. It's unclear why the digital signature is invalid in the non-US file, however, in any case the SHA256 value is different between the two files.

As part of our security validation process built into the Patch My PC Publisher, all packages published must pass hash validation before publishing the package into your environment/tenant. As Adobe's CDN is distributing a different file globally, some customers may experience a failure publishing the product "Adobe Acrobat DC Continuous (x64)" with the below error in PatchMyPC.log, or email or webhook alerts:

The hash of file downloaded is different than the file hash in our catalog. Hash errors happen when vendors release updates that aren't available in our catalog yet. This error should be resolved in the next catalog update. It could also have been induced by a firewall issue. Additional details:Hash from catalog [62Xvv9aL+eg2kDtlpFvdgVoXWtU=] doesn't match downloaded update hash of [Z2tLMqHBX3N47QnuNwewYccuqTY=]

We have notified Adobe of the issue in a support thread on their forum: Invalid digital signature on AcrobatDCx64Upd230062... - Adobe Community - 14246103 - kindly upvote, comment, or if you have the means to, escalate this thread to an Adobe contact.

In the mean time, you can workaround this by downloading the correct AcrobatDCx64Upd2300620380.msp (with the valid digital signature) using the below link hosted on our OneDrive and publishing it using your local content repository. Please make sure you have the option enabled to "Check the local content repository for content files before attempting to download content files from the Internet."

https://patchmypc-my.sharepoint.com/:u:/p/adam/EVTWVpoDBuFAitz7oJd4Sp4BNPuhkrRbc2xm-oOY6Q6-aA?e=9HV9o9

Hey,

Thank you for reaching out to us.

You can request for that application to get added to our catalog via our ideas page : ideas.patchmypc.com

Hope this helps.

Regards,
Raunak

Hey Bjohn,

Also, can you please share the logs from one of the affected machine.

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

%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.