Microsoft ha già iniziato da diversi mesi a lavorare sul prossimo grande update (nome in codice 19H1) e proprio in queste ore ha provveduto a rilasciare una nuova build per gli utenti Insider iscritti al ramo Fast Ring.

La nuova build di Windows 10 19H1 viene identificata dal numero 18317 e oltre alla correzione di diversi bug troviamo: Cortana e Ricerca ora sono separati nella barra delle applicazioni, drag and drop per installare nuovi font, processo del menu Start ora separato per garantire una migliore affidabilità, impostazioni Insider semplificate e migliorie per la Windows Console.

Aggiornamento x1 – 25-01-2019

Microsoft ha rilasciato una nuova build minore per gli Insider (18323) che va a migliorare il supporto alle immagini RAW (estensione disponibile a questo link), ottimizzando il tame Light e correggendo diversi bug minori. Trovate il post ufficiale Microsoft dedicato alla build a questo link.

Di seguito la lista delle novità completa segnalate da Microsoft:

Separating Search and Cortana

Going forward, we’ll be decoupling Search and Cortana in the taskbar. This will enable each experience to innovate independently to best serve their target audiences and use cases. Some Insiders have had this update for a few weeks now, and we appreciate all the feedback we’ve received about it so far! For those new to this update, when it rolls out to you, you’ll find clicking the search box in the taskbar now launches our experience focused on giving you the best in house search experience and clicking the Cortana icon will launch you straight into our voice-first digital assistant experience.

Other available Search and Cortana settings have also now been split between the two, along with the familiar group policies.

This change is one of several we’ve made throughout this release to improve your experience in this space, including updating the search landing page design, enhancing your search results, and integrating Microsoft To-Do with Cortana. If you have any further feedback, please don’t hesitate to share it with us here.

Note: Cortana is currently only available in supported markets.

The next step in improving Start reliability

As some of you may already know, up until now Start in Windows 10 has been hosted by something called ShellExperienceHost.exe. In order to provide you the best possible Start experience, we’re separating it into its own process, called StartMenuExperienceHost.exe. This has a number of benefits, including simplifying debugging and insulating Start from potential issues impacting other surfaces. This has been running as an experiment for a few weeks now and we’ve seen measurable improvements in the reliability amongst those that have the change, so we’re rolling it out to everyone.

We’re also making a change so that Start no longer suspends, which improves launch time.

A Better Font management experience in Settings

Insiders today can now drag and drop font files from File Explorer into the modern Settings > Fonts page to install them. After installation, click on the font in the Font page, to view the different font faces associated with the font and all the details of the font. You can also uninstall the font from this font details page. Drag and drop font installation by default is installed as a per-user font which does not require elevation, hence it will not be available for other users. To install the font for all users in the device, use the “Install for all Users” option by right clicking the font on file explorer.

A simpler Windows Insider Program Settings page

We are introducing a simplified Windows Insider Program Settings page via Settings > Update & Security > Windows Insider Program with Build 18317. The goal is to make the end-to-end experience of signing up for the Windows Insider Program and setting up your PC to take new builds much easier by simplifying the experience and removing some of the clutter. You’ll find that all the same functionality is still there.

Under “Pick your Insider settings” is where you can change your Insider ring on your PC.

Windows Console Updates

We’ve made several fixes & improvements in Windows Console in and leading up to build 18317, including:

• Fixed spurious text artifacts being displayed when running cscope in a Linux VM via ssh
• Fixed GitHub issue 296 where the incorrect mouse button ID was being reported when a mouse button was released, resulting in an “unexpected mouse-drag behavior” regression
• Fixed GitHub Issue 313, enabling colors above index #15 to be set via VT OSC 4
  • Colors <= 99 fixed in this build
  • Colors > 99 fixed in up-coming build
• Corrected sizing issues for Linux alt-buffer apps (e.g. vim, emacs, etc.) resulting in more reliable resizing
• Fixed some issues with Consoles growing in height if scroll-forward is disabled
• Fixed ConPTY, enabling underline VT sequences to now pass correctly, allowing ConPTY-enabled apps (e.g. VSCode’s integrated terminal) to correctly receive and display underlined text
• Made ConPTY flush its output buffer before terminating ensuring apps receive all input and display correct output
• When running Tmux, correctly restore state after Win + D, resulting in Tmux’s last line of text rendering correctly
• Fixed Console to preserve a Console window’s currently colored text when executing Cmd.exe
• If using raster fonts, Console now correctly preserves the user’s font after running .NET Core code (which defaults to UTF-8 codepage 65001)
• Correct how Console scrolls text region, fixing how text is rendered in Linux’ `screen`
• Significantly improved performance of ConPTY – perf now very close to “raw pipe”

General changes, improvements, and fixes for PC

• We fixed an issue resulting in File Explorer unexpectedly having a lock on USBs when trying to safely eject them.
• We fixed an issue resulting in frequent bugchecks (GSODs) in the last two flights, citing an error with bindflt.sys.
• We fixed an issue resulting in frequent bugchecks (GSODs) in the last flight, citing error KERNEL_LOCK_ENTRY_LEAKED_ON_THREAD_TERMINATION.
• We fixed an issue resulting in not being able to connect to VMs using Hyper-V console after upgrading to recent flights. This issue also impeded the ability to connect to VMs with Enhanced Sessions enabled.
• We fixed an issue resulting in some full screen games showing a black screen in recent flights even though they worked in windowed mode.
• We fixed an issue resulting in CDP User Service periodically unexpectedly using a high amount of CPU in recent flights.
• We fixed an issue causing text in the Windows Security app to be incorrect or potentially missing altogether.
• We fixed an issue from recent flights where clicking the network button on the sign-in screen didn’t work.
• We fixed an issue resulting in certain devices not being able to wake from hibernation recently. There were two possible symptoms on wake if you were impacted – one was a black screen, one was a screen that continued to say “hibernating…”.
• We fixed an issue resulting in Display Settings crashing in recent builds. If you were impacted, this would have also had the symptom that clicking System or Ease of Access from the main Settings page may crash Settings.
• We fixed an issue with certain touch keyboard languages where pressing AltGr + [any key] on the full layout would dismiss the touch keyboard.
• We fixed an issue where Windows Sandbox wouldn’t launch on PCs with multiple GPUs.
• When Scan Mode is on and Narrator is on a slider, the left and right arrows will decrease and increase the slider. Up and down arrows will continue to navigate to the previous or next paragraph or item. Home and End will move the slider to the beginning or the end.
• The Narrator list of headings command now works as expected in Chrome.
• We improved Narrator support for Microsoft Teams.
• For cursor and pointer, fixed returning to the right mouse pointers when changing back to the original size and colors.
• We fixed an issue where some devices would fail to install an update with error code If you are updating from 18309 or newer this issue will be fixed for this update, if you are updating from a build prior to 18309 it will be fixed for the next update.