Microsoft today is releasing build 21376 to Insiders in the Dev Channel. The main change in this release is an updated Segoe UI font.
Microsoft today is releasing Windows 10 21376 to Insiders in the Dev Channel. This release is the follow-up to build 21370. Today’s release brings an updated Segoe UI font as well as other changes and improvements. And a list of fixes. Here’s a look at what you can expect.
Windows 10 Build 21376
Microsoft notes in today’s release announcement that it is introducing an updated Segoe UI font. “We are introducing Segoe UI Variable which includes an optical axis so that font outlines can scale seamlessly from small to larger display sizes. Segoe UI Variable is a refreshed take on the classic Segoe, now with improved legibility at small sizes, and much improved outlines at display sizes. Please note: While Segoe UI Variable is included as part of the OS, its adoption across all the visual surface areas is ongoing and will roll out progressively over time. This means not every visual surface is utilizing the new font just yet.”
Here is the list of changes and improvements in this release:
- To continue enjoying Auto HDR, visit Settings > Display > HDR Settings and make sure Auto HDR is set to On.
- We’ve made some small updates to improve the drag-and-drop default cursor design in scenarios like dragging and dropping into Outlook.
- We’re updating the Connect app icon to align with our other recent iconography improvements.
- Based on feedback we’ve made some small tweaks to how the symbols in the symbols section of the emoji panel are sorted.
- We’re updating the Segoe UI Historic font to add Bamum Unicode range support.
And this is the list of fixes to expect in today’s latest build:
- [News and interests] We fixed an issue where news and interests would open on hover while the mouse was in motion over the button instead of only when the mouse is stationary.
- [News and interests] We fixed an issue so that the taskbar button will no longer be stuck in a reduced size when the taskbar height is increased from its default.
- [News and interests] We made some explorer.exe reliability and performance improvements, especially when using a Remote Desktop Connection.
- We fixed an issue resulting in WSL users finding that File Explorer launch performance and other file related activities regressed after upgrading to Build 21354 and higher.
- We fixed an issue resulting in Pinyin IME users not being able to select items from the candidate window using their keyboard.
- We fixed an issue where Windows Spotlight related text unexpectedly stopped showing on the lock screen in the last few builds.
- We fixed an issue impacting the responsiveness when switching from Start to Search in recent flights (aka when pressing the Windows key and typing).
- We fixed an issue where the “Search with Screenshot” button in Search wasn’t working.
- We fixed an issue resulting in Insiders seeing pseudoloc text on the Windows Update page in Settings.
- We fixed an issue where the Startup Apps page in Settings was showing the wrong icon for Edge Canary.
- We fixed an issue resulting in the Storage Sense page in Settings crashing for some people.
- We fixed an issue where Manage Disks and Volumes in Settings was still incorrectly displaying some HDDs as SSD.
- We fixed an issue that could result in explorer.exe locking up after signing into your PC if you had a large number of browser tabs displaying in ALT + Tab.
- We fixed a rendering issue when viewing acrylic surfaces under Magnifier.
- We fixed an issue impacting night light reliability in recent flights.
- We fixed an issue where the dual boot delay timer was being reset to 0 after upgrading.
- We fixed the issue where some Windows Subsystem for Linux instances can fail to launch with a ‘The parameter is incorrect’ message.
- We’ve worked with our partners to resolve and distribute a fix for an issue causing updates to hang due to a driver compatibility issue. If you are experiencing an issue, please ensure you are running the latest drivers from your manufacturer.
- We fixed an issue that could result in the Windows Update icon unexpectedly not displaying in the notification area when an update was pending reboot.
- We fixed an issue that could result in apps hanging after pressing ALT + Shift.
- We fixed an issue that could result in certain apps crashing if you set focus to the search box in the Open or Save dialog.
- We fixed an issue that could result in Windows Terminal unexpectedly displaying an error saying “Unable to find the selected font” on launch.
- We fixed an issue that could result in audio playback failing when using the new unified audio endpoint.
- We fixed an issue when using a precision touchpad that could result in issues controlling the cursor if your palm was slightly touching the other side of the touchpad.
- We fixed an issue that could result in a precision touchpad unexpectedly scrolling in the wrong direction sometimes.
- We fixed an issue where the black cat emoji wasn’t rendering correctly in DirectWrite controls.
- We fixed an issue where when typing with an IME while Task Manager or certain other apps were in focus, the unfinalized text could appear very tiny on a high DPI screen.
- We fixed an issue where some elements of the Japanese IME candidate window could be unexpectedly cut off after increasing the text scaling.
- We fixed an issue resulting in the F10 function not working if you switched to using the previous version of the Japanese IME.
- We fixed an issue where the touch keyboard unexpectedly had some blank keys when using the Bopomofo IME with the full keyboard layout.
Keep in mind that Insider builds are meant for coders, IT admins, and Windows 10 enthusiasts who want to test new features and submit feedback to Microsoft.
These builds are not meant for inexperienced users. They are also not meant to run on your primary production machine. Insider builds contain many known stability issues that can cause your system to become unstable or even crash.
For more on this build’s full list of changes, known issues, and workarounds make sure to read Microsoft’s full blog post.