August 17, 2019—KB4512495 (OS Build 14393.3181)

S’applique à : Windows 10, version 1607Windows Server 2016

Highlights


  • Updates an issue with downloading copyrighted digital media (music, TV shows, movies, and so on) from certain websites using Microsoft Edge and Internet Explorer.
  • Updates an issue that causes File Explorer to intermittently stop working. 

Improvements and fixes


This non-security update includes quality improvements. Key changes include:

  • Addresses an issue with downloading digital rights management (DRM) files from certain websites using Microsoft Edge and Internet Explorer. 
  • Addresses an issue in the Windows Push Notification Platform Connection Provider that causes File Explorer to intermittently stop working. 
  • Addresses an issue that may cause a new domain certificate to stop working after a day. This issue occurs when you set up the domain using a live account and the virtual private network (VPN) is configured using the Anywhere Access wizard. The error is, "Error 619: A connection to the remote computer could not be established, so the port used for this communication was closed". After more connection attempts, the following error appears, "Link to VPN connection failed. Reconnecting pending ..." 
  • Addresses an issue that prevents an App-V application from opening and displays a network failure error. This issue occurs under certain circumstances, such as when a system's battery is low or there is an unexpected power failure. 
  • Addresses an issue that causes spaceport.sys to stop working with a 0x9E error. 
  • Addresses an issue with enclosure awareness for a scenario that does not include Storage Spaces Direct (S2D). 
  • Addresses an issue that prevents some users from receiving a TTL value when they are added as members of Shadow Principals. This occurs for users who have distinguished names (DN) that contain an escape character. The TTL value is now added as expected. 
  • Addresses an issue that may break the domain trust when the Recycle Bin is configured on the domain that carries the trust.
  • Addresses an issue that may prevent devices from starting when they start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) or System Center Configuration Manager (SCCM). The error is, "Status: 0xc0000001, Info: A required device isn't connected or can't be accessed."
  • Addresses an issue that may cause the following to stop responding:
    • Applications that were made using Visual Basic 6 (VB6).
    • Macros that use Visual Basic for Applications (VBA).
    • Scripts or apps that use Visual Basic Scripting Edition (VBScript).

You may also receive an "Invalid procedure call” error.

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

Known issues in this update


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

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.
Applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent may fail to return results after the first page of data, often 50 or 100 entries. When requesting additional pages you may receive the error, “1359: an internal error occurred.” This issue is resolved in KB4516044.

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 (KB4509091) 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

Release Channel Available Next Step
Windows Update or Microsoft Update Yes Go to Settings > Update & Security > Windows Update and select Check for updates.
Microsoft Update Catalog Yes To get the standalone package for this update, go to the Microsoft Update Catalog.
Windows Server Update Services (WSUS) Yes

This update will automatically synchronize with WSUS if you configure Products and Classifications as follows:

Product: Windows 10

Classification: Update

File information

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