Windows 11 Beta build 22624.1610 (KB5025299) fixes registry compatibility issue, and more

Today, Microsoft has released builds 22624.1610 and 22621.1610 (KB5025299) to the Beta Channel for Windows 11 Insiders. The company writes in its blog post:

Hello Windows Insiders, today we are releasing Windows 11 Insider Preview Build 22621.1610 and Build 22624.1610 (KB5025299) to the Beta Channel.

• Build 22624.1610 = New features rolling out.
• Build 22621.1610 = New features off by default.

The new release contains a few small improvements and bug fixes, along with a list of current known issues. You can check out the entire changelog below:

Changes and Improvements in Build 22624.1610

[Settings]

• We are introducing new presence sensor privacy settings and APIs. If you have a device with compatible presence sensors, you can now manage your privacy and block/allow certain apps from accessing these sensors. No images or metadata is collected by Microsoft and all processing is done locally on the device hardware to maximize privacy. You will find these settings under Settings > Privacy & security > Presence sensing here if your device supports it. App developers with devices with compatible presence sensors can target apps to request and read user presence information after requesting a human presence capability. Learn more about the API here.

Changes and Improvements in BOTH Build 22621.1610 & Build 22624.1610

[Settings]

• Windows Insiders can help us preview a new experience we’re working on. Insiders will begin to see a new toggle under Settings > Windows Update for “getting the latest updates as soon as they are available”. This new toggle is meant to be used in the Beta Channel to allow Insiders to switch more seamlessly to the enablement package. Insiders in the Beta Channel who are on Build 22621 and toggle this on will get updated to Build 22624 via the enablement package. Insiders in the Beta Channel already on Build 22624 and toggle this on will see a “Windows configuration update” offered via Windows Update that is designed to help us make sure this new toggle is connected to our backend services correctly. This configuration update introduces nothing new for Insiders.

Fixes in Build 22624.1610

[General]

• Fixed an underlying issue which was causing a noticeable increase in explorer.exe crashes in the last flight for some Insiders.

Fixes for BOTH Build 22621.1610 & Build 22624.1610

• This update addresses a compatibility issue. The issue occurs because of unsupported use of the registry.

Known issues

[Search on the Taskbar]

• If you have the Bing button in the search box on the taskbar and you restart your computer, you may see the daily rotating search highlight for some time before getting the Bing button back.

[File Explorer]

Insiders who have access keys in File Explorer:

• Shift + Right click on a file or folder is not opening “Show more options”.

[Live captions]

• On ARM64 devices, enhanced speech recognition support installed through the Language & Region settings page will require restarting live captions if you switch languages in the live captions Caption language menu.
• [NEW] Live captions will crash on first launch due to an issue impacting registry data retrieval. A new fix is expected very soon.
• Certain languages shown on the Language & Region settings page will indicate speech recognition support (e.g., Korean) but don’t yet have support for live captions.
• When adding a language through the Language & Region settings page, language feature installation progress may become hidden, and you may not see install completion of “Enhanced speech recognition” (required by Live Captions). (You can use the language’s “Language options” to monitor progress.) If this happens, there may be an unexpected delay before the live caption setup experience detects this and lets you continue.
• Captioning performance may be degraded in non-English languages and missing out-of-language filtering in non-English (United States) languages which means that incorrect captions will be shown for speech not in the caption language.

You can view the official blog post here.