• 6 commenti

Disponibile la nuova build (21364) di Windows 10 per gli utenti Insider | Dev Channel

Microsoft da pochi minuti ha provveduto a rilasciare una nuova build di Windows 10 relativa al ramo di sviluppo Dev Channel per gli utenti Insider.

Ricordiamo che il ramo di sviluppo Dev Channel legato a questa build riguarda una versione futura di Windows 10 non abbinate a una versione specifica di Windows 10 (come ad esempio accade nel ramo Beta Channel).

La nuova Build di Windows 10 in fase di rilascio per gli utenti Insider viene identificata dal numero 21364 e implementa le seguenti novità:

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.

Showing Microsoft Edge process classification support 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.

Right-click on child processes in Task Manager to enable “Eco mode”.

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 new 50-on touch keyboard layout for Japanese.

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!

Enabling the new 50-on touch keyboard.

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.

Nuova pagina Telegram dedicata ESLUSIVAMENTE alla segnalazione di VERE offerte Amazon Italia!

Commenta la notizia

Vuoi un'immagine profilo personalizzata? Impostala su Gravatar utilizzando la stessa e-mail associata ai commenti.

  1. Il busca ha detto:

    grandissimi! cosi presto!! questo è un enorme passo avanti. windows sta diventando l’unico punto di partenza. Che sforzo immane. Bravi

    • Arcturus ha detto:

      Peccato che in altre circostanze, con implementazioni ben più semplici, si siano fatti attendere inutilmente. Se ne fossero usciti con Sun Valley 3 anni fa, oggi avrebbero molta più visibilità.

      • Il busca ha detto:

        Non si può avere tutto. Questo è davvero tanto tanto tanto. Certo non per tutti, ma il pubblico è fin troppo volubile. Meglio concentrarsi sulla funzionalità che è quello che resta.

        • Arcturus ha detto:

          @Fabio Buscaroli

          Certo…Anche se per quello che vale potevano anche incaricare altri team di completare questo lavoro. Di certo i soldi non gli mancavano per assoldare 4 designer.

  2. Lucas992X ha detto:

    WSL con GUI sembra tanta roba, spero arrivi presto nel ramo stabile 🤞

  3. Il busca ha detto:

    Già! le premesse sono davvero ottime. Io dismetto due pc linux e un dual boot che mi crea problemi. Non vedo l’ora

Lascia un commento

Il tuo indirizzo email non sarà pubblicato. I campi obbligatori sono contrassegnati *