News

Microsoft Releases Windows 10 Build 21382

By Brian Burgess

Published May 17, 2021

Microsoft is releasing Windows 10 preview build 21382 to Insiders in the Dev Channel. Here’s is what’s new.

Microsoft recently released Windows 10 preview build 21382 in Insiders in the Dev Channel. This release follows up build 21376 which included some font improvements and other fixes. This most recent build bring HDR support for managed color apps and other changes and improvements. Here’s a look at what you can expect.

Windows 10 Build 21382

HDR mode changes the behavior of some creative and artistic apps that use ICC display color profiles like Photoshop, Lightroom Classic, CorelDraw, and others. To find it, right-click an app and select Properties > Compatibility > Use legacy display ICC color management.

Other changes and improvements include the following:

• As some Insiders have noticed, Device Manager now has the ability to view drivers alongside of devices. The new driver focused “Devices by drivers”, “Drivers by type”, and “Drivers by devices” views enable users to view, install, and remove drivers, while the new “Add drivers” action enables users to add and install new drivers across all applicable devices. Managing drivers directly is more intuitive in many situations than working with them by way of the devices they are installed on, so we hope that developers and power users alike will enjoy the added flexibility. This change was added in Build 21343.
• The Start menu will launch to help people get to the apps they want quickly after a clean install or upgrade is finished.
• We’ve updated the new generic folder icon in File Explorer so it will now show an indication when the folder has contents.
• We’ve updated the touch keyboard to use the Segoe UI Variable font and made some small adjustments to the icons.

And this is the list of fixes contained in this release:

• We fixed an issue in the previous flight where after updating some devices unexpectedly showed a warning in the taskbar indicating the version of Windows 10 had reached end of service.
• We fixed an issue impacting explorer.exe reliability.
• We fixed an issue that could result in multiple hung SearchProtocolHost.exe processes.
• We fixed a memory leak that could result in DWM unexpectedly using a lot of memory over time.
• We fixed an issue resulting in certain notification toasts unexpected not firing.
• We fixed an issue resulting in delayed audio playback on ARM64 devices.
• We fixed an issue where the new unified audio endpoint work wasn’t displaying on ARM64 devices.
• We fixed an issue that could result in certain games launching to a black screen in recent builds.
• We fixed an issue where if you select the System option after pressing WIN + X it would just open Settings and not navigating to the About page.
• We fixed an issue resulting in certain devices unexpectedly being listed twice on the Printers and Scanners page in Settings.
• We fixed an issue that could result in Windows Update failing with error 0x80070003.
• We fixed an issue that could cause pixilation when a colored mouse pointer was set to be a large size.
• We fixed an issue where the cursive style for closed captions wasn’t displaying in the list on the Captions page in Settings.
• We fixed an issue where Japanese touch keyboard in 50-on or 12-key layout could show a non-functional and broken text candidate.
• We fixed an issue where incorrect spacing was applied when using the voice typing to type a parenthesis.
• We fixed an issue where when using the handwriting panel to write Chinese, pressing the return key wasn’t committing the text.

Remember 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.