This is also on Dev Channel. I got nothing on 6/24.

I got build 22000.1 on the 1st day (24 june) from Windows Update in the Dev channel. Yes it was updated by Windows Update to 22000.51 a few hours later. And I had to fix an incorrectly registered version for one file of .Net 4, using "SFC /SCANNOW": it was forgotten and stayed at the version shipped for 22000.1. So I really have had the two builds ! I suggest to all viewers in this thread to run "SFC /SCANNOW" because there are possible versioning problems: this command must be run from an administrator console, it should fix it. You'll need to reboot Windows after that, and run again "SFC /SCANNOW" to check that all is OK (look also in the "\Windows\Logs\CBS\CBS.log" with a text editor to see if there are other fixes: look directly at end of the log, you'll see if all repairs were correctly applied and all files were properly loaded from the Microsoft updates site). The versioning problem may explain why build 22000.51 was published just a few hours after 22000.1, but we have no details from Microsoft about the real reason.

@vienna10, Hi, Are you still getting the empty translucid window on Widgets ? https://aka.ms/AAd27y3

This registry setting does not work as stated in this article which describes (for build 22000.1): [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "TaskbarSi" =REG_DWORD:* ; default is undefined, the article says it should be 0 for small, or 2 for large, 1 being like the default, but this does not work for me). However the following works (sometimes) in my build 22000.51 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "TaskbarSmallIcons" =REG_DWORD:* ; default value is already set as 0, changing it to 1 enables smaller icons Who's right ??? Why are there two variables for what seems to be for the same goal (or different tests of layouts depending on flights?) @VerdyP, This worked fine for me on 5 machines at 22000.51: TaskbarSi 0 = Small 1 = Medium 2 = Large Takes effect after signing off/on or Restart.

Simple answer is because build 22000.1 was never flighted to Insiders. We got 22000.51. Just to correct you, the ISO created from the distribution folder is 22000.1, as was the install. The installation on my notebook was 22000.51 the next day I edited my comment to clarify. Insiders getting Windows 11 got build 22000.51 using W.U., not creating an ISO.

Windows 11 CO-Release Build 22000.51 is out to Dev Channel

CrazyKats 19,330 Volunteer Moderator

Live in W.U.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

589 answers

CrazyKats 19,330 Reputation points Volunteer Moderator

2021-07-05T17:31:04+00:00

This is also on Dev Channel.

I got nothing on 6/24.
Was this answer helpful?

0 comments No comments
Anonymous

2021-07-05T17:23:59+00:00

I got build 22000.1 on the 1st day (24 june) from Windows Update in the Dev channel.

Yes it was updated by Windows Update to 22000.51 a few hours later.

And I had to fix an incorrectly registered version for one file of .Net 4, using "SFC /SCANNOW": it was forgotten and stayed at the version shipped for 22000.1.

So I really have had the two builds !

I suggest to all viewers in this thread to run "SFC /SCANNOW" because there are possible versioning problems: this command must be run from an administrator console, it should fix it. You'll need to reboot Windows after that, and run again "SFC /SCANNOW" to check that all is OK (look also in the "\Windows\Logs\CBS\CBS.log" with a text editor to see if there are other fixes: look directly at end of the log, you'll see if all repairs were correctly applied and all files were properly loaded from the Microsoft updates site).

The versioning problem may explain why build 22000.51 was published just a few hours after 22000.1, but we have no details from Microsoft about the real reason.
Was this answer helpful?

0 comments No comments
Anonymous

2021-07-05T16:51:05+00:00

@vienna10,

Hi,

Are you still getting the empty translucid window on Widgets ?

https://aka.ms/AAd27y3
Was this answer helpful?

0 comments No comments
Anonymous

2021-07-05T16:39:19+00:00

This registry setting does not work as stated in this article which describes (for build 22000.1):

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]

"TaskbarSi" =REG_DWORD:*

; default is undefined, the article says it should be 0 for small, or 2 for large, 1 being like the default, but this does not work for me).

However the following works (sometimes) in my build 22000.51

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]

"TaskbarSmallIcons" =REG_DWORD:*

; default value is already set as 0, changing it to 1 enables smaller icons

Who's right ??? Why are there two variables for what seems to be for the same goal (or different tests of layouts depending on flights?)

@VerdyP,

This worked fine for me on 5 machines at 22000.51:

TaskbarSi

0 = Small

1 = Medium

2 = Large

Takes effect after signing off/on or Restart.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
CrazyKats 19,330 Reputation points Volunteer Moderator

2021-07-05T16:29:04+00:00

Simple answer is because build 22000.1 was never

flighted to Insiders. We got 22000.51.

Just to correct you, the ISO created from the distribution folder is 22000.1, as was the install. The installation on my notebook was 22000.51 the next day

I edited my comment to clarify.

Insiders getting Windows 11 got build 22000.51

using W.U., not creating an ISO.
Was this answer helpful?

0 comments No comments