Microsoft Releases Windows 10 Insider Preview Build 21364, Presents Linux GUI in WSL – Some time ago Microsoft released Windows 10 Insider Preview Build 21364 for Insider Dev Channel users, according to their weekly schedule.
And in this update, interestingly there is one new feature that users have been waiting for for a long time, namely Linux GUI App support in WSL, in other words, users can now run Linux applications directly on Windows Subsystem For Linux in Windows 10.
More New Features?
In addition to linux GUI, task manager now also supports Microsoft Edge Proces Classifications, so that with it every process, plugin, extension, and others will run in separate proccess, so that if there is one problem, we can close the proccess directly in task manager without affecting the other proccess.
Well exactly as in the picture above, each process will be distinguished by an icon depending on the classifications of the proccess, so the user should not be confused to see and find certain proccess there.
Eco Mode in Task Manager
Well the third, if you notice in Windows 10 Insider Preview Build 21364, when you right-click on the processes section, then there will appear eco mode option, where this option serves to throttling process resources, and is expected to save the user’s device resources a little, especially in battery energy efficiency.
In addition to the above, there is also a Japanese 50-on touch keyboard, which is useful if you want to enter Japanese text without knowing how to compose Hiragana characters.
Well more or less that’s all new features are given, and of course each get a positive response from users, especially linux GUI features that have been long enough users expect.
Changes and Improvements
- 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.
- 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.
- 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.