Windows 10: Cumulative Update KB4499177 Windows 10 v1607 Build 14393.2999 - May 23

Brink · May 23, 2019

May 23, 2019 - KB4499177 (OS Build 14393.2999)

Applies to: Windows 10 version 1607, Windows Server 2016

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 random-access memory (RAM) capacity of a CPU (“hot add”) on a 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.

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

Symptom Workaround 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.

Run mofcomp on the following mof files on the affected host:

Scvmmswitchportsettings.mof

VMMDHCPSvr.mof

Follow the best practices while patching to avoid a stop error in vfpext.sys in an SDN v2 environment (NC managed 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. To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options:

Option 1:
Open an Administrator Command prompt and type the following:

Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No

Option 2:
Use the Windows Deployment Services UI.

Open Windows Deployment Services from Windows Administrative Tools.

Expand Servers and right-click a WDS server.

Open its properties and clear the Enable Variable Window Extension box on the TFTP tab.

Option 3:
Set the following registry value to 0:

“HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”.

Restart the WDSServer service after disabling the Variable Window Extension.

Microsoft is working on a resolution and will provide an update in an upcoming release. 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:

Perform the operation from a process that has administrator privilege.

Perform the operation from a node that doesn’t have CSV ownership.

Microsoft is working on a resolution and will provide an update in an upcoming release. 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.
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.

If you are using Windows Update, the latest SSU (KB4498947) will be offered to you automatically. To get the standalone package for the latest SSU, search for it in the Microsoft Update Catalog.

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.
Click to expand...

Source: https://support.microsoft.com/en-us/help/4499177

Direct download links for KB4499177 from Microsoft Update Catalog:

*Arrow Download KB4499177 MSU for Windows 10 Version 1607 32-bit (x86) - 788.0 MB

*Arrow Download KB4499177 MSU for Windows 10 Version 1607 64-bit (x64) - 1412.8 MB

Tip Find Windows 10 Version Number

Find Windows 10 Build Number

:)

Brink · May 23, 2019

Cumulative Update KB4023680 Windows 10 v1607 Build 14393.1230

Installing now.

Brink · May 23, 2019

Cumulative Update KB4038782 Windows 10 v1607 Build 14393.1715

Update: Cumulative Update KB4038801 Windows 10 v1607 Build 14393.1737 - Windows 10 Forums

Edwin · May 23, 2019

Cumulative Update KB4019472 Windows 10 v1607 Build 14393.1198

I think I'm all up to date now!
PC, Tablet, Insider PC respectively.

Windows 10: Cumulative Update KB4499177 Windows 10 v1607 Build 14393.2999 - May 23

Cumulative Update KB4499177 Windows 10 v1607 Build 14393.2999 - May 23

Cumulative Update KB4499177 Windows 10 v1607 Build 14393.2999 - May 23

Cumulative Update KB4499177 Windows 10 v1607 Build 14393.2999 - May 23

Cumulative Update KB4499177 Windows 10 v1607 Build 14393.2999 - May 23 - Similar Threads - Cumulative Update KB4499177

Cumulative Update KB4522010 Windows 10 v1607 Build 14393.3206 Sept. 23 Win Update

Cumulative Update KB4505052 Windows 10 v1607 Build 14393.2972 - May 19

Cumulative Update KB4494440 Windows 10 v1607 Build 14393.2969 - May 14

Cumulative Update KB4100403 Windows 10 v1803 Build 17134.81 - May 23

Cumulative Update KB4103720 Windows 10 v1607 Build 14393.2273 - May 17

Cumulative Update KB4103723 Windows 10 v1607 Build 14393.2248 - May 8

Cumulative Update KB4038220 Windows 10 v1607 Build 14393.1537

Cumulative Update KB4016635 for Windows 10 v1607 Build 14393.970

Cumulative Update KB4025334 Windows 10 v1607 Build 14393.1532

Users found this page by searching for:

build 14393.2999

2019 Cumulative Update for Windows 10 v1607 Build 14393.2273

windows 10 build 10.0.14393