Microsoft has pushed Windows 10 PC Build 10.0.14393.2034 (KB4057142) to those on Anniversary update (Windows 10 Version 1607).
You can check the update availability by going to Settings–>Update & Security–>Windows update–>Check for updates. Coming to what is there in changes/fixes/improvements, there are expectedly no significant changes. But there are lots of fixes and improvements.
You can check the full changelog of Windows 10 PC Build 14393.2034 (KB4057142) below.
Windows 10 Build 14393.2034 (KB4057142) Changelog:
Improvements and fixes
This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:
- Addresses issue where some Microsoft-signed ActiveX controls don’t work when the Windows Defender Application Control (Device Guard) is enabled. Specifically, class IDs related to XML HTTP in msxml6.dll don’t work.
- Addresses issue where using smart cards on a Windows Terminal Server system may cause excessive memory use.
- Addresses issue where the virtual TPM self-test isn’t run as part of virtual TPM initialization.
- Improves compatibility with U.2 NVMe devices, specifically in hot-add/removal cases.
- Addresses issue where the iSCSI Initiator Properties Devices list doesn’t display certain targets.
- Adds compatibility for NGUID and EUI64 ID formats for NVMe devices.
- Addresses synchronization issue where backing up large Resilient File System (ReFS) volumes may lead to errors 0xc2 and 7E.
- Addresses issue where the UWF file commit adds old data to files in certain scenarios.
- Addresses issue where access-based enumeration may not work as expected in some scenarios after you install KB4015217 or later. For example, a user may be able to view another user’s folder to which they don’t have access rights.
- Addresses issue where AD FS incorrectly displays the Home Realm Discovery (HRD) page when an identity provider (IDP) is associated with a relying party (RP) in an OAuth Group. Unless multiple IDPs are associated with the RP in the OAuth Group, the user isn’t shown the HRD page. Instead, the user is navigated directly to an associated IDP for authentication.
- Addresses issue where PKeyAuth-based device authentication sometimes fails in Internet Explorer and Microsoft Edge when AD FS returns a context that exceeds the request limits for URL length. Event 364 is logged in the AD FS 2.0 Admin log with the following exception details: “System.Security.Cryptography.CryptographicException: The signature is not valid. The data may have been tampered with….”
- Addresses issue in AD FS where MSISConext cookies in request headers can eventually overflow the headers’ size limit. This causes authentication failure with the HTTP status code 400: “Bad Request – Header Too Long.”
- Addresses issue where AD FS produces an MFA Event 1200 log that doesn’t contain UserID information.
- Addresses issue where retrieving the Certificate Revocation List (CRL) from the Certification Authority (CA) using the Simple Certificate Enrollment Protocol (SCEP) fails. Users see event ID 45, which says, “NDES cannot match issuer and serial number in the device request with any Certification Authority (CA) Certificate”.
- Enables IT administrators to scientifically troubleshoot I/O failures using a comprehensive event log for the resiliency state transition.
- Provides transparency about replication health. It represents the state of replication by indicating when:
- The free disk space is running low.
- The Hyper-V Replica Log (HRL) size is growing to its maximum limit.
- The Recovery Point Objectives (RPO) threshold has been violated.
- Addresses issue where, if the Online Certificate Status Protocol (OCSP) renewal date comes after the certificate expiration date, the OCSP-stapled response is used until the renewal date even though the certificate has expired.
- Addresses issue where backwards compatibility for managing Microsoft User Experience Virtualization (UE-V) with group policy is lost. Windows 10 version 1607 group policy isn’t compatible with Windows 10 version 1703 or higher group policy. Because of this bug, the new Windows 10 Administrative Templates (.admx) cannot be deployed to the Group Policy Central Store. This means that some of the new, additional settings for Windows 10 aren’t available.
- Addresses issue with the App-V package folder access that causes the access control list to be handled incorrectly.
- Addresses issue that causes a delay when searching for new printers to add.
- Addresses issue where users may not be able to change passwords on the remote logon screen if the password has expired.
- Addresses issue where custom application defaults are sometimes not imported when using the DISM command.
- Addresses issue originally called out in KB4056890 where calling CoInitializeSecurity with the authentication parameter set to RPC_C_AUTHN_LEVEL_NONE resulted in the error STATUS_BAD_IMPERSONATION_LEVEL.
- Addresses issue where some customers with AMD devices get into an unbootable state.
Known issues in this update
|Due to an issue with some versions of antivirus software, this fix only applies to the machines where the antivirus ISV has updated the ALLOW REGKEY.||Contact your Anti-Virus AV to confirm that their software is compatible and have set the following REGKEY on the machine
|After installing this update, servers where Credential Guard is enabled may experience an unexpected restart with the error, “The system process lsass.exe terminated unexpectedly with status code -1073740791. The system will now shut down and restart.”
Event ID 1000 in the application log shows:
“C:\windows\system32\lsass.exe’ terminated unexpectedly with status code -1073740791
Faulting application: lsass.exe, Version: 10.0.14393.1770, Time Stamp: 0x59bf2fb2
Faulting module: ntdll.dll, Version: 10.0.14393.1715, Time Stamp: 0x59b0d03e
|Disable Credential Guard; see Disable Windows Defender Credential Guard.
Microsoft is working on a resolution and will provide an update in an upcoming