- 3163649 MS16-063: Cumulative security update for Internet Explorer: June 14, 2016
- 3163656 MS16-068: Cumulative security update for Microsoft Edge: June 14, 2016
- 3163622 MS16-072: Security update for Group Policy: June 14, 2016
- 3164028 MS16-073: Security update for kernel mode drivers: June 14, 2016
- 3164036 MS16-074: Security Update for Microsoft graphics component: June 14, 2016
- 3164038 MS16-075: Security Update for Windows SMB Server: June 14, 2016
- 3165191 MS16-077: Security update for Web Proxy Autodiscovery (WPAD): June 14, 2016
- 3165479 MS16-078: Security update to Windows Diagnostic Hub: June 14, 2016
- 3164302 MS16-080: Security update for Microsoft Windows PDF: June 14, 2016
- 3165270 MS16-082: Security update for Windows Structured Query: June 14, 2016
Windows 10 updates are cumulative. Therefore, this package contains all previously released fixes. If you have installed earlier updates, only the new fixes that are contained in this package will be downloaded and installed on your computer. If you are installing a Windows 10 update package for the first time, the package for the x86 version is 320 MB and the package for the x64 version is 680 MB.
- 3159398 MS16-072: Description of the security update for Group Policy: June 14, 2016
- 3163017 Cumulative update for Windows 10: June 14, 2016
- 3163018 Cumulative update for Windows 10 Version 1511 and Windows Server 2016 Technical Preview 4: June 14, 2016
- 3163016 Cumulative Update for Windows Server 2016 Technical Preview 5: June 14 2016
SymptomsAll user Group Policy, including those that have been security filtered on user accounts or security groups, or both, may fail to apply on domain joined computers.
CauseThis issue may occur if the Group Policy Object is missing the Read permissions for the Authenticated Users group or if you are using security filtering and are missing Read permissions for the domain computers group.
ResolutionTo resolve this issue, use the Group Policy Management Console (GPMC.MSC) and follow one of the following steps:
- Add the Authenticated Users group with Read Permissions on the Group Policy Object (GPO).
- If you are using security filtering, add the Domain Computers group with read permission.
Method 1: Windows UpdateThis update will be downloaded and installed automatically.
Method 2: Microsoft Update CatalogTo get the stand-alone package for this update, go to the Microsoft Update Catalog website.
PrerequisitesThere are no prerequisites for installing this update.
Restart informationYou must restart the computer after you apply this update.
Update replacement informationThis update replaces the previously released update 3156387.
The .NET framework version 3.5 and earlier versions did not provide support for applications to use Transport Layer Security (TLS) System Default Versions as a cryptographic protocol. This update enables the use of TLS v1.2 in the .NET Framework 3.5.
The following registry keys can be set to use the operating system defaults for SSL and TLS instead of the hardcoded .NET Framework defaults for a managed application running on the computer.
- For 64-bit operating systems:
- For 32-bit operating systems:
Note If the application has set the ServicePointManager.SecureProtocol in code or through config files to a specific value, or uses the SslStream.AuthenticateAs* APIs to specify a specific SslProtocols enum, the registry setting behavior does not occur.
In addition, we have added the SslProtocolsExtensions enumeration that you can use as an option for setting TLS v1.2, TLS v1.1, as well as operating system defaults for the ServicePointManager.SecurityProtocol property when targeting .NET framework version 2.0 SP2. (See the Developer Guidance section for the information on how to use the extensions.)
For more information about how to enable TLS v1.1 or v1.2 as operating system defaults, follow the instructions at https://technet.microsoft.com/en-us/library/dn786418(v=ws.11).aspx#BKMK_SchannelTR_TLS12.
Article ID: 3163017 - Last Review: Mar 30, 2017 - Revision: 3