KB4592438 CU Windows 10 v2004 build 19041.685 and v20H2 19042.685 Win Update

Thanks @f14tomcat.
I've already tried the .msu file, which also fails to install.
You've confirmed what I thought about the cab files.
Cheers, Dave.

f14tomcat said:

Yep, they did.

I got bit, but soon realized my error and reverted to .630 via repair install on my fast changing main machine and Macrium restore on the others. So no sweat.

f14tomcat said:

TG for MR!

I updated from 19041.630 to 19041.685 yesterday afternoon through Windows Update. I had NO problems whatsoever with the download and installation. Everything has been running smoothly all day today for both myself and my wife.

Downloaded the current ISO with the MCtool. It had been updated to a v661. I was at 661 and not going anywhere. In fact, today's patch repeatedly downloaded and installed unsuccessfully. The upgrade repair install with keep apps-settings was available and somehow I missed cancelling updates so that took some time. This is a slow internet connection (Mas 5g) but it went along at its max. It is now up to date which I was thinking was not going to be possible. This desktop had a clean install in Aug and hiccuped along the way. An older Lenovo laptop upgraded received all these Nov files in Win update plus Dec 8 patch without a hitch. After the system repair install a net update arrived. All settings are intact.

I had installed photo processing software and major updates so I wasn't keen on restoring an image before v661. Thankful that the keep all feature was back in that recent ISO.

I'm thinking that Microsoft Update needs to take a break, self isolate and perhaps do 6 month interval version updates.
Rose in quarantined Ontario, Can.

DaveH1 said:

Thanks @f14tomcat.
I've already tried the .msu file, which also fails to install.
You've confirmed what I thought about the cab files.
Cheers, Dave.

Hey Dave. I don't know if you're still struggling with the update, but if you uninstall the 20H2 Enablement Package, it reverts back to 2004 and then you can do an in-place repair/upgrade. I was on 19042.630 and doing that worked like a charm for me.

Done and dusted my end either and without the issues.

...so what's the story with Task Manager and its Start-up tab? It still says 'not measured' all over the place?