Cumulative update for Windows 10 Version 1607: September 13, 2016

View products that this article applies to.

This article is superseded by KB 3193494 .

Summary

This security update includes improvements and fixes in the functionality of Windows 10 Version 1607. It also resolves the following vulnerabilities in Windows:

3183038 MS16-104: Cumulative security update for Internet Explorer: September 13, 2016
3183043 MS16-105: Cumulative security update for Microsoft Edge: September 13, 2016
3185848 MS16-106: Security update for Microsoft Graphics Component: September 13, 2016
3178467 MS16-110: Security update for Windows: September 13, 2016
3186973 MS16-111: Security Update for Microsoft Kernel: September 13, 2016
3178469 MS16-112: Security update for Windows Lock Screen: September 13, 2016
3185879 MS16-114: Security Update for Windows SMBv1 Server: September 13, 2016
3188733 MS16-115: Security update for Microsoft Windows PDF Library: September 13, 2016
3188724 MS16-116: Security Update in OLE Automation for VBScript Scripting Engine: September 13, 2016

Windows 10 updates are cumulative. Therefore, this package contains all previously released fixes.

If you have installed previous updates, only the new fixes that are contained in this package will be downloaded and installed to your computer. If you are installing a Windows 10 update package for the first time, the package for the x86 version is 255 MB and the package for the x64 version is 431 MB.

↑ Back to the top

More Information

Known issues in this security update

Issue 1
Some users are experiencing an installation failure when they try to download this update because of a network transmission issue. To resolve the installation failure, please download KB3193494. Update 3193494 includes the same set of fixes as this update.
Issue 2
Symptoms

Consider the following scenario:
- You try to access a file server by using the SMBv1 protocol through an application such as File Explorer.
- The application uses the CONNECT_INTERACTIVE flag for the WNetAddConnection API.
- You're using a computer that's logged in through Microsoft Account credentials.
- The network credentials you're using to access the file server share are not present in Credential Manager.
- The firewall profile on the computer is set to Public.
In this scenario, you receive the following error message:

A specified logon session does not exist. It may already have been terminated.

This problem may occur if you have security update 3187754 installed.

Workaround

To work around this problem, use any of these options:
- Option 1: If possible, use SMBv2 instead of SMBv1.
- Option 2: Pass credentials explicitly through the following net use cmd:
```
net use \\<serverName>\<shareName> /user: <DomainName\UserName> <Password>
 
```
- Option 3: Change the network profile to Private for private home networks instead of Public.
- Option 4: Save credentials for trusted network shares in Credential Manager.