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.

You may encounter unexpected behavior when you use multiple IPv4 addresses on a computer that is running Windows 7 or Windows Server 2008 R2


View products that this article applies to.

Symptoms

You configure a computer that is running Windows 7 or Windows Server 2008 R2 to use multiple IPv4 addresses. However, you may encounter some unexpected behavior during the startup process. For example, the computer crashes or stops responding (hangs) during the startup process.

↑ Back to the top


Cause

This issue occurs because of an error in the Tcpip.sys component. If there is more than one IPv4 address to be configured for the computer, the OID_GEN_NETWORK_LAYER_ADDRESSES object that passes the IPv4 address will contain incorrect information.

↑ Back to the top


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: 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

There are no prerequisites for applying this hotfix.

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 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • 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 x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.16385187,47214-Jul-200901:20x86
Tcpip.sys6.1.7600.207851,289,08820-Aug-201004:34x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.16385288,33614-Jul-200901:47x64
Tcpip.sys6.1.7600.207851,888,64020-Aug-201005:50x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.16385482,89614-Jul-200901:58IA-64
Tcpip.sys6.1.7600.207853,779,45620-Aug-201004:28IA-64

↑ Back to the top


Status

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

↑ Back to the top


More Information

For more information about the OID_GEN_NETWORK_LAYER_ADDRESSES object, visit the following Microsoft Developer Network (MSDN) website: 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 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File nameX86_7226241cd72825f5823a89791361b3ff_31bf3856ad364e35_6.1.7600.20785_none_113f7ed835ef9230.manifest
File versionNot applicable
File size702
Date (UTC)20-Aug-2010
Time (UTC)18:24
PlatformNot applicable
File nameX86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20785_none_b37e0af2e0d76da6.manifest
File versionNot applicable
File size3,780
Date (UTC)20-Aug-2010
Time (UTC)18:26
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_72d25197156e45939d740e85817cd402_31bf3856ad364e35_6.1.7600.20785_none_73caa74a8cfdab91.manifest
File versionNot applicable
File size706
Date (UTC)20-Aug-2010
Time (UTC)18:24
PlatformNot applicable
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20785_none_0f9ca6769934dedc.manifest
File versionNot applicable
File size3,784
Date (UTC)20-Aug-2010
Time (UTC)18:29
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_171a01dabd1d7a5f626b2db60ee31572_31bf3856ad364e35_6.1.7600.20785_none_c9f1810e5bb96cff.manifest
File versionNot applicable
File size704
Date (UTC)20-Aug-2010
Time (UTC)18:24
PlatformNot applicable
File nameIa64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20785_none_b37faee8e0d576a2.manifest
File versionNot applicable
File size3,782
Date (UTC)20-Aug-2010
Time (UTC)18:24
PlatformNot applicable

↑ Back to the top


Keywords: consumerwin7track, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseinter, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 2175609
Revision : 2
Created on : 9/25/2018
Published on : 9/25/2018
Exists online : False
Views : 258