Dans le cadre du premier Patch Tuesday de 2019, Microsoft vient de publier plusieurs nouvelles mises à jours cumulatives. Elles s’adressent aux différentes versions de Windows 10 prises en charge. Windows 10 v1809 est également concerné.
Cette grande maintenance mensuelle concerne les appareils sous Windows 10 Fall Creators Update (v1709), Windows 10 April 2018 Update (v1803) et Windows 10 October 2018 Update (v1809). Ils sont concernés par les mises à jours cumulatives KB4480116, KB4480966 et KB4480978.
Microsoft propose un focus sur la sécurité avec plusieurs corrections de failles et de vulnérabilités. Les journaux de modifications indiquent des correctifs pour certaines applications natives (Microsoft Edge et Internet Explorer), le moteur de script Microsoft, le noyau Windows et certains de ses composants.
A noter que ce Patch Tuesday de janvier 2019 s’accompagne également de mises à jour de Delta.
Dans le cas de la mise à jour cumulative pour Windows 10 v1809, il est possible que d’autres améliorations soient proposées. October 2018 Update a été publié le 2 octobre, mais en raison d’un bug critique, son déploiement a été stoppé en urgence. La mise à niveau a refait surface en novembre. Depuis les équipes apportent différents correctifs pour résoudre les derniers bugs.
Pour le moment nous n’avons pas de retour concernant des soucis d’installation. Il faut cependant rester prudent car le déploiement ne fait que commencer.
Patch Tuesday de janvier 2019.
merci à GinjFoJanuary 8, 2019—KB4480116 (OS Build 17763.253)
Addresses a security vulnerability in session isolation that affects PowerShell remote endpoints. By default, PowerShell remoting only works with administrator accounts, but can be configured to work with non-administrator accounts. Starting with this release, you cannot configure PowerShell remote endpoints to work with non-administrator accounts. When attempting to use a non-administrator account, the following error will appear:
“New-PSSession: [computerName] Connecting to remote server localhost failed with the following error message: The WSMan service could not launch a host process to process the given request. Make sure the WSMan provider host server and proxy are properly registered. For more information, see the about_Remote_Troubleshooting Help topic.”
Addresses an issue in which using esentutl /p to repair a corrupt Extensible Storage Engine (ESE) database results in a mostly empty database. The ESE database is corrupted and cannot be mounted.
Security updates to Microsoft Edge, Internet Explorer, Windows App Platform and Frameworks, Windows MSXML, Windows Kernel, Windows Storage and Filesystems, Windows Wireless Networking, Microsoft JET Database Engine, Windows Linux, Windows Virtualization, and the Microsoft Scripting Engine.
January 8, 2019—KB4480966 (OS Build 17134.523)
Addresses a security vulnerability in session isolation that affects PowerShell remote endpoints. By default, PowerShell remoting only works with administrator accounts, but can be configured to work with non-administrator accounts. Starting with this release, you cannot configure PowerShell remote endpoints to work with non-administrator accounts. When attempting to use a non-administrator account, the following error will appear:
“New-PSSession: [computerName] Connecting to remote server localhost failed with the following error message: The WSMan service could not launch a host process to process the given request. Make sure the WSMan provider host server and proxy are properly registered. For more information, see the about_Remote_Troubleshooting Help topic.”
Security updates to Internet Explorer, Microsoft Edge, Windows App Platform and Frameworks, the Microsoft Scripting Engine, Windows Kernel, Windows Storage and Filesystems, Windows Virtualization, Windows Linux, Windows MSXML, and the Microsoft JET Database Engine.
January 8, 2019—KB4480978 (OS Build 16299.904)
Addresses a security vulnerability in session isolation that affects PowerShell remote endpoints. By default, PowerShell remoting only works with administrator accounts, but can be configured to work with non-administrator accounts. Starting with this release, you cannot configure PowerShell remote endpoints to work with non-administrator accounts. When attempting to use a non-administrator account, the following error will appear:
“New-PSSession: [computerName] Connecting to remote server localhost failed with the following error message: The WSMan service could not launch a host process to process the given request. Make sure the WSMan provider host server and proxy are properly registered. For more information, see the about_Remote_Troubleshooting Help topic.”
Security updates to Internet Explorer, Microsoft Edge, Windows App Platform and Frameworks, the Microsoft Scripting Engine, Windows MSXML, Windows Kernel, Windows Storage and Filesystems, Windows Virtualization, Windows Linux, and the Microsoft JET Database Engine.