This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(198.4, 2%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPO%3C/text%3E%3C/svg%3E)
New CU's are available together with new Feature Experience Pack.
Releasing Windows 10 Build 19042.906 (20H2) to Release Preview Channel | Windows Insider Blog
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
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.
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,
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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
Next check for updates installed kb5001460 replacing kb5000967 experience package.
W.U. failed with error 0x800f081f W.U. on Beta from 19043.899 to 19043.906.
This was previously updated by W.U. from 19042.867 to 19042.870 and then to Beta 19043.899 without any problem.
Fails every time that I retry to install KB5000842.
CP shows that there was already a KB5000842 installed on 3/23/2021 when it was updated to 19043.899 .
Something doesn't make sense, was it a different kb5000842 ?
Why is it trying to install the same KB5000842 ?
No option to uninstall it from the CP, so I will have to restore an older 19043 or 19042 to get this update to work.