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

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. 😉

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    :-(

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

Johnny, 

I just filed a new FBH report for error 0x800f0984 going from 19043.899 to 19043.928.

https://aka.ms/AAbx90o

As for the stay at home orders, I've been on that for over a year now...

Just got my second Moderna vaccine shot that gave me a few hours of 38 C. fever, it started 24 hours after the second shot, but after that I feel fine now. 

I hope this thing works, I'm sure it will eventually become a yearly routine like the flu shots.

Really Amazing Update 

Clearly this fix mentioned in the blog did not work, it eliminated one error message and created a new one.

• We have resolved an issue where some Insiders were getting an 0x800f081f error when attempting to install an early version of KB5000842. If you continue to hit an issue with the final version of KB5000842 update, let us know via Feedback Hub.

Now when trying to W.U. from 19043.899 to 19043.928 instead of error 0x800f081f we get error 0x800f0984.

https://aka.ms/AAbx90o

A workaround is still an update in place using an ISO file.

I just used the official MS ISO 19043.867 while online and letting it check for updates. 

The installation completed without errors and the system came up to build 19043.928.

W.U. then downloaded the latest experience package and .NET updates.

I'll just keep around a little longer a backup of 19043.899 to see if there is a working fix next time around. 

Not knowing when the 21H1 MCT will be available, I just made this for now. :-)

Hi Johnny, 

Another way around the updates errors from 19043.899.

I just just tried it out and worked fine.

A) Starting from 19043.899 on Beta, using the official MCT 20H2 ISO (Currently at level 19042.631) the update in place, online and checking for updates, will bring the system up to 19042.928.

B) Windows Update will download and install the 21H1 enablement package, .NET updates and the experience package and the system will be back to 21H1 19043.928. 😉

A)

B)

KB5001330 - having issues with netbios working after this patch is installed, I have had to remove this on about 6 machines so far to get network traffic working again.

@chrisbarton462, 

I just use the default settings. My local network traffic seems fine.

What kind of problems do you see? 

Did you file an FBH report ?