KB5010342 Windows 10 19042.1526, 19043.1526, 19044.1526 Win Update

Took a while! Ran SFC and DISM no errors, only time will tell.

curlysir said:

UPDATE: Just finished repair install on all 3 computers, now at 21H2 19044.1526 on all 3. First time I have had to do a repair install on all 3 on the same update.

Hmm, that is a rather bizarre coincidence for 3 PCs to do this

Thanks for sharing this.

Installed smoothly, no SFC or DISM errors.

Phone Man said:

The information on this update shows Windows 10 servicing stack update - 19042.1525, 19043.1525, and 19044.1525

My systems show 19041.1525. All the previous updates also showed 19041. It is strange that MS didn't change the 19041 to the newer versions but its working fine.

Jim

In the 1st post of this topic, there are links for Enablement packages, to upgrade to 19042 (20H2) or 19043 (21H1) or 19044 (21H2).

curlysir said:

UPDATE: Just finished repair install on all 3 computers, now at 21H2 19044.1526 on all 3. First time I have had to do a repair install on all 3 on the same update.

Did you install optional CU released one/two weeks ago on these machines by any chance? Or Jan CU was the latest update you installed there?

EDITED TO ADD #1: I can see that you did:

KB5009596 Windows 10 19042.1503, 19043.1503, 19044.1503

EDITED TO ADD #2: And you've had similar/the same problem before (I remembered my response then):

KB5007253 Windows 10 19041.1387, 19042.1387, 19043.1382, 19044.1387

Most interesting...

Consider this (but then it might be too late to confirm this now that you perform the repairs already):

[SOLVED] - Windows 10 - KB5007186 (Nov CU) ends up with 0xe0000100 | Sysnative Forums

It was empty INF files recently updated by matching penultimate CU within C:\Windows\System32\DriverStore\FileRepository in my case and to this day I do not know why it occurred (I've witnessed it twice in the last 3 years).

Phone Man said:

The information on this update shows Windows 10 servicing stack update - 19042.1525, 19043.1525, and 19044.1525

My systems show 19041.1525. All the previous updates also showed 19041. It is strange that MS didn't change the 19041 to the newer versions but its working fine.

Jim

@Brink
Hello Shawn,

You used to post the EKB download links (to go from 20/21XY to 21H2) in the front monthly CU announcements like this one. That stopped a few months back.

I think it might be handy to keep doing that as the EKBs are not available for download via the MS Catalog and it takes a bit of hunting around to find the EKB download links from the older monthly CU announcements. For example, the OP of the previous post I quoted might benefit from having the EKB direct download link.

What do you think about this suggestion? Thank you

steve108 said:

@Brink
Hello Shawn,

You used to post the EKB download links (to go from 20/21XY to 21H2) in the front monthly CU announcements like this one. That stopped a few months back.

I think it might be handy to keep doing that as the EKBs are not available for download via the MS Catalog and it takes a bit of hunting around to find the EKB download links from the older monthly CU announcements. For example, the OP of the previous post I quoted might benefit from having the EKB direct download link.

What do you think about this suggestion? Thank you

Hello Steve,

I had only stopped posting them since you should be able to directly update to 21H2 now without it.