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

sfc/scannow found and repaired corrupt files!

"Getting even weirder, checked again few minutes ago on the same machine and it now shows correctly 22622. Must be another A/B testing B.S"

Perhaps CMD is updated in some background process when main installation is completed?

Possible.

But I had rebooted already more than once after the update and when I submitted the FBH report earlier I did it with recording, so that they can see that I had 22621 in CMD prompt and 22622 in Winver.exe and system info.

Go figure?

"Getting even weirder, checked again few minutes ago on the same machine and it now shows correctly 22622. Must be another A/B testing B.S"

Perhaps CMD is updated in some background process when main installation is completed?

@Silverpulser

>"DISM shows the tool version as 22621.1 and the image version as 22622.290"

That's normal, as shown in Johnny's screenshot of 19041/19044. DISM show original version and it doesn't change when build number is increased by Enablement package. Original 'problem' is why winver and CMD show different build numbers.

All three devices in build 22622.290 show build 22622.290 also on CMD.

That is weird, why does mine show 22621 in CMD promt? This was updated with W.U. from 22621.160.

I'll try updating another box and see what happens. 🤷‍♂️

Edit:

Getting even weirder, checked again few minutes ago on the same machine and it now shows correctly 22622. Must be another A/B testing B.S. 🤣🤣

Mine shows 22622.290 in both places.

So much for consistency! 🤣

DISM shows the tool version as 22621.1 and the image version as 22622.290