The remote address field is zeroed out in a completion context when a WFP callout driver calls the FwpsPendOperation0() API in Windows Vista or in Windows Server 2008

Article ID: 2635039 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You run a Windows Filtering Platform (WFP)-based network filtering application on a computer that is running Windows Vista or Windows Server 2008.
  • A WPF callout driver is used to pend packet processing by calling the FwpsPendOperation0() API.
  • This call returns a completion context.
In this scenario, the Remote Address field in the completion context is zeroed out. Additionally, the computer may crash, depending on how the callout driver handles the Remote Address field.

Note This issue may occur if a reauthentication request is triggered by calling the FwpsCompleteOperation0() API.

CAUSE

This issue occurs because of an error in the Tcpip.sys file.

RESOLUTION

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=support
Note 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 Windows Vista Service Pack 2 (SP2) or Windows Server 2008 Service Pack 2 (SP2).

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 pack
For 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 2008

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.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.0.600 2 . 22xxxWindows Vista and Windows Server 2008SP2LDR
  • 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 x86-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Tcpipreg.sys6.0.6002.2273631,23201-Nov-201115:02x86
Tcpip.sys6.0.6002.22736913,28001-Nov-201119:43x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Tcpipreg.sys6.0.6002.2273640,44801-Nov-201114:21x64
Tcpip.sys6.0.6002.227361,423,23201-Nov-201119:39x64
For all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Tcpipreg.sys6.0.6002.2273680,89601-Nov-201114:26IA-64
Tcpip.sys6.0.6002.227362,968,44801-Nov-201119:34IA-64

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 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 x86-based versions of Windows Vista and of Windows Server 2008
Collapse this tableExpand this table
File nameX86_b2ee9b504eea343dc461ecaf40a1f6e1_31bf3856ad364e35_6.0.6002.22736_none_8b529b94efe876ed.manifest
File versionNot Applicable
File size717
Date (UTC)01-Nov-2011
Time (UTC)19:50
File nameX86_ec98e552b312707651f66ec19a41aa38_31bf3856ad364e35_6.0.6002.22736_none_6e07fde8149314fc.manifest
File versionNot Applicable
File size702
Date (UTC)01-Nov-2011
Time (UTC)19:50
File nameX86_microsoft-windows-l..istry-support-tcpip_31bf3856ad364e35_6.0.6002.22736_none_8872e7c81bc3c1b6.manifest
File versionNot Applicable
File size4,845
Date (UTC)01-Nov-2011
Time (UTC)17:40
File nameX86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.22736_none_b573c4137cbd0820.manifest
File versionNot Applicable
File size6,762
Date (UTC)01-Nov-2011
Time (UTC)19:51
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
Collapse this tableExpand this table
File nameAmd64_68850aff5446646e9f64b6710eb72668_31bf3856ad364e35_6.0.6002.22736_none_490146d673ec0a60.manifest
File versionNot Applicable
File size706
Date (UTC)01-Nov-2011
Time (UTC)19:50
File nameAmd64_b3627c05e787b6b16271a21877e8285f_31bf3856ad364e35_6.0.6002.22736_none_d13027978d049da7.manifest
File versionNot Applicable
File size721
Date (UTC)01-Nov-2011
Time (UTC)19:50
File nameAmd64_microsoft-windows-l..istry-support-tcpip_31bf3856ad364e35_6.0.6002.22736_none_e491834bd42132ec.manifest
File versionNot Applicable
File size5,122
Date (UTC)01-Nov-2011
Time (UTC)16:16
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.22736_none_11925f97351a7956.manifest
File versionNot Applicable
File size6,784
Date (UTC)01-Nov-2011
Time (UTC)19:51
Additional files for all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameIa64_89f70a689583400d9d17984f20a41789_31bf3856ad364e35_6.0.6002.22736_none_7d88446d97e1ff91.manifest
File versionNot Applicable
File size1,066
Date (UTC)01-Nov-2011
Time (UTC)19:50
File nameIa64_microsoft-windows-l..istry-support-tcpip_31bf3856ad364e35_6.0.6002.22736_none_88748bbe1bc1cab2.manifest
File versionNot Applicable
File size5,118
Date (UTC)01-Nov-2011
Time (UTC)15:58
File nameIa64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.22736_none_b57568097cbb111c.manifest
File versionNot Applicable
File size6,773
Date (UTC)01-Nov-2011
Time (UTC)19:51

Properties

Article ID: 2635039 - Last Review: December 14, 2011 - Revision: 1.0
APPLIES TO
  • Windows Vista Business
  • Windows Vista Business 64-bit Edition
  • Windows Vista Enterprise
  • Windows Vista Enterprise 64-bit Edition
  • Windows Vista Home Basic
  • Windows Vista Home Basic 64-bit Edition
  • Windows Vista Home Premium
  • Windows Vista Home Premium 64-bit Edition
  • Windows Vista Starter
  • Windows Vista Ultimate
  • Windows Vista Ultimate 64-bit Edition
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Datacenter without Hyper-V
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Enterprise without Hyper-V
  • Windows Server 2008 for Itanium-Based Systems
  • Windows Server 2008 Foundation
  • Windows Server 2008 Standard
  • Windows Server 2008 Standard without Hyper-V
  • Windows Web Server 2008
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseadvanced KB2635039

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com