Messages

Just wanted to highlight that Cisco Webex is failing to update, giving a hash error same as last time (https://patchmypc.com/forum/index.php?topic=7566.0)

Cisco Webex Meetings 44.4.0.159

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:[0K1ab9d40nkYni8aAK+DRd5u6aU=] vs [vf7Bt7gvdyd8jx1AmIPpq9Hd6b0=]

Apologies for not getting back sooner.  It turns out we had a complicated-to-work-out issue with our security scanner with these patches. We are good to go with using the .NET security patches made available within MECM and don't need a PatchMyPC solution.

This topic was marked complete, but feel there was more discussion to be had:
https://patchmypc.com/forum/index.php?topic=6833.0

.NET Core 7 updates are not part of SCCM or in MS catalog.  In the previous topic, a comment was left pointing to the Microsoft Catalog with this link: https://www.catalog.update.microsoft.com/Search.aspx?q=.NET

But that only shows updates for .Net Framework and .NET clients.  Neither of these update .NET Core.

Just posting this additional information for consideration to include .NET 7 Core in the PatchMyPC catalog.

The clients seem to update fine through SCCM and match what's listed in the catalog, but anything with .NET 7 Core doesn't seem to have a corresponding update.  We've had to manually patch them.

Am I right that .NET Core 7 can't be updated through SCCM? 

If that's correct, are there plans to do this through PatchMyPC? Especially since updates don't seem to remove previous versions from the device?

Yikes about their response!  Thanks for trying to work with the very unprofessional vendor.  Was wondering why we weren't on the latest version.

Okay, so the 2015-2019 should probably get removed from PatchMyPC? 

I see that there are two Microsoft Visual C++ Redistributable Package in PatchMyPC:

Microsoft Visual C++ 2015-2019 Redistributable Package 
Microsoft Visual C++ 2015-2022 Redistributable Package

In ConfigMgr the 2015-2022 version is currently 14.34.31938.0 and released earlier this year on 2/16/2023, while the 2015-2019 version 14.29.30139.0 was last updated on 1/13/2022.  Has the 2015-2019 version been replaced by the 2015-2022 version and should no longer be used?

We're probably just going to revert to an older version of Adobe Reader and continue deploying updates to get it up to the latest version. The manual method is too cumbersome to keep up with.

This is what we're doing right now as well. Thankfully we have set the retention settings to keep the old versions!

Which version did you go with?  We're still having trouble with it for some reason, but probably just need to go further back.

The last working version we got from PMPC was "Adobe Acrobat Reader DC 22.002.20191" - we have it deployed to collection(s) and in task sequences, where it seems to be working fine.

22.003.20258 and 22.003.20263 are both not working in task sequences - haven't dared to deploy them to collections yet.

Yep, that one worked!  We're just going to use this as a solution for now.

Thanks for the response, Andrew.  That provides a lot of context and deeper information than I've seen before.  That's very useful.

Yes, nice to see these details. Much appreciated.  Hopefully Adobe can be helpful in working this out.

We're probably just going to revert to an older version of Adobe Reader and continue deploying updates to get it up to the latest version. The manual method is too cumbersome to keep up with.

This is what we're doing right now as well. Thankfully we have set the retention settings to keep the old versions!

Which version did you go with?  We're still having trouble with it for some reason, but probably just need to go further back.

We're probably just going to revert to an older version of Adobe Reader and continue deploying updates to get it up to the latest version. The manual method is too cumbersome to keep up with.

We're also experiencing this issue.  Adobe Reader will install successfully through configuration manager, but will fail as part of a new image task sequence. 

The task sequence failed to install application Adobe Acrobat Reader DC 22.001.20117 for action (Install Application) in the group () with exit code 16389. The operating system reported error 2147500037: Unspecified error.

We tested with the 64-bit version and same issue.

Was hoping someone from PatchMyPC would have chimed in by now as I've seen recent responses to other threads.  The Reddit article posted earlier doesn't quite match what we're seeing.