Build 19042.906 and 19043.906 are available in RPC and Beta Channel

Next check for updates installed kb5001460 replacing kb5000967 experience package.

Johnny, 

Here is the update from 19042.870 to 19043.906

This was all done with W.U.

No more error 0x80073701 like I had with 19043.899 on machines that went through 19042.868.

Looks like they solved that issue, W.U. to 19043.906 now worked fine also on machines that went through both 19042.868 and 19042.870 and were failing solid with W.U to 19043.899.  😊

But 19043.899 created this new mess with error 0x800f081f.  

As you pointed out the 2 kb5000842 are different and the one in 19043.899 is the one causing the problem.

If they change an update file shouldn't they change the KB number ?  Something is definitely wrong.

I think they did the same type of  mistake when they went from 19042.868 to 19042.870 then they pulled the update and released it again 1 or 2 days later.   

03/26/2021  12:04 AM       559,903,750 kb5000842.899.fc78dc78-9f5f-47f6-8754-6c9555f795ca

03/25/2021  11:57 PM       561,385,402 kb5000842.906.2f8a5873-fa6f-4d03-833d-b6fff95b712b

Releasing Windows 10 Build 19043.906 (21H1) to Beta Channel | Windows Insider Blog

Hi Pauli,

I installed in the same order as your example, starting with experience pack. Suspect the issue is coming from 19043.899 to 19043.906, as Suat pointed out they both share same kb5000842 number.

CU .899 - 559,903,750

CU .906 - 561,385,402

Suat's was upgraded manually previously, mine was total clean install with .899 integrated into ISO. Different means but both of us not using WU for the 1st kb5000842.

Regards,

I had leave my non-insider PC to build 19043.870, but I get interested in this issue. I checked from Beta version which KB's was installed today to get 19043.906, search those packages, renamed to correct order and run update bat.

windows10.0-KB5001460-x64.cab   --> 1.cab

ssu-19041.903-x64.cab                    --> 2.cab 

windows10.0-kb5000842-x64          --> 3.cab

19043.870 updated to 19043.906 without issues.

What SKU of Windows are you running? Have you made modifications to enable or disable features? 

Sorry for late reply. My PC was busy trying things to install KB patch.

First I integrated KB5000842 into the ISO ( build 19043.844 ) which I had downloaded from MS website several days ago. This must have brought my ISO to build 19043.906.

I installed this build over my build 19043.899, thinking that I would reach build 19043.906.

But to my surprise, I saw that my PC ended up in build 19043.867 instead of build 19043.906. It downgraded. EDIT: This statement is incorrect because I inadvertently integrated patch KB5000842 into a different index number in the ISO. Not into my edition of Windows 10. 

Then I installed KB5000842 over build 19043.867. Now I have build 19043.906.

Now I have achieved my goal, somewhat indirectly, though. 

I have Windows 10 Pro. If this is what you meant by SKU.