Hotfix rollup 3013370 for the .NET Framework 3.5.1 on Windows 7 SP1 and Windows Server 2008 R2 SP1

Applies to: .NET Framework 3.5.1Windows 7 Service Pack 1Windows Server 2008 R2 Service Pack 1

This article describes hotfix rollup 3013370 that is available for the Microsoft .NET Framework 3.5.1. For more information about the issues that the hotfix rollup resolves, see the "Issues that this hotfix rollup resolves" section.


A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

More Information


To apply this hotfix, you must have the .NET Framework 3.5.1 installed.

Restart requirement

You have to restart the computer after you apply this hotfix if any affected files are being used. We recommend that you close all .NET Framework-based applications before you apply this hotfix.

Hotfix replacement information

This hotfix package does not replace a previously released hotfix package.

Issues that this hotfix rollup resolves

Issue 1

System.IO.IsolatedStorage in the .NET Framework 2.0 and the .NET Framework 3.5.1 uses a hash algorithm that is not Federal Information Processing Standards (FIPS)-compliant. This can cause some applications to fail compliance checks on operating systems that have FIPS enabled.

This hotfix replaces the involved hash algorithm by using the same FIPS-compliant version that is used in the .NET Framework 4.0 and later versions.

For more information about this issue, see KB 3021977 Replicationapp.exe crashes when FIPS is enabled on a Lync Server 2013-based computer that has .NET Framework installed .