Patch Tuesday was almost two weeks ago, however not uncommon for Microsoft to discharge cumulative updates between the month. The previous week, Windows 10 users on versions 1607 and 1703 got love, and already, the company is releasing a good solid update for the people on the Windows 10 Fall Creators Update, or version 1709.
Today’s update is KB4103714, also it brings the build number to 16299.461. It could be manually downloaded here, and also it contains the following fixes:
Addresses additional complaints about updated time zone information.
Addresses an issue that causes Web browser dialogs on a second monitor also to appear on the principal monitor while using extended display.
Addresses a huge concern with Microsoft Edge browser windows in remote sessions.
Addresses a reliability issue in .NET applications when exercising on a Japanese IME inside of a textbox.
Addresses a reliability issue which can cause Microsoft Edge along with applications to cure responding as soon as you create a new audio endpoint while audio or video playback is beginning.
Addresses an issue with Bluetooth devices neglecting to receive data after restart.
Addresses an issue that can stay away from the touch keyboard from appearance reliably in some circumstances.
Addresses an issue where UWP apps that store local crash dumps as part of the local app data folders may not be cleared using Disk Cleanup or StorageSense. In such cases, LocalDumps isn’t enabled.
Addresses an element that prevents adding performance counters for the Performance Monitor on systems with so many processors.
Addresses an issue that causes BitLocker to enter recovery mode when updates are applied.
Addresses problems where expired VPN certificates aren’t deleted, slowing application performance.
Addresses an issue that causes sporadic authentication issues when making use of Windows Authentication Manager.
Addresses an element that causes client applications used Windows Authentication Manager to relinquish working when making a request at the server.
Addresses an issue with your invalidation of the Windows Authentication Manager token cache.
Addresses an issue that cause a timeout error every time a VPN attempts to disconnect at a device that can be in the Connected Standby state.
Provides an explicit error when plugins never connect to prevent timeouts.
Addresses a predicament where running the DiskShadow utility after adding a persistent memory controller causes RetrieveAllVirtualMachinesComponentsMetadata() to eliminate responding.
Addresses an element that causes a VM to throw a slip-up after creating the VM with static memory. This takes place when you enable HYPER-V and disable NUMA from your BIOS on a physical machine that features more than 64 logical processors. Whole body is “The info is invalid. (0x8007000D)”, along with VM fails to start.
Addresses an issue that occurs when multiple processes are restricted by rate, using job objects. This is going to cause various symptoms including, even though not limited to, system-process CPU spikes, interrupt-time CPU spikes, high privileged time on some CPUs, and increased system or processor queue lengths.
Addresses an element that causes docker builds to fail when using the error message “hcsshim::ImportLayer failed in Win32: The product cannot chose the path specified.”
Addresses an aspect in which Windows 10 clients that authenticate to 802.1x WLAN access points do not apply Group Policy permissions, run scripts, or retrieve roaming profiles at user logon. This occurs because Kerberos authentication fails for \\domain\sysvol, \\domain
etlogon, and various other DFS paths.
Addresses one factor in a RemoteApp session plenty of clicking through the foreground window in order to become unresponsive by using grouped windows.
Addresses very important in a RemoteApp session that may result in a black screen when maximizing software on a secondary monitor.
Addresses a worry with application association inside the DISM tool.
Adds support to Microsoft Edge and Industry 11 relating to the SameSite cookie web standard. For more details about SameSite cookies, see our recently published post.
The build would not contain any known issues.
Typically, we’d recommend heading to Windows Update and checking for updates to provide a oceanfront cumulative update that’s designated for your special version of Windows 10. Unfortunately, Microsoft has decided that anyone who hits the Verify updates button wants Windows 10 version 1803 currently, whether your machine ready for it or. So if you want this update now, you must either handle the installation manually, or wait for Windows Update to have automatically.