• Welcome to Support Forum: Get Support for Patch My PC Products and Services.

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Pepper

Google Chrome 83.0.4103.61 is failing to install with 0x80242006

I am also noticing occasionally SCUP cannot automatically download the catalog file, and I have to download and then import it manually. Today, when that happened, I also noticed the four variants of K-Lite Codec had a certificate that was "unknown" and couldn't be marked as always trusted.
Interesting. I am not specifically using SCCM or your Software Center as shown in your picture. Does SCCM invoke the standard Windows Update under the covers, or is it doing something else to get the updates installed? My issue is happening when running Windows Update on the client PC.

My environment is using SCUP (6.0.394.0) to import the updates from the catalog, and then WSUS Package Publisher (1.3.1702.10) to approve them. I believe this "used to" be the recommended way to use the PatchMyPC catalog - or possibly it was how I initially did the Adobe catalogs and then added yours into it, it continued working up until now, and I have been too busy/afraid to try your newer more automated method.

Edit: I was pretty sure this was a Windows 2004 issue, but *just this morning* I have discovered a Windows 1909 machine that is having the same issue with Dropbox 95.4.441 so I am thinking it must be something else but it doesn't occur on all updates. Other updates I have found are Adobe Flash Player 32-bit/64-bit Plugin and Adobe Acrobat Reader DC Update 20.006.20042 (Adobe updates from their catalogs not yours).

Also seen failing on 2004: Apple Mobile Device Support (x64); Apple iTunes (x64); Apple Application Support 8.4 (both)

I just installed an old iTunes x64 on a machine running 1909, it updated to successfully, that same update fails on my machine running 2004.

I am thinking that instead of "All Updates fail on All 2004 OS" this may actually be "Some Updates fail on 2004 but work on earlier OS"

I will keep my eye out and see if others are found, it may be something in the update properties. The next one of yours that I can get to consistently fail on 2004 but succeed elsewhere*, I will let you know. *iTunes
Thanks, I am of course up to date on Windows, and am still seeing that issue at 19041.207 which Microsoft intends to be the public release in a few weeks from now, according to this: https://blogs.windows.com/windowsexperience/2020/04/16/getting-the-may-2020-update-ready-for-release/

I also have opened a ticket with Microsoft as detailed in that blog article, and I noted someone else has the same issue and has reported to feedback hub: https://aka.ms/AA88ggw

This might not be the right subforum, and yes I realize that version 2004 is still pre-release.

All updates imported to WSUS from the PatchMyPC catalog seem to be failing with a "Download error" in Windows Update. I have verified that this issue is happening only on version 2004 (build 19041) and not on the previous versions.

I do believe it's a Windows issue, as I'm seeing the same issue with updates imported from the Adobe Flash and Reader catalogs. So technically it's not "your fault." But...

- Are you working with Microsoft to get the issue fixed?
- Is there anything I can do to assist?
- Is there any workaround that you know of other than downloading and installing the updates manually?
- Maybe it's a new "security" feature and something needs to be toggled in the registry to allow updates from 3rd party sources?
Thanks, the new version seems to be installing.
So it looks like you "fixed" the issue on the 25th by excluding Windows 10 entirely, not just build 17763 and above (1809).

Also it looks like you misspelled "icloud.exe" as "icould.exe" in one of the rules.
Current version(s) of iCloud will not install on Windows 10, version 1809. Probably should add a check for build < 17763 until they release one that will install properly.
This is the same issue I was seeing with the OCZ SSD utility, back when I reported that one. I don't know if it ever worked correctly because I stopped importing and approving those.
On the machines I deployed this update to, it stuck at 0%, blocking other updates indefinitely, until I expired it and restarted the client.
Archived Feature and Product Request / OCZ SSD Utility
November 14, 2017, 11:38:46 AM
This is a little program that sits in the taskbar and monitors the health of Toshiba OCX Solid State Drives. At first I considered it optional but on one of the two systems I actually installed it on it is noting less than 100% health so I want to install it on all of them, therefore adding to SCUP would be nice.

This is the page the user gets taken to when there is a newer version available of the utility.


I have an older version I can install on some machines for testing when/if it's added to the catalog.

Malwarebytes in latest catalog released 8-27-2017 fails hash check on download.

Also, why is Foxit PhantomPDF in the PatchMyPC products group when there is already a Foxit group?
I can answer this in case you want to reconsider.

These products use a subscription based license, as long as it has not expired installing a new version will work.
Thanks, I thought my app had broken.
OK, just to confirm, here's what I did.

- In SCUP, go to "All Software Updates" and sort by date published.
- Select all non-expired updates with a published date older than when I replaced the certificate.
- Click Publish, tick the box you showed me which I had never noticed was there before, and then just wait a while for it to do the job.

That should take care of it, and after it's done it would be safe to remove the old certificate from my Group Policy, correct?