Build 19042.906 and 19043.906 are available in RPC and Beta Channel

@Sibro.o

Did you dbl check in Optional updates, the update was buried under another folder in optional.

@fg,

There sure was an issue coming from .899.  Deleted that ISO and creating a new one for 19043.906 and we will see how that goes. One vm on track, the other clean installed .899 was a total no go for update. No way to uninstall kb5000842.  Yes to your question regarding using same kb#, MS has done this many times in the past for CU updates in Dev, Beta channels.

Regards,

@fg,

There sure was an issue coming from .899.  Deleted that ISO and creating a new one for 19043.906 and we will see how that goes. One vm on track, the other clean installed .899 was a total no go for update. No way to uninstall kb5000842.  Yes to your question regarding using same kb#, MS has done this many times in the past for CU updates in Dev, Beta channels.

Regards,

Hi Johnny, 

If they reuse the same KB# shouldn't they just replace the one already installed with the newer one downloaded with W.U. ? 

Why the error ?

If they reuse the same KB# shouldn't they just replace the one already installed with the newer one downloaded with W.U. ? 

Why the error ?

Yes, normally it should and has in the past. As with any Dev software, things happen, that shouldn't. If you accept Eddie's statement on P1:  "That error generally occurs when you make unsupported modifications to the system."

I for one do not buy it. Using Dism or msu files to update is no different than using WU or any other method. Appears they will not admit to an issue of update error from .899 on some devices. We have a few Insiders in this thread that state otherwise. It is what it is.

Regards,

If they reuse the same KB# shouldn't they just replace the one already installed with the newer one downloaded with W.U. ? 

Why the error ?

Yes, normally it should and has in the past. As with any Dev software, things happen, that shouldn't. If you accept Eddie's statement on P1:  "That error generally occurs when you make unsupported modifications to the system."

I for one do not buy it. Using Dism or msu files to update is no different than using WU or any other method. Appears they will not admit to an issue of update error from .899 on some devices. We have a few Insiders in this thread that state otherwise. It is what it is.

Regards,

Mine were all updated with W.U. I did not use DISM and I did not make any unsupported modifications, sounds like a lame excuse ! 😉 

Everything works fine if I start from a build 19043 before W.U. updated to .899, or I can start from any of the current public build 20H2.  :-)

Another problem after a clean install with the official MS R.P. ISO 19043.867.

This keeps failing even on retry or after a restart, it updated to .906, but this keeps failing....

I don't see any .NET Framework update, maybe that is why it keeps failing ?

https://aka.ms/AAbofsf

The error 0x80070643 keeps happening when it tries to update security KB2267602 (Version 1.333.1349.0)