Windows 10 build 21364 is now available with support for Linux GUI apps

Laptop with vNext text inside next to the Windows 10 logo with light grey and mint green colors

With another Wednesday comes yet another build of Windows 10 for Insiders enrolled in the Dev channel. This time, we're getting build 21364, and just like we've seen for the past couple of weeks, this is coming from the co_release branch.

While that would suggest new features aren't being added as quickly in the immediate future, there's quite a bit packed into this one. For example, you can now run Linux GUI apps through the Windows Subsystem for Linux, instead of being limited to command line interfaces. There are also Task Manager improvements for Microsoft Edge, and more. Here's the full list:

Run Linux GUI applications directly on Windows using the first preview of GUI app support on the Windows Subsystem for Linux (WSL)

The Windows Subsystem for Linux now includes a first preview of support for GUI applications! This means you can now run your favorite GUI editors, tools, and applications, to develop, test, build and run your Linux apps! Please view the video below for a demo:

For more info on this change please view this blog post.

Task Manager supports Microsoft Edge process classification

We partnered with the Microsoft Edge team to support process classification in Task Manager. This will help you to identify resource consumption under Microsoft Edge. The classification is broken down to several different components like Tabs, Browser processes (Browser, GPU Process, Crashpad), Utility plugins (Utility: Audio Service Extensions), Dedicated & Service workers etc. It also features separate icons for each process to help you identify them including fav icon for website. Head over to this Microsoft Edge blog post for a list of detailed improvements.

Detailed process attribution for different Microsoft Edge processes in Task Manager

NOTE: This feature is available to Windows Insiders that are running the latest Microsoft Edge Canary or Dev builds. Insiders can download the latest version here. This feature is also rolling out to a subset of Insiders in the Dev Channel at first, to help us quickly identify issues that may impact performance and reliability. Rest assured they will be gradually rolled out to everyone in the Dev Channel.

Eco mode in Task Manager

Task Manager has a new experimental feature in this build called “Eco mode” which provides users with an option to throttle process resources. It will also help identify apps that are already running in Eco mode. This feature is helpful when you notice an app consuming high resources and would like to limit its consumption so that the system gives priority to other apps which will lead to faster foreground responsiveness and better energy efficiency.

A context menu in Task manager giving users the ability to turn on Eco mode in Build 21364

Here is how to enable Eco mode for any process:

  1. Open Task Manager.
  2. Click on Processes tab.
  3. Right-click on a child process or an individual process.
  4. Click on “Eco mode” in the context menu to apply throttling.
  5. The status column in the Processes tab should show Eco mode for the process.

This same process also works on the Details tab too.

If “Eco mode” is greyed out, then it’s a parent/group process. You can expand the process tree to apply Eco mode on one of its child processes.

And if Microsoft Edge (or Chrome) is showing “Eco mode” as enabled but you did not apply it, this is due to both Microsoft Edge and Chrome experimenting with lowering base priority and applying power efficiency APIs to improve performance which is similar to what Task Manager is doing to identify “Eco” efficient apps. You may see other apps with “Eco mode” if they adapt to similar techniques to improve performance.

You can submit feedback on these recent Task Manager changes in Feedback Hub under Desktop Environment > Task Manager.

NOTE: This feature is rolling out to a subset of Insiders in the Dev Channel at first, to help us quickly identify issues that may impact performance and reliability. Rest assured they will be gradually rolled out to everyone in the Dev Channel.

Japanese 50-on touch keyboard

We’re excited to introduce a new touch keyboard layout for Japanese, 50-on touch keyboard. 50-on touch keyboard is a popular layout widely used for Kiosk devices in Japan. It allows you to input Japanese texts intuitively without knowing how to compose Hiragana characters.

The 50-on keyboard layout for the Japanese virtual keyboard in Windows 10 build 21364

You can switch to 50-on layout from [⚙] > [50-on]. It also provides alphabet and symbol views newly designed specifically for the layout. You may notice some known issues where inserting a full-width space using Shift key doesn’t work and typing some characters shows garbled suggestion candidates. We’re actively working on addressing them. Thank you for your patience. We’re looking forward to your feedback via [Give feedback] menu!

Virtual keyboard settings menu in Windows 10 displaying all layout options for Japanese

There are also a couple of smaller changes in this build, such as Night Light enabling or disabling immediately when toggled manually:

  • Based on feedback, we’re updating the notification that used to say “We need to fix your account (most likely your password changed)”, to be more representative of what it’s for, and now say “Select here to sign in to your account to continue using apps between this device and your other devices.”
  • When you turn on or off night light manually, for example via the Action Center, night light will now turn on immediately rather than slowly transition.

As usual, you'll also find a long list of fixes in this build, though some other improvements are hidden in Microsoft's list, like support for out-of-process x64 shell extension on ARM64 devices:

  • We fixed an issue causing some USB attached printers to no longer work after upgrading to Build 21354 and higher.
  • Theme-aware splash screens are now visible again in this build.
  • We fixed an explorer.exe crash impacting Insiders in the last few builds.
  • We fixed an issue resulting in the About page in Settings appearing blank sometimes.
  • We fixed an issue resulting in some corrupted characters across Settings in the previous build, for example in the “These folders won’t be indexed” text on the Searching Windows page.
  • We fixed an issue that could result in the Windows Update status in the Settings header not being correct.
  • We fixed an issue where the “Manage Disks and Volumes” page in Settings was incorrectly displaying HDDs as SSDs.
  • We fixed an issue where chkdsk was sometimes not calculating elapsed time correctly.
  • We fixed an issue where some of the text in the UAC dialog wasn’t displaying correctly.
  • We fixed an issue with where the recent changes to the default spacing in File Explorer, the icon in the address bar was a little too close to the side.
  • We fixed an issue resulting in the New Text Document button in File Explorer’s ribbon not working.
  • We fixed an issue where File Explorer was unexpectedly not pinned for some Insiders after resetting or clean installing their PC in recent builds.
  • We fixed an issue where the battery icon in the taskbar looked like it was at 90% when it was actually at 100% at some scaling.
  • We fixed an issue impacting Windows Hello reliability in recent flights.
  • We fixed an issue where Windows Firewall was unexpectedly giving an error recently when updating existing rules to Block.
  • We fixed an issue where sihost.exe would crash sometimes when trying to use the Share option when right clicking an app in Start.
  • We fixed an issue impacting Search reliability for some Insiders in the last two builds. Please let us know if you continue experiencing crashes after upgrading, as it may be a different underlying root cause.
  • We fixed an issue resulting in some Insiders seeing a CRITICAL PROCESS DIED bug check in recent builds.
  • We fixed an issue that could result in freezing in certain games recently when bringing up overlays when HDR was enabled.
  • We fixed an issue where certain images expectedly wouldn’t appear in your clipboard history after copying them from a webpage using Microsoft Edge.
  • We fixed an issue where elements of the Japanese IME candidate window may get truncated when using a text scaling of 200%.
  • We fixed an issue where after using the gesture on the touch keyboard’s space bar to move your cursor, the Shift and CTRL key displayed states may become out of sync with the actual state.
  • We fixed an issue that was preventing x64 apps on ARM64 like Cyberlink PhotoDirector from detecting the presence of the C++ redistributables.
  • We fixed and issue preventing split screen mode for Auto HDR from working.
  • We added support for x64 out of process shell extensions on ARM64.
  • 3D Viewer and Print 3D app shortcuts have been moved back into Start.

Finally, the list of known issues is fairly small this time around and it seems like Microsoft is ironing out a lot of the problems in these builds, maybe because the update should be nearly finalized. Here's what you need to look out for:

  • We’re looking into reports of the update process hanging for extended periods of time when attempting to install a new build.
  • [News and interests] Pressing ESC key to dismiss an opened context menu in the flyout dismisses the whole flyout instead.
  • [News and interests] Sometimes the news and interests flyout cannot be dismissed with pen.
  • We’re investigating an issue where elements of Search (including the search box in File Explorer) are no longer displaying correctly in dark theme.
  • The Windows Camera App currently does not respect the default brightness setting set via the new Camera Settings page.
  • We’re working on a fix resulting in WSL users finding that File Explorer launch performance regressed after upgrading to Build 21354 and higher.
  • [ADDED] Some Insiders are reporting error 0x80092004 installing KB5001030 – 2021-02 Cumulative Update Preview for .NET Framework 3.5 and 4.8 after updating to this build. We are working on a fix for a future build.

As usual, you can download the update from Windows Update manually by checking manually, but it should be installed sooner or later if you're enrolled in the Dev channel. It's still unclear if all these changes will make their way to a full feature update later this year or if plans have changed in light of the reported Windows 10X delays.

Report a problem with article
The Falcon 9 with a Crew-2 Dragon atop it
Next Article

NASA has delayed the Crew-2 Dragon mission to the ISS

A meeting with multiple presenters highlighted on Google Meet
Previous Article

Google redesigns Meet on the web, adds low-light improvements, and more

35 Comments - Add comment

Advertisement