Here's what's fixed, improved, and still broken in Windows 10 build 21337

Microsoft has released its weekly build of Windows 10 for Insiders in the Dev channel, bringing the build number up to 21337. After last week's build 21332 focused more so on removing features rather than adding them, this build actually includes a bunch of news, such as Windows Terminal and Power Automate Desktop now being included as system apps.

It wouldn't be an Insider build without accompanying lists of minor improvements, fixes, and known issues, though, and there's a bit to go over with this release. Starting with the miscellaneous improvements in build 21337, there are updates to emoji panel and the updated IME for Asian languages should now be available for everyone:

• We are now rolling out the new IME candidate window design to all Windows Insiders I the Dev Channel using Japanese, Chinese Traditional, and Indic IMEs. We’ll let you know once the rollout for the remaining IMEs increases.
• We’re updating the emoji panel (WIN + Period) to support searching in more languages, including Amharic, Belarus, Cherokee, Filipino, Faroese, Icelandic, Khmer, Mongolian (Cyrillic script), Burmese, Sindhi, Serbian (Cyrillic script), Serbian (Latin script), Swahili, Thai, Turkmen, Tonga, Uzbek (Latin script), and Cantonese (Traditional). Please continue sharing feedback about the emoji search results in the Feedback Hub under Input and Language > Emoji Panel.
• Live previews for websites pinned to the taskbar from Microsoft Edge are now rolling out for all Insiders.

There's also a decently long list of fixes in this build, which might help make it more usable. Here's the full list:

• We fixed a DWM memory leak impacting Insiders in recent flights.
• We fixed an issue resulting in errors for some Insiders when trying to launch Settings via URI, including when using the Display Settings and Personalization options when right clicking the desktop.
• We fixed an issue where if you click on the Advanced Options page under Settings > Update & Security > Windows Update would crash Settings in the previous flight.
• We fixed a set of issues causing crashes in many x64 apps on ARM64, particularly in scenarios involving video or DRM content. Examples of x64 apps no longer crashing include Microsoft Translator, BlueJeans, The CW, Alexa, Astroneer, and Epic Games Launcher.
• We fixed an issue that could result in the Windows Security icon in the taskbar saying an action was needed, but the app had no actions to take.
• We fixed an issue that could result in the Windows Security icon in the taskbar being unresponsive.
• We fixed an issue in recent flights that could result in some games freezing after locking and unlocking your PC while the game was in full screen mode. This issue may also have resulted in freezes after ALT + Tab.
• We fixed an issue in recent flights resulting in flickering when hovering over icons and buttons in certain apps.
• We fixed an issue in recent flights for some Insiders with domain joined devices where their credentials for apps and websites would unexpectedly be lost on upgrade.
• We fixed an issue resulting in some Insiders noticing that System File Checker (SFC) tool would erroneously saying it found corrupt files the first time it was run after each upgrade.
• We fixed an issue causing certain UPS to show up in Device Manager with error code 43.
• We fixed an issue that could result in werfault.exe crashes.
• We fixed an issue in recent builds resulting in some insiders not being able to resume their devices from sleep or experiencing a bug check with the error IRQL_NOT_LESS_OR_EQUAL.
• We fixed an issue resulting in some Insiders unexpectedly seeing a Bitlocker recovery screen after upgrading to recent Dev Channel builds.
• We fixed a ctfmon.exe crash impacting the reliability of voice typing (WIN + H).
• We fixed a ctfmon.exe crash that could occur if you switched to a Microsoft IME while in a 3rd party IME reconversion session.
• We fixed an issue in recent builds that could result in Search not opening after clicking the search box in the taskbar.

With that being said, there are still quite a few known issues in this build, so you may want to check them out before checking for updates:

• We’re looking into reports of the update process hanging for extended periods of time when attempting to install a new build.
• We’re working on enabling the new taskbar experience for existing pinned sites. In the meantime, you can unpin the site from the taskbar, remove it from the edge://apps page, and then re-pin the site.
• [News and interests] We’re addressing an issue where news and interests may not be available when signing into Windows without internet access but returns when online.
• [News and interests] Sometimes the news and interests flyout cannot be dismissed with pen.
• [ARM64] Insiders who installed the preview version of the Qualcomm Adreno graphics driver on the Surface Pro X may experience reduced brightness of the display. This issue is fixed with an updated version of the preview graphics driver at https://aka.ms/x64previewdriverprox. If you are experiencing this issue, please see the feedback collection for more information.
• We’re working on a fix for an issue where some devices with Realtek network adapters running driver version 1.0.0.4 may experience intermittent loss of network connectivity.
• We are working on the fix for an issue where on some high-refresh-rate monitors, games will only run at 60Hz. Variable-refresh-rate monitor scenarios may also result in tearing.
• The network flyout on the login screen doesn’t open on this build, which will prevent you from connecting to a new network before logging in. If your account is in a state that requires internet to log in, you can work around the issue by plugging in Ethernet, getting the device in range of a previously configured Wi-Fi network, or logging in with any other available account first.
• We are working on the fix for an issue Insiders reported in the previous flight where devices with certain NVMe drives may experience disk resets or WHEA_UNCORRECTABLE_ERROR bugchecks. If you were impacted by this on Build 21332, you may want to pause updates.
• We’re investigating reports of an issue with some devices receiving DPC_WATCHDOG_ERROR bugchecks. If you were impacted by this on Build 21332, you may want to pause updates.

As a reminder, these builds are part of an active development branch, and according to the Insider program restructuring that happened last summer, these builds aren't tied to a specific Windows 10 update that will roll out to the general public. The next truly major update will be released in the second half of the year, and it's expected to include a significant overhaul of the Windows 10 UI - though we've yet to see much of it.