Microsoft ha provveduto a rilasciare in queste ore una nuova build Redstone 4 relativa al ramo di sviluppo Fast per gli utenti Insider che hanno scelto di provare in anteprima questa nuova versione.

La nuova build dedicata a Windows 10 in fase di rilascio per gli Insider viene identificata dal numero 17110 ed essendo Redstone 4 in fase finale di sviluppo porta modifiche marginali e diverse correzione di bug, in particolare è stata aggiunta una nuova funzione per le aziende che permette di eseguire azioni personalizzate (tramite script) durante la fase di aggiornamento.

Aggiornamento x1

Poco dopo il rilascio della build 17110 si è scoperto un bug legato al Microsoft Store: Impossibilità all’avviarlo, scomparsa delle Tile apposita nel menu applicazioni o dalla barra delle applicazioni. Microsoft sta lavorando alla correzione di questo problema e invita i propri utenti a NON eseguire il reset dell’applicazione in quanto creerebbe solo maggiori problemi.

In attesa di una soluzione definitiva, di seguito vi proponiamo una correzione proposta da un utente che ripristina il corretto funzionamento dello Store:

• Avviare PowerShell come amministratore premendo il tasto Windows + X o facendo clic con il pulsante destro del mouse su Start
• Una volta che PowerShell è avviato, copiare e incollare quanto segue: Get-AppXPackage *WindowsStore* -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
• Premere invio e riavviare il PC

——

Di seguito la lista completa delle modifiche apportate con questa build segnalate da Microsoft:

Enterprises can now run custom actions during feature update: In RS4, we are adding a new feature that will enable your enterprise to run your own custom actions/scripts synchronously with setup. Setup will execute custom actions during two update phases controlled by using preinstall.cmd or precommit.cmd:

• Pre-install: This would be just before all the system and device compatibility scans run.
• Pre-commit: This would be just before the system reboots into the offline phase.

Setup also migrates the scripts for future updates. In the event of an update failure or rollback, a failure.cmd script can be used to perform custom operations or undo actions of previous custom scripts.

Run (Migrate):

• C:\Windows\System32\update\run\<GUID>\preinstall.cmd
• C:\Windows\System32\update\run\<GUID>\precommit.cmd
• C:\Windows\System32\update\run\<GUID>\failure.cmd
• C:\Windows\System32\update\run\<GUID>\reflectdrivers\foo.inf
• C:\Windows\System32\update\run\<GUID>\reflectdrivers\foo.sys

Run Once (Do not migrate):

• C:\Windows\System32\update\runonce\<GUID>\preinstall.cmd
• C:\Windows\System32\update\runonce\<GUID>\precommit.cmd
• C:\Windows\System32\update\runonce\<GUID>\failure.cmd
• C:\Windows\System32\update\runonce\<GUID>\reflectdrivers\bar.inf
• C:\Windows\System32\update\runonce\<GUID>\reflectdrivers\bar.sys

Enterprises can run post rollback scripts in system context​: Current /postrollback scripts run if the first user logs in after the rollback has admin privileges. We received feedback from several enterprises that most of their employees don’t have admin privileges. With RS4, we are enabling /postrollback scripts to run in admin context or system context.

We are not changing the behavior of the existing /postrollback switch. We have added a new switch /postrollbackcontext “xxx” to be used along with /postrollback switch to specify in which context should the scripts be executed:

• To run /postrollback scripts in system context

–        setup.exe /postrollback c:\Fabrikam\setuprollback.cmd /postrollbackcontext system

• To run /postrollback scripts with first user to login have admin privileges (admin context)

–        setup.exe /postrollback c:\Fabrikam\setuprollback.cmd /postrollbackcontext admin

Windows containers

Docker for Windows users, we are flighting the matching Windows container images of Server Core and Nano Server to the Docker Hub for continued testing and feedback.  Thank you for all the great feedback and please keep it coming!

General changes, improvements, and fixes for PC

• We fixed an issue where buttons on Game bar were not centered correctly.
• We fixed an issue where a small number of PCs might have experienced one CPU under persistent high load or even a bugcheck (GSOD with error DPC_WATCHDOG_VIOLATION).
• We fixed an issue where tearing a PDF tab in Microsoft Edge would result in a bugcheck (GSOD).
• We’ve updated Start so that it now follows the new Ease of Access setting to enable or disable hiding scrollbars.
• We fixed an issue resulting in some app icons appearing distorted in Task View.
• We fixed an issue where making a pinch gesture over the open apps in Task View might result in no longer being able to scroll down to Timeline.
• We fixed an issue where pressing and holding on a card in Timeline would open the corresponding app, rather than bringing up a context menu.
• We fixed an issue resulting in the title bar overlapping content when you opened your lists in Cortana’s notebook.
• We’ve updated the new notification to fix blurry apps so that it now will persist in the Action Center to be accessed later once the toast has timed out and dismissed.
• We fixed an issue where it wasn’t possible to open a new inPrivate window of Microsoft Edge from the taskbar jumplist while in Tablet Mode.
• We fixed an issue where dragging a Microsoft Edge tab out of the window and releasing hold of it somewhere over the desktop might periodically result in a stuck invisible window.
• We fixed an issue resulting in DirectAccess not working in recent builds, where the connection would be stuck with status “Connecting”.
• We fixed an issue where the touch keyboard number pad would show the period as a decimal separator for countries that use the comma as a decimal separator.
• We fixed an issue resulting in not being able to turn on and off third party IMEs using the touch keyboard.
• We fixed an issue resulting in numbers not being inserted when flicking up on the top row of letters in the wide touch keyboard layout.

Aggiornamento x2

Breve update per segnalarvi che Microsoft ha provveduto questa sera a rilasciare una nuova Build di Windows 10 Redstone 4 per gli utenti Insider (17112) che porta diverse correzione di bug. Da segnalare inoltre due problemi noti: Windows Mixed Reality viene eseguito con un numero di fps ridotto (8-10 fps) e il bug relativo allo Store scoperto la scorsa build.

Di seguito la lista completa delle modifiche apportate con questa build segnalate da Microsoft:

• We fixed an issue where selecting a notification after taking a screenshot or game clip opened the Xbox app’s home screen instead of opening the screenshot or game clip.
• We fixed an issue where EFI and Recovery partitions were unexpectedly listed in Defragment and Optimize Drives.
• We fixed an issue optimizing drives in Defragment and Optimize Drives didn’t work in the last few flights.
• We fixed an issue resulting in a permanently black window if you dragged a tab out of a Microsoft Edge window, pulled it up to the top edge of the screen, and moved it back down and released it.
• We fixed an issue where the warning on Windows 10 S when trying to run non-Microsoft Store apps from File Explorer might end up stuck behind the File Explorer window.
• We fixed an issue where there was some unexpected extra space in the File Explorer navigation pane before the chevron icons to expand/collapse folders.
• We fixed an issue where if focus was set inside Action Center pressing Esc wouldn’t close the Action Center window.
• We fixed an issue that could result in ShellExperienceHost periodically waking the device from hibernate if active live tiles were pinned to Start.
• We fixed an issue where navigating to Settings > System > Focus Assist > “Customize your priority list” could crash Settings.