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.
![](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)
This is not the first or the last time when same updates act differently on different machines and as you said and MS has told in blog they are going to fix this issue so this is going to be history very soon.
Yes, there was a similar issue from 19042.868 to 19042.870, W.U. was failing for everybody, then they pulled the update from W.U. and released it again a day or 2 later with a fix.
Time for me to go to bed, have a good day,
I'll catch you later.
This is not the first or the last time when same updates act differently on different machines and as you said and MS has told in blog they are going to fix this issue so this is going to be history very soon.
I have get impression that about 4-6 years old computers act better with Insider Previews than new computers?
I update to 19043.899 using W.U. immediately when it was released. How many different KB5000842 was released same time?
No Idea, but apparently there is a difference in your machines versus the ones that fail,
I had 4 machines at .899 and they all failed the update to .906, had to go back to a previous backup and bypass .899.
I update to 19043.899 using W.U. immediately when it was released. How many different KB5000842 was released same time?
I had that option also on build 19043.899.
See my previous reply BilliaZ.
P.S. I didn't had that issue any of installed Beta 19043.899. (2 PC and 1 VM) Alla updated to 19043.906 by W.U.
Looks like many other people had the problem, maybe your update to .899 was done with a different version of the kb5000842, I sure could not uninstall it from .899, and did get the error 0x800f081f going from .899 to .906 with W.U. in Beta.