Good morning friends! Microsoft has released new preview builds of Windows 11 (version 22H2) under the numbers 22621.436 and 22622.436 (KB5015888) for members of the Windows Insider Beta Program.
Assembly 22622.436 – testing of new functions is available.
Assembly 22621.436 – new features are disabled by default.
If you are in a group with features disabled by default (build 22621.xxx), then check for updates and agree to install an optional update that will make these features available (build 22622.xxx).
Innovations in assembly 22622.436
Nearby Sharing Improvements
Improved device discovery with Nearby Sharing by using UDP protocol (network must be private for the feature to work) along with Bluetooth. Now when you try to share a local file from your desktop, File Explorer, Photos, Snipping Tool, Xbox, and other apps, you’ll find more available devices in the Share system window, including desktop PCs.
Share a local file in OneDrive
Now, when you try to share a local file from your desktop, File Explorer, Photos, Snipping Tool, Xbox, and other apps that use the system share window, you can select OneDrive to directly upload the file to your cloud storage. In the Share window, you can also customize the sharing options for the uploaded file without opening the OneDrive app.
Note. Please note that this feature is currently only available for Microsoft accounts. If the user is signed in through AAD, they need to switch to their Microsoft account by clicking on the profile icon in the top right corner of the Share window. AAD support will be added in one of the future updates.
Changes and improvements in build 22622.436
The Windows Terminal app is now the default in Windows 11. This means that all command line applications will now automatically open in Windows Terminal (such as Command Prompt and PowerShell). You can change your selection under “Settings” -> “Privacy and Security” -> “For Developers”. Note that this change requires Windows Terminal 1.15 or later.
You can now report inappropriate animated GIFs directly from the emoji panel (WIN + ).
Fixes in build 22622.436
We fixed an issue where CTRL + Tab switched tabs in the wrong order after reordering tabs.
Fixed explorer.exe crash when dragging tabs.
If the “Show all folders” option is enabled, the separators in the navigation bar in File Explorer should no longer be displayed. This change will also help resolve an issue where separators were unexpectedly displayed in some other folder pickers.
If you open a zipped folder in a new tab, the tab name will no longer be empty.
Removable drives should no longer suddenly appear in a separate section in the navigation bar between This PC and Network.
There should no longer be a thin bar between the current tab and the command bar.
Updated tooltip when hovering over a tab. She now suggests using Ctrl + W to close the tab, rather than the Ctrl + F4 combination that didn’t work.
If the focus is on the tab bar, then CTRL + W will no longer close two tabs unexpectedly, instead of only closing the current tab.
We fixed an issue where the tab bar could unexpectedly expand vertically, overlapping the contents of the command bar.
We fixed an issue resulting in the Start menu crashing for some Insiders on Build 22622.160.
Fixes in both builds
We fixed an issue that prevented the troubleshooter from opening.
Fixed an issue that caused Smart App Control to lock files signed by the directory file.
We fixed an issue where photos taken with the Camera app could be severely distorted. This problem occurs when using some camera modules in low light conditions.
We fixed an issue resulting in an exception when debugging drivers using Visual Studio 2022 version 17.2 (or later).
We fixed an issue where the Windows Profile service would sometimes crash. The failure could occur during login. The error message is: “The gpsvc service failed to log on. Access is denied”.
We fixed an issue that caused virtualized App-V Office apps to not open or become unresponsive.
We fixed an issue where a small number of Insiders in the Beta channel could experience a cyclic crash in Windows UI components (such as explorer.exe), which could cause the screen to appear to flicker. The fix should prevent this issue from occurring in the future, but if you’re already experiencing this issue, then you need to run the following command in PowerShell as an administrator: