Windows 10: Cumulative Update KB4057142 Windows 10 v1607 Build 14393.2034


  1. Posts : 29,330
    64-bit Windows 10 Pro build 17672
       17 Jan 2018 #1

    Cumulative Update KB4057142 Windows 10 v1607 Build 14393.2034


    January 17, 2018 - KB4057142 (OS Build 14393.2034)

    Applies to: Windows Server 2016Windows 10 Version 1607


    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.

    If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.

    For more information about the resolved security vulnerabilities, see the Security Update Guide.

    Windows Update Client Improvement
    Microsoft will release an update directly to the Windows Update Client to improve Windows Update reliability. It will only be offered to devices that have't installed the most recent updates.


    Known issues in this update

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

    Key="HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat"

    Value Name="cadca5fe-87d3-4b96-b7fb-a231484277cc"

    Type="REG_DWORD”

    Data="0x00000000”
    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
    Exception: 0xc0000409
    Disable Credential Guard; see Disable Windows Defender Credential Guard.
    Microsoft is working on a resolution and will provide an update in an upcoming release.

    How to get this update

    To get the standalone package for this update, go to the Microsoft Update Catalog website.

    File information

    For a list of the files that are provided in this update, download the file information for cumulative update 4057142.


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





    Direct download links for KB4057142 from Microsoft Update Catalog:

    Download KB4057142 MSU for Windows 10 Version 1607 32-bit (x86) - 632.2 MB

    Download KB4057142 MSU for Windows 10 Version 1607 64-bit (x64) - 1205.5 MB
    Last edited by Brink; 17 Jan 2018 at 17:03.
      My ComputersSystem Spec


  2. Posts : 130
    Windows 10 Home 64bit V1709
       18 Jan 2018 #1

    I'm on a prior v1607 build on my older AMD notebook. Should I skip this and just download the latest KB4073290 v1709 from catalog?
      My ComputerSystem Spec


  3. Posts : 29,330
    64-bit Windows 10 Pro build 17672
    Thread Starter
       18 Jan 2018 #2

    Hello galaxys, :)

    The v1709 KB4073290 update wouldn't apply to your v1607 installation.

    KB4057142 is the latest update for v1607.
      My ComputersSystem Spec


  4. Posts : 130
    Windows 10 Home 64bit V1709
       18 Jan 2018 #3

    Thanks Brink, will do 1607 then. Cheers
      My ComputerSystem Spec


  5. Posts : 29,330
    64-bit Windows 10 Pro build 17672
    Thread Starter
       18 Jan 2018 #4



    If you wanted, you could use the Windows 10 Update Assistant to update to the latest version 1709.

    Update to Latest Version of Windows 10 using Update Assistant Installation Upgrade Tutorials
      My ComputersSystem Spec


 

Related Threads
Source: https://support.microsoft.com/en-us/help/4056890 Find Windows 10 Version Number Find Windows 10 Build Number Direct download links for KB4056890 from Microsoft Update Catalog:
Source: https://support.microsoft.com/en-us/help/4051033 Find Windows 10 Version Number Find Windows 10 Build Number Direct download links for KB4051033 from Microsoft Update Catalog:
Update July 11, 2017: Cumulative Update KB4025339 Windows 10 v1607 Build 14393.1480 - Windows 10 Forums Source: https://support.microsoft.com/en-us/help/4022723 Find Windows 10 Version Number
Update April 11th 2017: This KB4016635 update has been replaced by KB4015217. Source: https://support.microsoft.com/en-us/help/4016635/windows-10-update-kb4016635 To download: (Not available in Windows Update)
UPDATE: This cumulative update KB4015438 has been replaced by KB4016635 on March 22nd 2017. Source: March 20, 2017—KB4015438 (OS Build 14393.969) - Microsoft Support To manually download:
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:29.
Find Us