Applies to:

Microsoft .NET Framework 4.5.2

 

A new version of this update was released on May 23, 2019. If you have downloaded and installed this update prior to this date, we recommend that you uninstall the previous version and then install the latest version of this update to avoid experiencing the issue described in the "Known Issues" section.

This update for Windows 7 Service Pack 1 (SP1), Server 2008 R2 Service Pack 1 (SP1), and Server 2008 Service Pack 2 (SP2) includes cumulative reliability improvements in .NET Framework 4.5.2. We recommend that you apply this update as part of your regular maintenance routines. Before you install this update, see the Prerequisites and Restart requirement sections.

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.

Quality and reliability improvements

CLR1

  • Addressed an issue where the Framework would throw an exception is the year in the parsed date is greater or equal the year start the next era. Now, the framework will not throw such exception.

  • Updated Japanese Era dates that are formatted for the first year in an era and for which the format pattern uses “y年”. The format of the year together with the symbol “元” is supported instead of using year number 1. Also, formatting day numbers that include “元” is supported.

  • Removed dependency of single quote to output the Gannen character in Japanese era formatting.

1 Common Language Runtime (CLR)

Additional information about this update

For more information about this update as it relates to Windows 7 SP1 and Windows Server 2008 R2 SP1, see the following article in the Microsoft Knowledge Base:

4489486 March 2019 Update for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, and 4.7.2 for Windows 7 SP1 and Server 2008 R2 SP1 (KB 4489486)

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

4489489 March 2019 Update for .NET Framework 2.0 SP2, 3.0 SP2, 4.5.2, and 4.6 for Windows Server 2008 SP2 (KB 4489489)

Known issues

Customers who install this update (4488669) for .NET Framework 4.5.2 prior to May 23, 2019, and then upgrade their systems to .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, or 4.7.2 on Windows 7 Service Pack 1, Windows Server 2008 R2 SP1, or Windows Server 2008 Service Pack 2 SP2 will experience multiple runtime application failures. The error messages that are generated may include “Entry Point Not Found” when applications try to load either Msvcp120_clr0400.dll or Msvcr120_clr0400.dll. 

Workaround 1
Customers who have not experience this issue but who plan to upgrade to a newer version of .NET Framework can take the following steps:

  1. Uninstall this update (4488669) if you have already installed it.

  2. Upgrade to .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, or 4.7.2.

  3. Apply the corresponding update 4488666 for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, or 4.7.2.

    Note Update 4488666 contains the same fixes as this update (4488669).

Workaround 2
Customers who have installed this update prior to May 23, 2019, have not experienced this issue and who don’t currently plan to upgrade to a later version of .NET Framework are still advised to uninstall the previous version of this update (4488669) and install the new version of 4488669(v2). For more information, see the "Resolution" section.

Workaround 3
Customers who have experienced this issue after they upgraded to a later version of .NET Framework can take the following steps:

  1. Uninstall the later version of .NET Framework (4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, or 4.7.2).

  2. Reinstall the desired version of .NET Framework (4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, or 4.7.2). This returns the system to a good state.

  3. Apply the corresponding update 4488666 for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, or 4.7.2.

    Note Update 4488666 contains the same fixes as this update (4488669).


Resolution
Customers should uninstall the previous version of the update, and then install the latest version of the update that was published on May 23, 2019, to avoid experiencing the issue that is described in this section. To obtain the latest update, see the next section.

How to obtain and install the update

Note This update was re-released on May 23, 2019. Please make sure that you download and install the latest version of this update.

Microsoft Update Catalog

To get the standalone package for this update, go to the Microsoft Update Catalog.

Windows Software Update Services (WSUS)

On your WSUS server, follow these steps:

  1. Select Start, select Administrative Tools, and then select Microsoft Windows Server Update Services 3.0.

  2. Expand ComputerName, and then select Action.

  3. Select Import Updates.

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

  5. After the ActiveX control is installed, you see the Microsoft Update Catalog screen. Type 4489486 for Windows 7 SP1 and Windows Server 2008 R2 SP1 or type 4489489 for Windows Server 2008 SP2 in the Search box, and then select Search

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

  7. After you select all the packages that you require, select View Basket.

  8. To import the packages to your WSUS server, select Import.

  9. After the packages are imported, select Close to return to WSUS.

The updates are now available for installation through WSUS.

Prerequisites

To apply this update, you must have .NET Framework 4.5.2 installed.

Restart requirement

You must restart the computer after you apply this update if any affected files are being used. We recommend that you exit all .NET Framework-based applications before you apply this update.

Update replacement information

This update does not replace a previously released update.

File information

The English (United States) version of this software update 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

Note: The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

x86 Windows 7 SP1 and Server 2008 SP2

File name

File version

File size

Date

Time

clr.dll

4.0.30319.36523

6,938,368

02-May-2019

01:53

clrjit.dll

4.0.30319.36523

508,976

02-May-2019

01:53

mscordacwks.dll

4.0.30319.36523

1,284,144

02-May-2019

01:53

mscordbi.dll

4.0.30319.36523

1,107,504

02-May-2019

01:53

mscorlib.dll

4.0.30319.36523

5,268,016

02-May-2019

01:53

peverify.dll

4.0.30319.36523

163,888

02-May-2019

01:53

SOS.dll

4.0.30319.36523

762,416

02-May-2019

01:53

msvcp120_clr0400.dll

12.0.52480.36480

536,856

02-May-2019

01:48

msvcr120_clr0400.dll

12.0.52480.36480

875,800

02-May-2019

01:48

x64 Windows 7 SP1, Server 2008 R2 SP1 and Server 2008 SP2

File name

File version

File size

Date

Time

clr.dll

4.0.30319.36523

10,070,064

02-May-2019

02:08

clr.dll

4.0.30319.36523

6,938,368

02-May-2019

01:53

clrjit.dll

4.0.30319.36523

1,234,480

02-May-2019

02:08

clrjit.dll

4.0.30319.36523

508,976

02-May-2019

01:53

mscordacwks.dll

4.0.30319.36523

1,731,120

02-May-2019

02:08

mscordacwks.dll

4.0.30319.36523

1,284,144

02-May-2019

01:53

mscordbi.dll

4.0.30319.36523

1,533,488

02-May-2019

02:08

mscordbi.dll

4.0.30319.36523

1,107,504

02-May-2019

01:53

mscorlib.dll

4.0.30319.36523

5,221,936

02-May-2019

02:08

mscorlib.dll

4.0.30319.36523

5,268,016

02-May-2019

01:53

peverify.dll

4.0.30319.36523

226,072

02-May-2019

02:09

peverify.dll

4.0.30319.36523

163,888

02-May-2019

01:53

SOS.dll

4.0.30319.36523

822,832

02-May-2019

02:08

SOS.dll

4.0.30319.36523

762,416

02-May-2019

01:53

msvcp120_clr0400.dll

12.0.52480.36480

678,488

02-May-2019

01:50

msvcp120_clr0400.dll

12.0.52480.36480

536,856

02-May-2019

01:48

msvcr120_clr0400.dll

12.0.52480.36480

869,464

02-May-2019

01:50

msvcr120_clr0400.dll

12.0.52480.36480

875,800

02-May-2019

01:48

How to obtain help and support for this update

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×