Microsoft releases new cumulative update for Windows 10 Anniversary and Creators Update PCs

Microsoft today released OS Build 14393.2155 and OS Build 15063.994 to Windows 10 Anniversary Update (Windows 10 Version 1607) and Windows 10 Creators Update (Windows 10 Version 1703) users respectively. These cumulative updates does not include any new features, but they include several bug fixes. Find the full change log below.

March 22, 2018—KB4088891 (OS Build 15063.994):

• Addresses issue with a GDI handle leak in the Windows Ribbon control.
• Addresses issue where, during BitLocker decryption or encryption of a drive, files protected with the Encrypting File System (EFS) may become corrupted.
• Addresses issue where, when an iSCSI request contains an incomplete header in the first packet, iSCSI may not recognize when a request has been sent.
• Adds support in stornvme for additional SSDs.
• Addresses issue where the Japanese keyboard layout was not functioning properly during a Remote Assistance session.
• Addresses rendering issue in Microsoft Edge for PDF documents with backgrounds created using various third-party publishing tools.

March 22, 2018—KB4088889 (OS Build 14393.2155):

• Addresses issue with a GDI handle leak in the Windows Ribbon control.
• Addresses issue where customers can’t change the lock screen image from the Settings app. This occurs if the “Force a specific default lock screen and logon image” Group Policy is turned on and the “Prevent changing lock screen and logon image” Group Policy is turned off.
• Addresses issue where, during BitLocker decryption or encryption of a drive, files protected with the Encrypting File System (EFS) may become corrupted.
• Adds support for additional high-speed eMMC devices.
• Adds support in stornvme for additional SSDs.
• Addresses issue where UWF file exclusion failed when non-ASCII characters were used in the directory name.
• Addresses issue where ID:55 and ID:130 might be logged when using UWF in DISK mode, which eventually requires a restart.
• Addresses issue where the VSS API ResyncLun failed to find the hardware provider.
• Addresses issue where Hyper-V replication suspends when the primary server restarts and Azure Site Recovery (ASR) is used to replicate Hyper-V virtual machines.
• Addresses issue where an error might occur when the memory manager finds an undeleted page table space when a process terminates.
• Addresses issue where Windows Server 2016 Domain Controllers (DC) may periodically restart after a Local Security Authority Subsystem Service (LSASS) module faults with exception code 0xc0000005. This interrupts applications and services bound to the DC at that time. DCs may log the following events:
  • Application Error event ID 1000; the faulty module is NTDSATQ.dll with exception code 0xc0000005.
  • User32 event ID 1074 and Microsoft-Windows-Wininit event ID 1015, which indicates that lsass.exe failed with status code 255.
• Addresses issue where the AdminSDHolder task fails to run when a protected group contains a member attribute that points to a deleted object. Additionally, Event 1126 is logged with “Active Directory Domain Services was unable to establish a connection with the global catalog. Error value: 8430. The directory service encountered an internal failure. Internal ID: 320130e.”
• Addresses issue where users may exist in a trusted domain with transitive trust (a child domain across Forest trust or AD FS in a child domain and the user is across Forest trust). However, users cannot locate a PDC or DC for the Extranet Lockout Feature. The following exception occurs: “Microsoft.IdentityServer.Service.AccountPolicy.ADAccountLookupException: MSIS6080: A bind attempt to domain ‘globalivewireless.local’ failed with error code ‘1722’.” A message appears on the IDP page, “Incorrect user ID or password. Type the correct user ID and password, and try again.”
• Addresses issue where, when Claims Provider Trust is set with OrganizationalAccountSuffix (even after performing HRD), AD FS doesn’t save the HRD information. The user will always see the HRD page for any new request. This breaks the SSO request for users because they need to type a username or email and password for each request.
• Improves the performance of AD FS MFA authentication response time by improving the utilization of Strong Authentication Service (SAS) calls.
• Addresses issue caused by a new privilege in Windows Server 2016 and Windows 10 version 1607 named “Obtain an impersonation token for another user in the same session”. When applied using Group Policy to those computers, gpresult /h fails to generate reporting data for any setting configured by the Security Configuration Engine (SCE) extension. The error message is “Requested value ‘SeDelegateSessionUserImpersonatePrivilege’ was not found”. The Group Policy Management Console fails to show the privilege in the Settings tab for a GPO where the setting has been configured.
• Addresses issue where WMI stops responding to queries and WMI-dependent operations fail after exceeding the 256 MB WMI Arbitrator memory limit. Computers that experience high WMI memory usage or that return error WBEM_E_INVALID_CLASS or WBEM_E_NOT_FOUND should install this update.
• Addresses a threading issue that might cause the WinRM service to stop working when under load. This is a client-side solution, so it should be applied to affected computers as well as computers that communicate with it using WinRM.
• Addresses issue with system performance that causes logons to become unresponsive with the message “Please wait for the Remote Desktop Configuration” because of a deadlock in the WinRM service.
• Addresses issue where the Remote Desktop License report gets corrupted when it exceeds the 4 KB size limit.
• Addresses a race condition in RemoteApp that occurs when an activated RemoteApp window opens behind the previous foreground window.
• Addresses rendering issue in Microsoft Edge for PDF documents with backgrounds created using various third-party publishing tools.
• Addresses issue caused by a race condition where Windows Server 2016 may restart after win32kbase.sys faults with error code 0x18.

Source: Microsoft (1), (2)