Hotfix rollup 3000058 for the .NET Framework 3.5 on Windows 8 or Windows Server 2012

Applies to: Windows 8 EnterpriseWindows 8 ProWindows 8

Introduction


This article describes hotfix rollup 3000058 that is available for the Microsoft .NET Framework 3.5. For more information about the issues that the hotfix rollup resolves, see the "More Information" section.

This hotfix rollup is available for the following operating systems:
  • Windows 8
  • Windows Server 2012

Resolution


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


Prerequisites

To apply this hotfix, you must have the .NET Framework 3.5 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
A managed application profiler crashes when you profile an ASP.NET application by using the .NET Framework 3.5.

This hotfix corrects the conditions under which the application crashes because of this issue.

Issue 2
A recent security hotfix exposes a faulty dependency between Network Class Libraries and System.Configuration. The manifestation of this issue is seen only when you use the legacy No-Touch Deployment.

This hotfix moves the configuration from App.Config to registry:

HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node\]Microsoft\.NETFramework\v4.0.30319
SchUseStrongCrypto DWORD 1

The following keys will be enabled, and that allows the EXE path configuration of each process:

HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node\]Microsoft\.NETFramework\v4.0.30319\System.Net.ServicePointManager.SecurityProtocol

S:\Prj\console_pg\console_pg45\bin\Release\console_pg45.exe REG_SZ <SecurityProtocolType>
<RegistryKeyName: the application full path> REG_SZ <RegistryKeyValue:default ServicePointManager.SecurityProtocol value>

Examples:
  • S:\contoso\contoso_v1.exe REG_SZSsl3
  • S:\contoso\contoso_v2.exe REG_SZ Tls12, Tls11

Notes:
  • For 32-bit applications that are running on a 64-bit operating system, the Wow6432Node path needs to be included in the name. (This does not apply to 32-bit applications that are running on a 32-bit operating system.)
  • The version has to correspond to the .NET Framework that the application uses. The version will change with future releases of the .NET Framework.
  • The full path of the EXE will be used in its long form. If the application is started by using the 8.3 short file name format, the registry key should contain the long file format. For example, if you execute C:\contoso\CONSOL~1.EXE, the registry key should be C:\contoso\contoso_v1.exe.
Issue 3

After you apply September security update, the Page.IsPostBack property may be incorrect.

This update contains a fix for this issue. For recommended practice for cross-page posts and more information about EnableViewStateMac, go to this blog.