Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Note

Known issues in this security update

View products that this article applies to.

Summary

This update resolves a vulnerability in the Microsoft .NET Framework that could allow remote code execution when the .NET Framework fails to properly validate input before loading libraries. An attacker who successfully exploits this vulnerability could take control of an affected system. The attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. To learn more about this vulnerability, see Microsoft Common Vulnerabilities and Exposures CVE-2017-0160.

Important

  • If you install a language pack after you install this update, you must reinstall this update. Therefore, we recommend that you install any language packs that you need before you install this update. For more information, see Add language packs to Windows.

Additional information about this security update

  • For any Windows Management Instrumentation (WMI) applications returning the following error message:

    Get-WmiObject: The method or operation is not implemented.

    To temporarily disable this update, customers can apply the following registry entry to their system.

    Warning Enabling this registry entry could allow security vulnerabilities including Remote Code Execution.

    Registry entry

    • For 32-bit process on 32-bit system and 64-bit process on 64-bit system:

      HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework\v4.0.30319@WMIDisableCOMSecurity=1

    • For 32-bit process on 64-bit system:

      HKEY_LOCAL_MACHINE \Software\Wow6432Node\Microsoft\.NETFramework\v4.0.30319@WMIDisableCOMSecurity=1


    Notes

    • This registry entry should be a DWORD entry.

    • This registry entry restores the previous unsecured state.

  • For more information about this security update as it relates to Windows Server 2012, see the following article in the Microsoft Knowledge Base:

    4014986 Security Only update for the .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, and 4.6.2 updates for Windows Server 2012: April 11, 2017

How to obtain and install the update

Method 1: Microsoft Update Catalog

To get the stand-alone package for this update, go to the Microsoft Update Catalog.

Method 2: Windows Software Update Services (WSUS)

On your WSUS server, follow these steps:

  1. Click Start, click Administrative Tools, and then click Microsoft Windows Server Update Services 3.0.

  2. Expand ComputerName, and then click Action.

  3. Click Import Updates.

  4. WSUS will open a browser window in which you may be prompted to install an ActiveX control. You must install the ActiveX control to continue.

  5. Once the control is installed, you will see the Microsoft Update Catalog screen. Enter 4014986 in the Search box, and then click Search.

  6. Locate the .NET Framework packages that match the operating systems, languages, and processors in your environment. Click Add to add them to your basket.

  7. When you have selected all the packages you need, click View Basket.

  8. Click Import to import the packages to your WSUS server.

  9. Click Close once the packages have been imported to return to WSUS.

The updates are now available for installation through WSUS.

Update deployment information

For deployment details for this security update, go to the following article in the Microsoft Knowledge Base:

Security update deployment information: April 11, 2017

Update removal information

Note We do not recommend that you remove any security update. To remove this update, use the Programs and Features item in Control Panel.

Update restart information

This update does not require a system restart after you apply it unless files that are being updated are locked or are being used.

Update replacement information

This update does not replace any previously released update.

File information

Package Name

Package Hash SHA 1

Package Hash SHA 2

Windows8-RT-KB4014549-x64.msu

CF76A8E74993E961978B0AC2513E3AD0AA7A090D

BDE1D70AAF4E191AECA2ACFEF99B8FB0C75000E06738DC46D1AD5657389145B4

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2012 file information

File name

File version

File size

Date

Time

Platform

Msvcp120_clr0400.dll

12.0.52512.0

690,016

20-Mar-2017

05:16

x64

Msvcr120_clr0400.dll

12.0.52512.0

993,632

20-Mar-2017

05:16

x64

System.management.dll

4.6.1646.0

415,424

20-Mar-2017

08:06

x86

Wminet_utils.dll

4.6.1646.0

188,080

20-Mar-2017

08:01

x64

System.management.dll

4.6.1646.0

415,424

20-Mar-2017

08:06

x86

Msvcp120_clr0400.dll

12.0.52512.0

484,552

20-Mar-2017

05:16

x86

Msvcr120_clr0400.dll

12.0.52512.0

987,848

20-Mar-2017

05:16

x86

Wminet_utils.dll

4.6.1646.0

136,368

20-Mar-2017

08:06

x86

How to obtain help and support for this security update

Applies to

This article applies to the following:

  • Microsoft .NET Framework 4.6.2 when used with:

    • Windows Server 2012

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×