Symptoms

Assume that you are running a 32-bit application that has the /LARGEADDRESSAWARE option enabled on a computer that is running a 64-bit version of Windows. Then, the application calls various network-related APIs such as GetHostByAddress() or GetAdaptersAddresses(). In this situation, you may receive an error message that resembles one of the following:

  • WSANO_DATA

  • ERROR_NO_DATA (232)

  • ERROR_NOACCESS (998)

This issue occurs on 64-bit versions of the following operating systems:

  • Windows Vista

  • Windows Server 2008

  • Windows 7

  • Windows Server 2008 R2

Note This issue occurs if the application experiences high memory usage.

Cause

This issue occurs because of a problem with address-conversion routines. The 32-bit application passes a user-mode memory buffer that is allocated beyond the standard 2-gigabyte (GB) memory address space by using a network-related API such as GetHostByAddress() or GetHostByName(). The address is then converted from a 32-bit address to a 64-bit address in kernel routines. The address-conversion routines incorrectly sign-extend the particular address to convert it into a 64-bit address. This 64-bit address is outside the scope of the user-mode address pool. Therefore, the kernel denies read or write access to the address and returns an error to the application.

Resolution

After you install the hotfix, the conversion routines correctly convert a 32-bit address that is supplied by the user application to an equivalent 64-bit address without sign-extension.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:

  • Windows Vista Service Pack 2 (SP2)

  • Windows Server 2008 Service Pack 2 (SP2)

  • Windows 7 Service Pack 1 (SP1)

  • Windows Server 2008 R2 Service Pack 1 (SP1)

For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:

935791 How to obtain the latest Windows Vista service packFor more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 How to obtain the latest service pack for Windows Server 2008For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix 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 Vista and Windows Server 2008 file information notes

Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    Version

    Product

    SR_Level

    Service branch

    6.0.600 2. 22xxx

    Windows Vista and Windows Server 2008

    SP2

    LDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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.

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

File name

File version

File size

Date

Time

Platform

Nsi.dll

6.0.6002.22688

11,264

02-Aug-2011

15:27

x64

Nsiproxy.sys

6.0.6002.22688

24,064

02-Aug-2011

13:55

x64

Nsisvc.dll

6.0.6002.22688

24,576

02-Aug-2011

15:27

x64

Winnsi.dll

6.0.6002.22688

22,016

02-Aug-2011

15:28

x64

Nsi.dll

6.0.6002.22688

8,192

02-Aug-2011

15:17

x86

Winnsi.dll

6.0.6002.22688

14,848

02-Aug-2011

15:18

x86

For all supported IA-64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Nsi.dll

6.0.6002.22688

17,920

02-Aug-2011

15:25

IA-64

Nsiproxy.sys

6.0.6002.22688

49,664

02-Aug-2011

14:04

IA-64

Nsisvc.dll

6.0.6002.22688

53,248

02-Aug-2011

15:25

IA-64

Winnsi.dll

6.0.6002.22688

37,376

02-Aug-2011

15:27

IA-64

Nsi.dll

6.0.6002.22688

8,192

02-Aug-2011

15:17

x86

Winnsi.dll

6.0.6002.22688

14,848

02-Aug-2011

15:18

x86

Windows 7 and Windows Server 2008 R2 file information notes

  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.1.760 1.17xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    GDR

    6.1.760 1.22xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    LDR

  • GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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.

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Nsiproxy.sys

6.1.7601.17856

24,576

02-Jun-2012

02:50

x64

Nsiproxy.sys

6.1.7601.22009

24,576

01-Jun-2012

02:35

x64

Nsi.dll

6.1.7601.17856

8,704

02-Jun-2012

04:39

x86

Winnsi.dll

6.1.7601.17856

16,896

02-Jun-2012

04:41

x86

Nsi.dll

6.1.7601.22009

8,704

01-Jun-2012

04:50

x86

Winnsi.dll

6.1.7601.22009

16,896

01-Jun-2012

04:52

x86

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Nsiproxy.sys

6.1.7601.17856

53,760

02-Jun-2012

01:52

IA-64

Nsiproxy.sys

6.1.7601.22009

53,760

01-Jun-2012

01:53

IA-64

Nsi.dll

6.1.7601.17856

8,704

02-Jun-2012

04:39

x86

Winnsi.dll

6.1.7601.17856

16,896

02-Jun-2012

04:41

x86

Nsi.dll

6.1.7601.22009

8,704

01-Jun-2012

04:50

x86

Winnsi.dll

6.1.7601.22009

16,896

01-Jun-2012

04:52

x86

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about the /LARGEADDRESSAWARE option, visit the following Microsoft website:

General information about the /LARGEADDRESSAWARE optionFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008

File name

Amd64_c6d4eaed9183d43ed82b76b624c52c50_31bf3856ad364e35_6.0.6002.22688_none_e05796d1cf0f86a5.manifest

File version

Not Applicable

File size

1,048

Date (UTC)

04-Aug-2011

Time (UTC)

10:15

Platform

Not Applicable

File name

Amd64_microsoft-windows-usermodensi_31bf3856ad364e35_6.0.6002.22688_none_d0a25f36964eda3e.manifest

File version

Not Applicable

File size

11,833

Date (UTC)

02-Aug-2011

Time (UTC)

15:47

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

2,608

Date (UTC)

04-Aug-2011

Time (UTC)

10:15

Platform

Not Applicable

File name

Wow64_microsoft-windows-usermodensi_31bf3856ad364e35_6.0.6002.22688_none_daf70988caaf9c39.manifest

File version

Not Applicable

File size

7,616

Date (UTC)

02-Aug-2011

Time (UTC)

15:22

Platform

Not Applicable

Additional files for all supported IA-64-based versions of Windows Server 2008

File name

Ia64_8f4e884ba8a1e575211d5b9921c9bb36_31bf3856ad364e35_6.0.6002.22688_none_e4216fea51c8ead4.manifest

File version

Not Applicable

File size

1,046

Date (UTC)

04-Aug-2011

Time (UTC)

10:15

Platform

Not Applicable

File name

Ia64_microsoft-windows-usermodensi_31bf3856ad364e35_6.0.6002.22688_none_748567a8ddef7204.manifest

File version

Not Applicable

File size

11,824

Date (UTC)

02-Aug-2011

Time (UTC)

15:36

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

1,930

Date (UTC)

04-Aug-2011

Time (UTC)

10:15

Platform

Not Applicable

File name

Wow64_microsoft-windows-usermodensi_31bf3856ad364e35_6.0.6002.22688_none_daf70988caaf9c39.manifest

File version

Not Applicable

File size

7,616

Date (UTC)

02-Aug-2011

Time (UTC)

15:22

Platform

Not Applicable

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

Amd64_microsoft-windows-usermodensi_31bf3856ad364e35_6.1.7601.17856_none_d05eeee4de3204ca.manifest

File version

Not Applicable

File size

8,305

Date (UTC)

04-Jun-2012

Time (UTC)

08:26

Platform

Not Applicable

File name

Amd64_microsoft-windows-usermodensi_31bf3856ad364e35_6.1.7601.22009_none_d121744bf7249826.manifest

File version

Not Applicable

File size

8,305

Date (UTC)

04-Jun-2012

Time (UTC)

08:26

Platform

Not Applicable

File name

Update-bf.mum

File version

Not Applicable

File size

2,719

Date (UTC)

04-Jun-2012

Time (UTC)

08:15

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

2,774

Date (UTC)

04-Jun-2012

Time (UTC)

08:14

Platform

Not Applicable

File name

Wow64_microsoft-windows-usermodensi_31bf3856ad364e35_6.1.7601.17856_none_dab399371292c6c5.manifest

File version

Not Applicable

File size

4,690

Date (UTC)

02-Jun-2012

Time (UTC)

05:01

Platform

Not Applicable

File name

Wow64_microsoft-windows-usermodensi_31bf3856ad364e35_6.1.7601.22009_none_db761e9e2b855a21.manifest

File version

Not Applicable

File size

4,690

Date (UTC)

01-Jun-2012

Time (UTC)

05:07

Platform

Not Applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name

Ia64_microsoft-windows-usermodensi_31bf3856ad364e35_6.1.7601.17856_none_7441f75725d29c90.manifest

File version

Not Applicable

File size

8,303

Date (UTC)

04-Jun-2012

Time (UTC)

08:15

Platform

Not Applicable

File name

Ia64_microsoft-windows-usermodensi_31bf3856ad364e35_6.1.7601.22009_none_75047cbe3ec52fec.manifest

File version

Not Applicable

File size

8,303

Date (UTC)

04-Jun-2012

Time (UTC)

08:15

Platform

Not Applicable

File name

Update-bf.mum

File version

Not Applicable

File size

1,425

Date (UTC)

04-Jun-2012

Time (UTC)

08:14

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

1,447

Date (UTC)

04-Jun-2012

Time (UTC)

08:14

Platform

Not Applicable

File name

Wow64_microsoft-windows-usermodensi_31bf3856ad364e35_6.1.7601.17856_none_dab399371292c6c5.manifest

File version

Not Applicable

File size

4,690

Date (UTC)

02-Jun-2012

Time (UTC)

05:01

Platform

Not Applicable

File name

Wow64_microsoft-windows-usermodensi_31bf3856ad364e35_6.1.7601.22009_none_db761e9e2b855a21.manifest

File version

Not Applicable

File size

4,690

Date (UTC)

01-Jun-2012

Time (UTC)

05:07

Platform

Not Applicable

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.