KB5006670 Windows 10 2004 19041.1288, 20H2 19042.1288, 21H1 19043.1288 Win Update

@Brink, @Try3,

Info windows from the ... button seemed to indicate MS thought the file was coming by an insecure route ?!?!

Went ahead and kept the file, checked the SHA1 hash and it matches, except all the letters returned from the context menu hash generator were uppercase, while those in the filename are all lowercase... Oh well, I had already started the update from Windows Update, so I'll see how that goes.

Thanks much for the help!

Mike

lirene said:

The lack of a SSU this month sped up the process a little since that meant a little less System Restore scoping to slow things down for me. So that's a nice development to feel slightly more efficient.

SSUs are now part of the CU KBs and have been for a while. The OP has some words about SSU.

This KB's MSU contains SSU-19041.1220-x64.cab

Try3 said:

Mike,

Your browser thought so and my browser thought so. Perhaps there's a fault in the MSUpdateCatalog site at the moment.

Denis

I got the same result trying to download any of the enablement package files for 21h2. The fix for me was to go back to 21h1 build 1202. Any build after that would not let me download the enablement package. I was using the Edge browser.

steve108 said:

SSUs are now part of the CU KBs and have been for a while. The OP has some words about SSU.

This KB's MSU contains SSU-19041.1220-x64.cab

on checking.. last month, kb5005699 (not a SSU) was installed before the monthly update.. and back in August, it was kb5005260 (a SSU). It shows up under Setup on Event Viewer, but if you just look at System or the ReportingEvents txt file, the individual SSU isn't mentioned.

steve108 said:

SSUs are now part of the CU KBs and have been for a while. The OP has some words about SSU.

This KB's MSU contains SSU-19041.1220-x64.cab

The Sept 14 CU included the same SSU as this CU so it did not have to install it again.

Jim

lirene said:

on checking.. last month, kb5005699 (not a SSU) was installed before the monthly update.. and back in August, it was kb5005260 (a SSU). It shows up under Setup on Event Viewer, but if you just look at System or the ReportingEvents txt file, the individual SSU isn't mentioned.

Phone Man said:

The Sept 14 CU included the same SSU as this CU so it did not have to install it again.

Jim

Thanks. My SSU also appears to have last been last updated during the September CU KB installation. I had not checked to see when my SSU last got updated until just now based on both of your posts.

curlysir said:

This is what I had to do
Repair Install Windows 10 with an In-place Upgrade

Thanks. I restored the computer with an image backup.
I might wait to attempt installing KB5006670 again just for now.
I see others are also having problems.
Sometimes in Microsoft Land, updates have a tendency to fix themselves if you wait.

Stigg said:

I see others are also having problems.

yes indeed.

the KB5006670 CU seems to be causing some network printing problems as described in this BleepingComputer forum thread.

I think I'll skip KB5006670 and wait for the next CU to come out either next week or by the end of October