Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Hotfix rollup 2908374 is available for the .NET Framework 3.5.1 on Windows 7 SP1 or Windows Server 2008 R2 SP1

Hotfix rollup 2908374 is available for the .NET Framework 3.5.1 on Windows 7 SP1 or Windows Server 2008 R2 SP1

View products that this article applies to.

To apply this hotfix rollup, go to the following knowledge base article and download the correct hotfix rollup:

2926993 Hotfix rollup 2926993 is available for the .NET Framework 3.5.1 on Windows 7 SP1 or Windows Server 2008 R2 SP1

↑ Back to the top

Introduction

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

This hotfix rollup is available for the following operating systems:
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2 Service Pack 1 (SP1)

↑ Back to the top

More Information

Hotfix Information

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:
http://support.microsoft.com/contactus/?ws=support
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.

Restart requirement

You must 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.
File information
The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

LDR service branch

For all supported x86-based versions of Windows 7 SP1 and Windows Server 2008 R2 SP1
File nameFile versionFile sizeDateTime
System.directoryservices.dll2.0.50727.7047401,40821-Nov-201300:00
System.dll2.0.50727.70473,198,97621-Nov-201300:00
Mscorlib.dll2.0.50727.70474,554,75221-Nov-201300:00
Mscordacwks.dll2.0.50727.7047990,36021-Nov-201300:00
Mscorwks.dll2.0.50727.70475,943,96021-Nov-201300:00
Sos.dll2.0.50727.7047389,76821-Nov-201300:00
For all supported x64-based versions of Windows 7 SP1 and Windows Server 2008 R2 SP1
File nameFile versionFile sizeDateTime
Mscorlib.dll2.0.50727.70474,571,13621-Nov-201300:25
Mscordacwks.dll2.0.50727.70471,757,33621-Nov-201300:25
Mscorwks.dll2.0.50727.704710,007,19221-Nov-201300:25
Sos.dll2.0.50727.7047486,02421-Nov-201300:25
System.directoryservices.dll2.0.50727.7047401,40821-Nov-201300:25
System.dll2.0.50727.70473,198,97621-Nov-201300:25
System.directoryservices.dll2.0.50727.7047401,40821-Nov-201300:00
System.dll2.0.50727.70473,198,97621-Nov-201300:00
Mscorlib.dll2.0.50727.70474,554,75221-Nov-201300:00
Mscordacwks.dll2.0.50727.7047990,36021-Nov-201300:00
Mscorwks.dll2.0.50727.70475,943,96021-Nov-201300:00
Sos.dll2.0.50727.7047389,76821-Nov-201300:00

↑ Back to the top

Issues that this hotfix rollup resolves

Issue 1:

ASP.NET applications that access additional functionality by using the application configuration settings can experience a deadlock at startup.

Issue 2:

The NET Framework 2.0 and 3.5 applications will throw a NullReferenceException when they use GetEnvironmentVariable if the registry key does not exist.

Issue 3:

DirectorySearcher.FindOne() may throw overflow exceptions when it runs as a 32-bit process that is linked with the LARGEADDRESSAWARE compiler flag and it runs on an 64-bit operating system that is configured to use the 3 GB memory. Applications hosted inside IIS may see this exception as w3wp.exe is compiled as a LARGEADDRESSAWARE application.

This fix makes sure that memory addresses greater than 2 GB are handled correctly.

Issue 4:

When an update is being installed, Fusion can access a state where NGEN is called repeatedly. This causes entries in the following registry key keep to grow until the computer freezes:


          HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727\NGenService\Roots
          HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\NativeImagesIndex

↑ Back to the top

Keywords: kb, kbsurveynew, kbhotfixserver, kbfix, kbexpertiseadvanced, kbqfe

↑ Back to the top

Article Info
Article ID : 2908374
Revision : 3
Created on : 3/10/2020
Published on : 3/11/2020
Exists online : False
Views : 324