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:
- Updates wininet.dll to prevent the re-creation of File Transfer Protocol (FTP) control sessions.
- Addresses an issue that prevents the OS from loading new icon files if it encounters an icon file that has a bad format.
- Addresses an issue to set the date separator properly in the Japanese short date format. For more information, see KB4469068.
- Updates time zone information for Morocco.
- Updates time zone information for the Palestinian Authority.
- Improves performance related to case-insensitive string comparison functions such as _stricmp() in the Universal C Runtime.
- Addresses an issue that may cause a temporary KRB_AP_ERR_MODIFIED Kerberos sign-in failure in applications and services configured to use a Group Managed Service Account (GMSA). This issue occurs after the automatic update of the service account password.
- Addresses an issue that causes a sign-in to fail with the error, “Incorrect Username or password” when using an empty or null password and Windows Defender Credential Guard is enabled.
- Addresses an issue that causes Microsoft Office and other applications to prompt for a password after you change a user account password. This issue occurs on hybrid Azure Active Directory (AD) joined systems.
- Addresses an issue with BranchCache when it is in distributed cache mode. BranchCache may use more disk space than assigned for the republication cache. To fully address the issue, devices that have exceeded the disk space assignments should empty BranchCache using the netsh branchcache flush command.
- Addresses an issue that may cause a Stop D1 error when you increase the virtual processor count (“hot add”) on a running virtual machine.
- Addresses an issue that may cause event 7600 in the Domain Name System (DNS) server event log to contain an unreadable server name.
- Addresses an issue with apps that have incorrect audits and are not protected by Extranet Smart lockout when they are published using the Active Directory Federation Services (ADFS) RichClient.
- Addresses an issue that fails to record a local user’s last logon time even when the user has accessed the server’s network share.
- Addresses an issue that may cause error “0x7E” when moving a Network File System (NFS) File Server role and any client is active.
- Addresses an issue with the Windows Management Instrumentation (WMI) class, Win32_PhysicalMemory, which reports 32 GB of memory without a Capacity value.
- Addresses an issue with scrollLeft in Internet Explorer.
- Addresses an issue that causes rendering to stop working for <svg> elements.
Addresses an issue that causes a delay when loading many unsigned Domain Name System (DNS) zones related to the Domain Name System Security Extensions (DNSSEC) feature. This issue occurs after configuring the following registry setting:
Value: A value of 1 enables the feature. A value of 0 disables the feature.
Restart the operating system or the DNS server after changing the registry values.
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:
After installing this update and restarting, some devices running Windows Server 2016 with Hyper-V enabled may enter Bitlocker recovery mode and receive an error, "0xC0210000".Note Windows 10, version 1607 may also be affected when Bitlocker and Hyper-V are enabled.
For a workaround for this issue, please see KB4505821.
Microsoft is working on a resolution and will provide an update in an upcoming release.
|This update may not show as applicable through WSUS or SCCM to Windows 10, version 1607 or Windows Server 2016. Also, when manually installing the standalone update from Microsoft Update Catalog, it may fail to install with the error, "The update is not applicable to your computer."||The servicing stack update (SSU) (KB4498947) must be installed before installing the latest cumulative update (LCU). The LCU will not be reported as applicable until the SSU is installed. For more information, see Servicing stack updates.|
|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.
|Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.|| |
To set the Default Search Provider, use the following steps:
We are working on a resolution and estimate a solution will be available in mid-June.
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 4499177.