KB4499177 Windows 10 1607 14393.2999 Cumulative update - 23 May 2019

Here comes an off-beat update - KB4499177 for Windows 10 version 1607. With this patch, the operating system build gets to 14393.2999. Most importantly, the cumulative update addresses several of the issues that were detected in the previous push.

You will obtain the patch KB4499177 automatically via Windows update. Moreover, you can manually download the same from the Microsoft Update Catalogue as standalone package in MSU file format and manually install.

Windows 10 Cumulative Updates List

KB4499177 for Windows 10 version 1607 14393.2999 Improvements and updates with KB449917

• KB449917 improves wininet.dll for preventing the re-creation of FTP control sessions.
• It contains an update for Morocco time zone information for Morocco and the Palestinian Authority.
• The update improvises the performance associated with case-insensitive string comparison functions like _stricmp() in the Universal C Runtime.
• It also improvises Japanese short date format to set the date separator properly

Fixes coming with KB449917

• Address an issue causing a temporary KRB_AP_ERR_MODIFIED Kerberos sign-in failure. The problem occurs after an automatic update of service account password in services and apps configured for using a Group Managed Service Account (GMSA).
• The update resolves a problem which results in a sign-in failure when the password in empty or null with Windows Defender Credential Guard enabled. You may also see the error, “Incorrect Username or password”.
• KB449917 fixes an issue that causes MS Office and other apps to prompt for a password once the user changes an account password. The problem was seen occurring on hybrid Azure Active Directory (AD) joined systems.
• The update resolves the issue of BranchCache using up more-than-assigned disk space while in distributed cache mode. Users musts empty BranchCache using the netsh branchcache flush command in case of devices exceeding the disk space assignments.
• Fixes a problem causing a Stop D1 error as the user increases the RAM capacity of a CPU (“hot add”) on a virtual machine.
• There is also a fix for unreadable server name in the Domain Name System (DNS) server event log (event 7600).
• KB449917 resolves the problem preventing the system to record a local user’s last login time despite that the user has accessed the server’s network share.
• It further fixes a problem causing error “0x7E” if any client is active when moving a Network File System (NFS) File Server role.
• Addresses an issue with the Windows Management Instrumentation (WMI) class, Win32_PhysicalMemory, which reports 32 GB of memory without a Capacity value.
• There is a fix for scrollLeft related issue in IE.
• KB449917 fixes a problem that intrudes with working for <svg> elements.
• Lastly, it also resolves the issue preventing the OS from loading new icon files while encountering the ones with has a bad format.

Known issues with KB4499177

Listed below are the known issues with this update.

Issue 1:

There can be a problem in hosts which are managed by SCVMM or System Center Virtual Machine Manager (SCVMM). In this case, SCVMM is unable to enumerate/manage the logical switches deployed on the host. Also, there is a possibility of occurrence of stop error in vfpext.sys.
Workaround:
Run mofcomp on the following mof files:

• mof
• mof

Microsoft recommends users to follow the best practices when patching in order to prevent the stop error in vfpext.sys.

Issue 2:

Another known issue known is that post installation, the cluster service may not start. An error message “2245 (NERR_PasswordTooShort)” will be shown. This occurs particularly if the users set group policy “Minimum Password Length” over 14 characters.

Workaround:

As a workaround, you can set the "Minimum Password Length", which might be, by default, over 14 chars, to less than or equal to 14 chars.
The developer is currently working on finding a permanent solution for this issue. We can expect an update in relation to this in an upcoming release.

Issue 3:

Users are facing some troubles as they try to start a device using the Preboot Execution Environment (PXE). Usually, the problem appears when users start it from a WDS or Windows Deployment Services server configured to use Variable Window Extension. It may result in prematurely terminating the connection to the WDS server while downloading the image. This problem, however, does not affect clients or devices which do not use VWE or Variable Window Extension. Microsoft is attempting to resolve this issue

Workaround:

Try and see if any of the below workarounds disable the Variable Window Extension on WDS server and mitigate the issue.
Alternative 1:

1.  In the search box, type cmd. Then, open Command prompt as an administrator.
2. In the command line, enter the following:

Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No

Alternative 2:
Another way around this problem involves the use of Windows Deployment Services User interface.

1. From the Windows Administrative tools, open Windows Deployment Services.
2. Then, expand the Servers options and right-click on a WDS server.
3. Open properties. Then, on the TFTP tab, you need to clear the Enable Variable Window Extension box.

Alternative 3:

1. In the search box, type regedit. Then, click on the result to open the registry editor.
2. Go to the following location and set the registry value to 0:

“HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”.
After you disable, Microsoft suggests restarting the WDSServer service.
Microsoft team is working to figure a permanent solution. A future update should be having the resolution.

Issue 4:

There still are the recently detected issues with folders or files which are on a CSV (Cluster Shared Volume). Renaming or such operations performed on those files and folders often fail. They are mostly accompanied by an error message, ‘STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)’.

Workaround:

This problem is faced by users who try operating in a CSV-owner node from a process which is not having the administrator privilege. So, as a workaround, for now, try performing the operation from:

• A process that has administrator privilege.
• A node that does not have a CSV ownership.

Microsoft is working on a permanent resolution and will provide an update in an upcoming release.

Issue 5:

In some cases, the systems that are running Windows Server 2016 with Hyper-V enabled goes into Bitlocker recovery mode after installation of KB4499177. Also, an error- "0xC0210000”- might appear.
The developer is yet to offer a permanent solution for this issue.

Issue 6:

You may be unable to install KB449917 to Windows 10 version 1607, Further, you may get the error "The update is not applicable to your computer” when trying to do so.  The update may not be applicable even via Windows Update services or SCCM.

Workaround:

The cumulative update might not be reported until you install the SSU or servicing stack update (KB4498947). Install the SSU before you install KB449917.

Microsoft update catalog

Release note