• 0 commenti

Disponibile la nuova build (20231) 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 nuovo 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 la 20H2 disponibile nel ramo Beta Channel).

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

Improving relevancy of initial device setup

Based on feedback, we’re exploring adding a page to Windows setup (OOBE) to help better understand how you plan to use your device and aid in customizing your device given your intended usage.

Displaying a page in OOBE prompting you to customize your device by saying if you plan to use it for things like gaming or business.

This is the initial wave of work for this feature, and Insiders may notice different options presented in OOBE depending on what they select, however at this time Insiders will not notice any other configuration differences after exiting OOBE. We look forward to sharing future improvements in this space.

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. NOTE: You will see this feature if you choose to reset your PC and when you do a clean install of Windows. You can find the ISO for Build 20231 here on our download page later today.

Better Management Options for App Default File Associations 

Enterprise customers can now modify file associations on a per-user or per-device basis. This change will apply to existing users as well as users with new deployments. This means that IT admins can set which apps will automatically open various file types or links. For example, this makes it easy to set Microsoft Edge as your organization’s default browser, or always open PDFs in your organization’s preferred app. Leveraging this group policy for the default browser and common file types means that your organization’s end users will not have to decide on these defaults themselves.

Deployment/Testing Steps:

  1. Generate Default Application Associations XML file by following this page.
  2. Manually modify the XML by adding 2 new properties:
  3. Add Version=”1″ to the DefaultAssociations tag.
  4. Add Suggested=”True” to any Association tag.
  5. Enable the group policy to set the default file associations by following this doc.
  6. Reboot or log in as the user.

Please note: If your device does not have this feature enabled, the policy will fall back to the default logic and will not respect the “Version” and “Suggested” fields of the policy.

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.

Updates for developers

The Windows SDK is now flighting continuously with the Dev Channel. Whenever a new OS build is flighted to the Dev Channel, the corresponding SDK will also be flighted. You can always install the latest Insider SDK from aka.ms/InsiderSDK. SDK flights will be archived in Flight Hub along with OS flights.

Changes and Improvements

Fixes

  • We fixed the vEthernet adapter disconnecting inside of the Windows Subsystem for Linux. Please see this GitHub thread for full details.
  • We fixed an issue that could result in your ALT + Tab order changing unexpectedly and leading you to switch to the wrong window.
  • We fixed an issue that could result in Action Center and notification buttons not being visible after switching between High Contrast Black and High Contrast White.
  • We fixed an issue where the “Show audio alerts visually” option under Settings > Ease of Access> Audio wasn’t functioning for incoming notifications.
  • We fixed an issue where if the PC was locked using with Narrator running, dismissing the lock screen wouldn’t announce the signed in username on the login screen.
  • We fixed an issue when using Narrator and logging in with Windows Hello, Narrator wouldn’t announce the error message if your face wasn’t recognized.
  • We fixed an issue resulting in audio and microphone glitches over Bluetooth for certain devices. As a reminder, when encountering issues in this space, please take a moment to capture a repro trace, as it helps the teams investigate. More details about capturing traces available .
  • We fixed an issue impacting Task View reliability.
  • We fixed an issue resulting in the Windows Hello setup camera preview in OOBE displaying in the wrong position if you rotated your device into portrait mode during setup.
  • We fixed an issue resulting in Settings hanging on launch for some Insiders.
  • We fixed an issue resulting in systemsettingsbroker.exe crashing for some Insiders.
  • We fixed an issue where the HideRecentJumplists MDM Policy wasn’t taking effect.
  • We fixed an issue that could result in duplicate cloud provider entries appearing in the File Explorer navigation pane.
  • We fixed an issue resulting in PDF previews no longer displaying in File Explorer.
  • We fixed an issue resulting in the touch keyboard unexpectedly dismissing after setting focus to the search box in File Explorer.
  • We fixed an issue where when typing with the Chinese Pinyin IME, if your text included an apostrophe, then after finalizing your composition by pressing Shift the result would display a garbled character.

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.


Lascia un commento

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