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?
We're not currently tracking this issue, but will set up a Windows 10 2004 system in our lab and see if we can reproduce. We'll keep you updated on what we find.
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 is excellent, we will work to reproduce the issue and try to get it on Microsoft's radar. Thanks again for bringing it to our attention!
I was unable to repro in our test environment. SCCM 2003 TP and Windows 10 2004.
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 126.96.36.1993 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 188.8.131.52 (x64); Apple iTunes 184.108.40.206 (x64); Apple Application Support 8.4 (both)
I just installed an old iTunes x64 on a machine running 1909, it updated to 220.127.116.11 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 18.104.22.168
SCCM uses WSUS for it's update deployments, so that part should be just fine.
Your method should still work, and if you are on the Basic license, I believe that is how you have to manage things generally. We do have more automated methods available on the Enterprise plan if you are interested.
I have seen iTunes act odd before, but always have a hard time replicating and determining what the actual issue is. I haven't heard anything about Dropbox updates causing problems though.
Thanks for reporting, we'll keep an eye out for additional issues!
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.
Are you using a driver catalog like Dell or HP?
This should have actually been fixed by Microsoft with KB4557957