In this article, we will talk about the latest Windows 11 Insider Preview Build for the Beta Channel, which is Build 22622.590.
Before talking about anything that is new in the Beta Channel, we need to talk about the changes regarding the Beta Channel System.
Starting today, Microsoft is releasing updates to the Beta Channel that put Windows Insiders into one of two groups similar to what they did back in 2019:
- A group of Insiders in the Beta Channel will receive Build 22622.xxx updates that will have new features getting rolled out or turned on via an enablement package like how we release updates for Windows 10 today.
- A group of Insiders in the Beta Channel will receive Build 22621.xxx updates that will have new features turned off by default.
This way, Microsoft will be able to test out new features easier.
If you receive the Build that has all the features automatically turned off, you can enable them manually in 2 ways:
- Search for Update in the Settings App Windows Update
- Use Vivetool to manually enable the features
Fixes in Build 22622.590
[General]
- We fixed the issue causing Control Panel to not launch from the Start menu, Search or if pinned to the taskbar in the previous flight.
- As a result of feedback from Windows Insiders, we have disabled the ability to share a local file directly to OneDrive using the built-in Windows share window that first began rolling out to Windows Insiders in the Beta Channel with Build 22622.436. We hope to bring this feature back in the future after further refinement of the experience. As we’ve mentioned previously, features we try out in the Dev or Beta Channels may not always ship.
[File Explorer]
- Fixed an issue causing a small percentage of Insiders to experience repeated explorer.exe crashes after attempting to access certain folders on their systems in the previous Beta Channel build.
- As a one-time change to help people find their folders with the navigation pane updates, if the default folders pinned to File Explorer’s navigation pane had been unpinned, they will be re-pinned after upgrading.
- Fixed a recent issue where if File Explorer was open when you switched between light and dark mode, you could end up with some unreadable text / UI showing the wrong color.
- Fixed an issue where the New / Sort / View / etc buttons in the command bar could become noticeably clipped vertically after increasing your text scaling in Accessibility Settings.
- The search box background should no longer unexpectedly have a dark background sometimes when you’re using light mode.
- If you move keyboard focus to the tab row (using F6), pressing the arrow keys to move keyboard focus within the row will now include setting focus to the close button within the tab.
- If File Explorer is maximized and the taskbar is set to autohide, hovering your mouse on the bottom of the screen should now actually bring up the taskbar.
- Fixed a memory leak which was happening when closing File Explorer windows.
- Fixed a GDI objects leak when resizing the navigation pane in File Explorer, which could potentially lead to content in File Explorer not rendering correctly over time for Insiders who resized the navigation pane frequently.
[Taskbar]
- The taskbar overflow flyout should now follow your accent colour like the rest of the taskbar does when “Show accent color on Start and taskbar” is enabled under Settings > Personalization > Colors.
- The apps in the taskbar overflow flyout should now be in the correct order when using an Arabic or Hebrew display language.
- When the taskbar is center aligned and full, the widgets entry point will now collapse to a shorter width to give you a little more room on the taskbar.
- Fixed a couple of issues related to the taskbar overflow which could lead to sporadic explorer.exe crashes.
Fixes for BOTH Build 22621.590 & Build 22622.590
- We fixed an issue that affects cldflt.sys. A bugcheck occurs when it is used with Microsoft OneDrive.
- We fixed an issue that affects robocopy. Robocopy fails to set a file to the right modified time when using the /IS
For the list of Known Issues, you can check this article from the Microsoft Blog.
Share the article: