Windows 10, version 1607, reached end of service on April 10, 2018. Devices running Windows 10 Home or Pro editions will no longer receive monthly security and quality updates that contain protection from the latest security threats. To continue receiving security and quality updates, Microsoft recommends updating to the latest version of Windows 10.
IMPORTANT: Windows 10 Enterprise and Windows 10 Education editions will receive six months of additional servicing at no cost. Devices on the Long-Term Servicing Channels (LTSC) will continue to receive updates until October 2026 per the Lifecycle Policy page. Windows 10 Anniversary Update (v. 1607) devices running the Intel “Clovertrail” chipset will continue to receive updates until January 2023 per the Microsoft Community blog.
Windows 10 Mobile, version 1607, reached end of service on October 8, 2018. Devices running Windows 10 Mobile and Windows 10 Mobile Enterprise will no longer receive monthly security and quality updates that contain protection from the latest security threats. To continue receiving security and quality updates, Microsoft recommends updating to the latest version of Windows 10.
Improvements and fixes
This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:
- Addresses the redenomination of local currency that the Central Bank of Venezuela implemented to enter the Bolivar Soberano into circulation.
- Addresses additional issues with updated time zone information.
- Addresses an issue in which no error message appears when a blocked app is invoked from the Start menu.
- Addresses an issue in which the AccountName in the Event Log entry for the Microsoft-Windows-Kerberos-Key-Distribution-Center source and Event ID 7 sometimes appears corrupted.
- Addresses an issue with cloud authentication performance for accounts that create logon sessions very quickly.
- Addresses an issue that makes it impossible to disable TLS 1.0 and TLS 1.1 when the Federal Information Processing Standard (FIPS) mode is enabled.
- Addresses an issue that maps two or more certificates for authentication to the same user. The user receives the message, “Duplicates found” and receives the error, “STATUS_CERTIFICATE_MAPPING_NOT_UNIQUE”.
- Addresses an issue in which applications have handle leaks when using client authentication certificates with the TLS protocol. This issue occurs when the FreeCredentialsHandle call occurs before the DeleteSecurityContext call in application code.
- Addresses memory leak issues on svchost.exe (netsvcs and IP Helper Service).
- Addresses an issue that depletes the storage space on a cluster-shared volume (CSV) because of a Hyper-V virtual hard disk (VHDX) expansion. As a result, a Virtual Machine (VM) might continue writing data to its disk until it becomes corrupted or stops working. The VM might also restart and then resume writing data until a corruption occurs.
- Addresses an issue that causes the promotion of a read-only domain controller (RODC) to fail. This might occur if application partitions are defined, but the DNS name resolution failed with the “Name error”. The errors are “While promoting Read-only Domain Controller, the expected state objects could not be found” and “More data is available” (error code 234).
- Addresses interoperation issues between Active Directory Federation Services (ADFS) Extranet Smart Lockout (ESL) and Alternate Login ID. When Alternate Login ID is enabled, calls to AD FS Powershell cmdlets, Get-AdfsAccountActivity and Reset-AdfsAccountLockout, return "Account not found" errors. When Set-AdfsAccountActivity is called, a new entry is added instead of editing an existing one.
- Addresses an issue with navigation from the Decade view in the Japanese calendar. When the user tries to go from the current era to the next era, navigation does not work properly. For more information, see KB4469068.
- Addresses an issue that causes the Remote Desktop Services Gateway to stop working effectively in a load balanced scenario after 12 to 24 hours of uptime.
Addresses an issue that occurs when using multiple Windows Server 2016 Hyper-V clusters. The following event appears in the log:
“Cluster Shared Volume 'CSVName' ('CSVName') has entered a paused state because of 'STATUS_USER_SESSION_DELETED(c0000203)'. All I/O will temporarily be queued until a path to the volume is reestablished.”
Addresses an issue that may cause the creation of a single node cluster or the addition of more nodes to a cluster to fail intermittently.
Addresses an issue that occurs when restarting a node after draining the node. Event ID 5120 appears in the log with a “STATUS_IO_TIMEOUT c00000b5” message. This may slow or stop input and output (I/O) to the VMs, and sometimes the nodes may drop out of cluster membership.
Addresses an issue in which the System.Security.Cryptography.Algorithms reference was not correctly loaded on .NET Framework 4.7.1 after the July 10, 2018 and August 14, 2018 patches.
- Addresses an issue that may cause the system to stop working during the shutdown of some Windows Presentation Foundation (WPF) apps because of TaskCanceledException. Apps that are vulnerable to this issue perform work involving weak events or data binding after the Application.Run() function returns values.
- Addresses a race condition in temporary files and some antivirus scanners that causes .NET Framework applications to stop working. The error message is, "The process cannot access the file <name of temp file>".
- Updates the .NET Framework's support for the formatting of Japanese dates for the first year in the eras. When the format pattern is “y年”, the year format will use the symbol 元 and not use year number 1. Additionally, the .NET Framework will support dates that include 元. For more information, see KB4469068.
- Updates Venezuela currency information. This will affect the culture of “es-VE” as follows:
- The currency symbol is “Bs.S”.
- The English currency name is “Bolívar Soberano”.
- The local currency name is “bolívar soberano”.
- The International Currency Code is “VES”.
- Addresses an issue that may cause the addition of nodes to fail intermittently after creating a single node in a Windows Server 2016 Cluster. The error code is, “0x0000001e”.
Addresses an issue that may cause an application that has a child window to stop processing mouse inputs. This issue occurs when a precision touchpad triggers a WM_MOUSEWHEEL event.
Addresses an issue that causes navigation across eras to stop working in the Japanese Calendar view.
Addresses an issue related to the date format for the Japanese era calendar.
Addresses an issue that causes the GetCalendarInfo function to return a wrong value for the Japanese era.
If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.
Windows Update Improvements
Microsoft has released an update directly to the Windows Update client to improve reliability. Any device running Windows 10 configured to receive updates automatically from Windows Update, including Enterprise and Pro editions, will be offered the latest Windows 10 feature update based on device compatibility and Windows Update for Business deferral policy. This doesn't apply to long-term servicing editions.
Known issues in this update
|After installing this update, installation and client activation of Windows Server 2019 and 1809 LTSC Key Management Service (KMS) (CSVLK) host keys do not work as expected.||This issue is resolved in KB4467684.|
|After installing this update, Windows Server 2016 promotions that create non-root domains fail in forests in which optional features like Active Directory recycle have been enabled. The error is, “The replication operation encountered a database error”.|| |
This issue is resolved in KB4467684.
After you install the August Preview of Quality Rollup or September 11, 2018 .NET Framework update, instantiation of SqlConnection can throw an exception. For more information about this issue, see the following article in the Microsoft Knowledge Base:
4470809 SqlConnection instantiation exception on .NET 4.6 and later after August-September 2018 .NET Framework updates
|Microsoft is working on a resolution and will provide an update in an upcoming release.|
|After installing this update, users may not be able to use the Seek Bar in Windows Media Player when playing specific files. This issue does not affect normal playback.||This issue is resolved in KB4471321.|
How to get this update
Before installing this update
Windows cumulative updates require that you install the latest servicing stack update (SSU) for your operating system before installing the latest cumulative update (LCU). This helps to mitigate potential issues while installing the LCU. For more information, see Servicing stack updates.
Install this update
To download and install this update, go to Settings > Update & Security > Windows Update and select Check for updates.
To get the stand-alone package for this update, go to the Microsoft Update Catalog website.
For a list of the files that are provided in this update, download the file information for cumulative update 4462928.