Beta Build 22621.290 & 22622.290 Read the blog!!!!!!!

There were two updates. The first one to 621 and the second to 622. The blog explains the difference so you can uninstall the second update if you want to stay with 621.

It changed to 22622 later in the day (not sure if it was almost immediate or took some time while I was away from the computer), I wasn't aware of it in my original post.

@J W Stuart,

I had 2 different behaviors on 2 machines. Seems to be at MS discretion. 🤣

Hi Pauli,

I could reproduce the problem, now we'll see how long it takes to fix itself. 😜

I made an image backup when it was showing correctly 22622 on CMD prompt then I restored the image, and this showed up after reboot. 🤷‍♂️

Never seen this happening before this Build. Now I could reproduce it on 2 different boxes with this Build.

For sure I never noticed this issue before with windows 10, I just tried restoring an image on Windows 10 and this issue did not happen. 😎

It fixed itself after another reboot:

One of my three devices did same. On first run it get 22621.290 and when it was completed next run of W.U. give Enablement Package to 22622.290.

As said in blog:

We realize that Insiders in the Beta Channel will want to choose which update they get. Insiders who land in the group with new features turned off by default (Build 22621.xxxx) can check for updates and choose to install the update that will have features rolling out (Build 22622.xxx).

Typical MS confusion. 🤣

At least this time it matches.

Both machines at 22622 have Tabs and navigation pane update.

One of my three devices did same. On first run it get 22621.290 and when it was completed next run of W.U. give Enablement Package to 22622.290.

As said in blog:

We realize that Insiders in the Beta Channel will want to choose which update they get. Insiders who land in the group with new features turned off by default (Build 22621.xxxx) can check for updates and choose to install the update that will have features rolling out (Build 22622.xxx).