Build 19043.928 out to Beta & Release Channel + ISO for 19043.928

Hi fg,

Good to know this, Had another poster report same error trying to install this update, but don't know if he was on .899

https://answers.microsoft.com/en-us/insider/forum/all/update-error-in-windows-10-21h1-os-build-19043899/89298a97-e6d4-4b60-bfb0-e3a79e3963c5?page=3

Yep, I already tossed those 899 images after 906 was released.

So much for the supposed fix mentioned in Blog, did you file another report to FBH.  Wonder how many more will be coming in forum with same error. Might be a good time for a fishing trip, except we under stay at home orders    :-(

Johnny, 

It looks like the error is reported also by carlos.mendes with the new error code, instead of 0x800f081f, we now get 0x800f0984.

The message is also misleading again, it says "download error", but the error occurs at the end of the installation phase not on download.

Here is my new report:

https://aka.ms/AAbx90o

Hi fg,

Good to know this, Had another poster report same error trying to install this update, but don't know if he was on .899

https://answers.microsoft.com/en-us/insider/forum/all/update-error-in-windows-10-21h1-os-build-19043899/89298a97-e6d4-4b60-bfb0-e3a79e3963c5?page=3

Yep, I already tossed those 899 images after 906 was released.

So much for the supposed fix mentioned in Blog, did you file another report to FBH.  Wonder how many more will be coming in forum with same error. Might be a good time for a fishing trip, except we under stay at home orders    :-(

Johnny, 

I kept a backup of 19043.899 just to test if they ever fixed the problem that was introduced with it, but it looks like it was never fixed, it still fails trying to update from 19043.899 to 19043.928.

It is not an issue any longer because I had already worked around that bug by skipping the update to .899 or by doing and update with ISO to 19043.906. 

Looks like I'll never know what kind of bug was introduced with .899.

Right now it seems pointless, I'll just throw away the copies of .899 that I kept for retesting. 😉

Here are 3 different situations on my machines:

A) 19042.928  Public Release.

B) 19042.928 RPC.

C: 19043.928 Beta.

>I only got 19042.928.  on Release.

>Not getting 19043.xxx

Only business users who are in RPC and have updated to 21H1 get this CU, not normal users.

Quote from blog:

This update is also available for commercial devices in the Release Preview Channel on 21H1 as mentioned here in this blog post