Reminder: The additional servicing for Windows 10 Enterprise, Education, and IoT Enterprise editions ends on April 9, 2019 and doesn't extend beyond this date. To continue receiving security and quality updates, Microsoft recommends updating to the latest version of Windows 10.
Reminder: March 12th and April 9th will be the last two Delta updates for Windows 10, version 1607. For Long-Term Servicing Branch (LTSB) customers, security and quality updates will continue to be available via the express and full cumulative update packages. For more information on this change please visit our blog.
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 additional servicing at no cost until April 9, 2019. 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 Server 2016 Standard edition, Nano Server installation option and Windows Server 2016 Datacenter edition, Nano Server installation option reached end of service on October 9, 2018. These 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.
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. Key changes include:
- Addresses an issue that causes Internet Explorer to block a sub-resource download when its loaded over the HTTP protocol on a page hosted over the HTTPS protocol.
- Addresses an issue that may prevent Custom URI Schemes for Application Protocol handlers from starting the corresponding application for local intranet and trusted sites on Internet Explorer.
- Addresses an issue that prevents the CALDATETIME structure from handling more than four Japanese Eras. For more information, see KB4469068.
- Addresses an issue that causes ShellExperienceHost.exe to stop working when the start date for the Japanese Era is not on the first day of the month. For more information, see KB4469068.
- Updates the NLS registry to support the new Japanese Era. For more information, see KB4469068.
- Addresses an issue that causes the DateTimePicker to display the date incorrectly in the Japanese date format. For more information, see KB4469068.
- Addresses an issue that causes the Date and Time Settings control to cache old Eras and prevents the control from refreshing when the time enters the new Japanese Era. For more information, see KB4469068.
- Updates fonts to support the new Japanese Era. For more information, see KB4469068.
- Addresses an issue that prevents an input method editor (IME) from supporting the new Japanese Era character. For more information, see KB4469068.
- Addresses an issue that causes the Clock and Calendar flyout control to display the day of the week incorrectly mapped to a date in the month of the new Japanese Era. For more information, see KB4469068.
- Adds alternative fonts for the new Japanese Era fonts. For more information, see KB4469068.
- Enables Text-To-Speech (TTS) functionality to support new Japanese Era characters. For more information, see KB4469068.
- Addresses an issue in Gdi32full.dll that causes an application to stop responding.
- Addresses a gradual memory leak in LSASS.exe on systems that have cached logon enabled. This issue mainly affects servers that process many interactive logon requests, such as web servers.
- Addresses an issue that causes Lightweight Directory Access Protocol (LDAP) client applications to stop responding for at least 30 seconds when many LDAP queries are requested through multiple connections. This occurs because of a race condition in wldap32.dll. You must install this update on the LDAP client that calls wldap32.dll.
- Addresses an issue that may prevent Cluster Aware Update from restarting nodes when a cluster's credentials are reset. Cluster Aware Update must restart nodes after installing an update. The error is the following:
”Failed to restart "NODENAME": (ClusterUpdateException) Failed to restart "NODENAME": (Win32Exception) The user name or password is incorrect.”
- Addresses an issue that may cause Microsoft Cluster Shared Volumes File Systems (CSVFS) to stop working under certain conditions.
- Addresses an issue with setting up a Storage Replica in a Scale-Out File Server with a Storage Spaces Direct cluster. Using Test-SRTopology to query multiple volumes when the Primary DNS suffix is different than the domain name may cause the query to fail with a null reference exception in GetPartitionInStorageNodeByAccessPath.
- Addresses an issue that may cause error 0x7E to occur when adding a node to an Exchange Database Availability Group server.
- Addresses an issue that causes slow screen refresh rates when an application creates and destroys many child windows.
- Addresses an issue that causes connection requests to the Remote Desktop Session Host (RDSH) servers in the deployment to fail. This issue occurs because of a deadlock in the Connection Broker.
- Addresses an issue that occasionally causes a PostScript printer to use the wrong font.
- Addresses an issue that fails to enumerate devices that have 64-bit base address registers and are assigned to virtual machines. This issue also prevents Windows from detecting these devices. This issue occurs on hosts that have the Hyper-V role enabled.
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
For hosts managed by System Center Virtual Machine Manager (SCVMM), SCVMM cannot enumerate and manage logical switches deployed on the host after installing the update.Additionally, if you do not follow the best practices, a stop error may occur in vfpext.sys on the hosts.
|After installing KB4467684, the cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the group policy “Minimum Password Length” is configured with greater than 14 characters.|| |
Set the domain default "Minimum Password Length" policy to less than or equal to 14 characters.
Microsoft is working on a resolution and will provide an update in an upcoming release.
|After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.|| |
This issue is resolved in KB4503267.
|Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.|| |
Do one of the following:
|Zone transfers between primary and secondary DNS servers over the Transmission Control Protocol (TCP) protocol may fail after installing this update.||This issue is resolved in KB4494440.|
When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic.
This issue is resolved in KB4494440.
|Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of this update on the server. Applications that may exhibit this behavior use an IFRAME during non-interactive authentication requests and receive X-Frame Options set to DENY.|| |
You can use the Allow-From value of the header if the IFRAME is only accessing pages from a single-origin URL. On the affected server, open a PowerShell window as an administrator and run the following command: set-AdfsResponseHeaders -SetHeaderName X-Frame-Options -SetHeaderValue "allow-from https://example.com"Microsoft is working on a resolution and will provide an update in an upcoming release.
How to get this update
Before installing this update
Microsoft strongly recommends you install the latest servicing stack update (SSU) for your operating system before installing the latest cumulative update (LCU). SSUs improve the reliability of the update process 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 standalone 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 4493473.
Thank you for visiting the Windows 10, version 1607 update history page today. If you would like to learn more about how to use these pages and make the most of them, see our blog post.
To improve the information presented in the history pages and related KBs and make them more useful to our customers, we have created an anonymous survey for you to share your comments and feedback.