Microsoft Bumps Windows 10 Current Branch to Build 10563.332 with Cumulative Update KB4020102
Microsoft released an unexpected patch for Windows 10 Creators Update, aka Windows 10 Version 1703, that addresses several quality improvements.
Although we typically see cumulative updates of a security or routine nature released for Windows 10 on Tuesdays in the course of a month but this week we got a Thursday surprise when Microsoft pushed out a routine update for Windows 10's latest version.
This update, which arrives on your Windows 10 Creators Update based system as Knowledge Base KB4020102, and moves what is now the Current Branch release of Windows 10 to Build 15063.332.
The Creators Update which is also known as Windows 10 Version 1703 began its public roll out last month and, as we wrote about earlier this week, it is on schedule and running smooth enough that Microsoft is expanding the number of devices being targeted for the update.
I mention that the update is still rolling out because some of you may not have received it yet and when you read this and try to download the update it will not be available on your device. That is expected until you have upgraded to the Creators Update.
However, when you do finally get the update, this patch or a subsequent one since they are all cumulative, will also get installed to bring your device fully up to date.
For those of you already running the Creators Update the following items have been addressed in this patch:
-- Addressed issue where NTLM fails to generate a challenge response when CredGuard is enabled, NTLMv2 is used, and no target information is provided by the server.
-- Addressed issue where Internet Explorer does not respect the “Send all sites not included in the Enterprise Mode Site List to Microsoft Edge” policy when opening favorites.
-- Addressed issue in Internet Explorer 11 where a non-administrator user is not able to install an ActiveX control.
-- Addressed issue where, after starting Split View, some apps (Microsoft Edge, Hub, Cortana, etc.) no longer receive input when multiple displays are in use.
-- Addressed issue with an unnecessary scrollbar in the logon credential provider dialog, which may block use of other fields when the dialog has multiple fields.
-- Addressed issue where, during a VM reset, the VM goes into Second Level Paging (SLP) even if there is enough balancer available memory on the host.
-- Addressed issue where some non-Unicode fonts (Courier, MS Sans Serif, etc.) do not render characters correctly on non-Latin, single-byte system locales (Greek, Hebrew, Arabic, etc.). Black bars or other artifacts appear instead.
-- Addressed issue with an SMS/messaging app that stops working when attempting to delete messages.
-- Addressed issue where, after installing the Creators Update, audio output through external decoders no longer works.
-- Addressed issue where the IoT shell fails to keep monitored background applications running.
-- Addressed issue with high latency when using the Universal Windows Platform (UWP) MIDI API.
-- Addressed issue where network printers may fail to install when using the printer vendor’s setup software on machines with less than 4GB of RAM. These printers will install if you install from the Settings app or from Devices and Printer in Control Panel.
-- Addressed issue where PrintBRM fails to restore the Print Queue Configurations when printer names are identical and a port is set to FILE:.
-- Addressed issue with per user proxy settings not migrating to machine proxy settings.
Patches were not released for other versions of Windows 10 including Version 1511 (November Update) and 1607 (Anniversary Update). It actually makes sense for the Creators Update to get this patch because these will be improvements that are necessary in the short period of time since it was made available to the general public.
----------
But, wait...there's probably more so be sure to follow me on Twitter and Google+.
Read more about:
MicrosoftAbout the Author
You May Also Like