- 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
- 3185876 MS16-113: Security Update for Windows Secure Kernel Mode: 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
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 459 MB and the package for the x64 version is 1,020 MB.
Issue 1Some 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.
Consider the following scenario:
A specified logon session does not exist. It may already have been terminated.
- 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.
This problem may occur if you have security update 3187754 installed.
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.
Artikel-id: 3185611 - Laatst bijgewerkt: 21 dec. 2016 - Revisie: 1