Microsoft releases Windows 10 build 21382 with HDR improvements for Photoshop

Windows 10 Insider Preview text next to a laptop with the vNext text on the screen

Microsoft has released another weekly build of Windows 10 to Insiders enrolled in the Dev channel, this time bringing the build number up to 21382. As per usual, this build comes from the co_release branch, not the rs_prerelease branch, and it's part of a future Windows update, not the upcoming version 21H1 that's already available in the Beta and Release Preview channels.

Much like other recent builds, there isn't a whole lot that's new in this release, but there is an improvement that's likely to be welcomed by creative professionals. Apps that use ICC display color profiles will now be able to use the full color gamut of HDR displays and retain color accuracy:

Bringing HDR support to color managed apps

HDR mode changes the behavior of some creative and artistic apps that use International Color Consortium (ICC) display color profiles, such as Adobe Photoshop, Adobe Lightroom Classic, and CorelDraw (amongst others). In the past, these apps were limited to targeting the sRGB color gamut.

We have added a new feature that lets these apps get accurate color and access the full gamut of your HDR display. To turn this feature on, close your application, right-click the app’s icon and click in Properties > Compatibility tab and then under Settings select “Use legacy display ICC color management”. This flag only has an effect in HDR mode.

New color management options in Windows 10

That's pretty much it in terms of new features, but there are some other changes and improvements, like the new Segoe UI Variable font now being available on the touch keyboard:

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

Of course, the build also comes with the usual array of bug fixes:

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

And finally, there are still some known issues in this build, though the list has been shrinking significantly with the past few builds. Here's what you need to look out for:

  • The Windows Camera App currently does not respect the default brightness setting set via the new Camera Settings page.
  • We’re investigating an issue where elements of Search (including the search box in File Explorer) are no longer displaying correctly in dark theme.
  • [News and interests] We’re investigating an issue where the flyout may occasionally flash in the top left corner of your screen after clicking the button on your taskbar.
  • During the upgrade and in the initial welcome screens when after first signing in after upgrading, you may unexpectedly see the text that appears to be displayed in Times New Roman font.

On that note, Microsoft announced earlier this week that it's bringing back its Bug Bash events, so if you'd like to help improve the quality of the next Windows 10 release, you may want to file any issues you find during this period. There are also a number of quests available in the Feedback Hub to help users find specific issues Microsoft may be looking for. The event has already started and it will last until May 17.

Report a problem with article
An ATX 12VO10-pin connector
Next Article

Intel ATX12VO might finally see wider adoption with Alder Lake-S

keysmart charger
Previous Article

This portable multi-device Power Bank will keep you juiced at a discount

10 Comments - Add comment

Advertisement