Messages

If you are experiencing this issue I would encourage you to submit a support case so we can look into what might be happening.

https://patchmypc.com/technical-support

If do you remove the Adobe and HP catalog I would recommend you decline the updates for them as well to ensure they are not scanned against by clients anymore.

Is this issue for all clients? Or are you noticing it on clients over the CMG / IBCM?

There is generally not anything special going on specifically for third party updates. We have seen this delay happen though if you also have the Dell, Lenovo, or HP driver catalogues in place. They have very complicated applicability rules and can greatly increase CPU load / scan time.

Sorry about that!

Logs https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#update-troubleshooting-client-logs

Ticket https://patchmypc.com/technical-support

Hello,

Can you please submit a support ticket here and please zip up and include the logs mentioned here.

This should help us identify what is going on for detection.

Hello,

These are different 'major versions' of the software. We should be able to add 7, but I would encourage you to add it as a requested application on our uservoice.

https://ideas.patchmypc.com/

We have to do some work to determine how to detect version 6 vs. 7. The registry entries and files are very similar between the two, oddly enough...

For Task Sequences, you would likely want to set the below two options.

https://patchmypc.com/application-creation-options#topic1

and

https://patchmypc.com/base-install-update-options-explained#topic1

The first link discusses the option which will ensure the checkbox is set to allow the application to be installed during a task sequence without being deployed.

The second link shows the option to always use the same application, and just update metadata (the default option).

Outside of that, any per-product configurations are going to be up to the businesses needs.

Can you open a support case here https://patchmypc.com/technical-support

and provide the log files described here

https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#update-troubleshooting-client-logs

Are you able to validate that WebEx Teams is downloaded in SCCM, and part of a deployment package that is distributed to Distribution Points your clients are associated with?

Hello,

This should be resolved! If you opt into preview builds in the about tab of the publisher, and upgrade to 1.9.2.3 you should be able to delete your .NET Core Runtime apps / updates and then recreate them.

Let us know if things don't work as expected with this.

Feel free to opt out of preview if you'd like once this is done.

Hello,

We have made progress on this. We were able to solve the detection pretty quick, but it exposed some other issues around having to split up version 2 and 3 .NET Core Runtime.

I think we should have this complete by the end of next week at the latest.

Hey there,

We are working on resolving this one. Unfortunately Microsoft has the display version in the registry as a completely different version, such as '24.80.28821' so we are discussing how to handle this scenario.

We will let you know when this is resolved.

Hey there,

We are working on resolving this one. Unfortunately Microsoft has the display version in the registry as a completely different version, such as '24.80.28821' so we are discussing how to handle this scenario.

We will let you know when this is resolved.

Hello,

The EXE version of Wireshark should now detect as expected. You will need to delete the application from Intune, and then run a Publisher sync to recreate it with an updated detection method.

Just to be safe, you can also uncheck Wireshark as a product, apply settings, then re-check Wireshark, and apply prior to running a sync.

Let us know if it doesn't work!

Yeah, I figured you understood 

It is a frustrating experience for us as well. Most vendors, by a large margin, do not give us these hash mismatch headaches!!