This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:
-
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 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.
-
Addressed issue where non-English characters showed incorrectly in apps that attempt to wrap/replace the in-box console.
-
Addressed issue when trying to set a default lockscreen using the following Group Policy, you do not see the defined image on the lockscreen but you do see the defined image in Settings under lockscreen settings.
Computer Configuration\Administrative Templates\Control Panel\Personalization\"Force a specific default lock screen image"
If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.