An update is available for the .NET Framework 3.5 on Windows 8 and Windows Server 2012: September 2013

Dotyczy: Windows 8Windows 8 EnterpriseWindows 8 Pro


An update for the Microsoft .NET Framework 3.5 is available. For more information about the issues that this update resolves, see the "Issues that this update resolves" section.

More Information

How to obtain this update

Microsoft Download Center

The following file is available for download from the Microsoft Download Center:

Download Download the package now.

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Restart requirement

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

Command-line switches for this update

For more information about the various command-line switches that are supported by this update, visit the following MSDN website:

Update replacement information

This update does not replace any previously released update.

How to uninstall this update

To remove this update, use the Programs and Features item in Control Panel.

Issues that this update resolves

Issue 1

Consider the following scenario:
  • You use a browser which can’t be recognized by ASP.NET, such as Amazon Kindle Fire 2 or Internet Explorer 11, to access an ASP.NET-based webpage.
  • You trigger a postback event on that webpage.
In this scenario, the postback operation fails, and you receive the following error message:
"Script Error encountered", "'__doPostBack' is undefined"

Issue 2

Consider the following scenario:
  • An ASP.NET website renders different content based on the user browser.
  • A user uses Internet Explorer 11 to visit this ASP.NET website.
In this scenario, ASP.NET cannot recognize Internet Explorer 11 and will not render the content correctly. After the user applies this hotfix, Internet Explorer 11 can be recognized as InternetExplorer by ASP.NET.

Issue 3

Consider the following scenario:
  • An ASP.NET page contains an update panel, and inside it there is an ImageButton. If user clicks ImageButton, it will trigger a partial postback event and the server side click event.
  • A user uses Internet Explorer 10 or a later version to access this ASP.NET page, and then clicks the Imagebutton.
In this scenario, the partial postback fails, and the server side click event is not fired.

Issue 4

Consider the following scenario:
  • There is an ASP.NET page that contains a menu control.
  • A user uses Internet Explorer 11 to access that page, and presses Tab to switch the focus between the menu control and other controls.
In this scenario, the user will receive the following JavaScript error message:
Error: SCRIPT5007: Unable to get value of the property 'toLowerCase': object is null or undefined
Note 1 There is a configuration switch to be used to revert back to the old behavior:
<add key="aspnet:UseLegacyBrowserCaps" value="true" />