It got interesting in the Windows Insider Program. Microsoft just released two new versions of Windows 11 on the Windows Insiders Beta channel, dividing the channel into two categories. To you longtime insiders, this sounds like what Microsoft did with the Lent Ring in 2019. Here’s what that means for you.

So here are two new versions. one is build 22621.290 and the other is build 22622.290. Those who receive Build Update new functions are introduced or activated through activation packages. Those who are there drunkimage are those who new features are disabled by default.

Please note that the majority of Beta Channel Insiders receive automatically Build Insiders end up in the group with new features disabled by default Build may check for updates and install the update for which features are introduced at any time. Microsoft’s explanation is below.



This approach allows us to enforce our ability to release updates with features disabled by default. It will also allow us to get a better idea of ​​the impact of enabling new features. For example, by comparing feedback and usage data between Insiders in these two groups, we can determine if a feature has reliability issues.

Based on this information, we can decide whether new features are available for further learning by enabling their introduction or, in some cases, disabling a feature to fix bugs. The goal is to use benchmark data to ensure the best possible experience as we test new features and experiences with Windows Insiders in the Beta Channel.

This approach is only used for the beta channel and does not indicate any changes or plans for the eventual rollout of features. The activation pack artificially increments the build number of the update with new features deployed and enabled to differentiate devices with the update with features disabled by default. As a reminder, the features we’re trying out with Windows Insiders will be rolled out when they’re ready, and not all features we’re trying out in the beta channel will be rolled out to general customers.

Microsoft Splits Windows Insider Beta Channel and Releases Two Versions of Windows 11 - Here's What You Should Know - - July 5, 2022

It can be confusing and you may lose some features with these versions. If so, install the activation pack and they should be back shortly.

However, build 22622.290 suggested actions for phone numbers and data, as well as OneDrive storage alerts and subscription management in settings. Bug fixes for this version are listed below.

  • Middle-click on a folder in the main part of File Explorer to now open it in a new tab.
  • The row of tabs should now be included in the keyboard focus cycle when pressing Tab or F6. Once the focus is on the row of tabs, you can use the left or right arrow keys to continue.
  • Fixed an issue where the tab order was wrong when using CTRL+Tab when rearranging the tabs in File Explorer.
  • Made some adjustments when “Show full path in title bar” is enabled to ensure the folder name is always visible.
  • Fixed a scaling issue that could cause tabs to resize unexpectedly.
  • Right-clicking on a tab and then clicking again in File Explorer should now more reliably hide the context menu.

Build 22621.290 and 22622.290 receive these fixes

  • New! We added the FSCTL_LMR_QUERY_INFO code from the SMB (Server Message Block) forwarder specific to Public File System Control (FSCTL).
  • New! We’ve added support for Transport Layer Security (TLS) 1.3 in client and server implementations of Windows LDAP (Lightweight Directory Access Protocol).
    We’ve updated the Remove-Item cmdlet to properly interact with Microsoft OneDrive folders
  • We have enabled the InternetExplorerModeEnableSavePageAs group policy. For more information, see the Microsoft Edge browser policy documentation.
  • We fixed an issue resulting in the Take Photo button appearing when using a generic file dialog to open the camera.
  • We fixed an issue preventing devices from receiving an offer from Windows Update for the same add-on driver if that add-on driver was already installed without the base driver.
  • We fixed an issue resulting in Create Media (IFM) installation for Active Directory failing with error “2101 JET_errCallbackFailed”.
  • We fixed an issue that occurs when Active Directory Lightweight Directory Service (LDS) resets the password for userProxy objects. Password reset failed with error like “00000005: SvcErr: DSID-03380C23, problem 5003 (WILL_NOT_PERFORM), data 0”.
  • We have enabled the InternetExplorerModeEnableSavePageAs group policy. For more information, see the Microsoft Edge browser policy documentation.
  • We fixed an issue that occurs when the Active Directory Lightweight Directory (AD LDS) service resets the password on userProxy objects. When attempting to reset someone’s password and authenticate with single bind, the password reset failed. The error is something like “00000005: SvcErr: DSID-03380C23, problem 5003 (WILL_NOT_PERFORM), data 0”.
  • We fixed an issue preventing Microsoft Edge from being available in Windows Sandbox.

There is only one known issue. Microsoft is working on a fix for an issue that causes cyclic crashes in Windows UI components (like explorer.exe) for a small number of Beta Channel initiations, resulting in the screen popping up. If you’re concerned, run the following command in an elevated PowerShell window.

Add-AppxPackage -Register -Path C:\Windows\SystemApps\Microsoft.UI.Xaml.CBS_8wekyb3d8bbwe\AppxManifest.xml -DisableDevelopmentMode -ForceApplicationShutdown

phew! Happy downloading, Windows Insiders!

Share this post:

Leave a Reply

Your email address will not be published.