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.

Invalid subnet masks occur after IP configuration change and computer restart in Windows


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a computer that is running Windows 8.1, Windows Server 2012 R2, Windows 7, or Windows Server 2008 R2.
  • The network adapter on this computer is configured to use multiple IPv4 addresses.
  • The IPv4 addresses are located in different IP subnets.
  • You make a change to the IP configuration, and then you restart the computer.

In this scenario, the subnet masks may be invalid.

↑ Back to the top


Resolution

To resolve this issue for Windows 8.1 and Windows Server 2012 R2, install update 2919355.
To resolve this issue for Windows 7 and Windows Server 2008 R2, install the hotfix that is described in this article.

Update information for Windows 8.1 and Windows Server 2012 R2

For more information about how to obtain update 2919355, click the following article number to view the article in the Microsoft Knowledge Base:
2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update April, 2014


Hotfix information for Windows 7 and Windows Server 2008 R2

A supported hotfix is available from Microsoft Support. 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, go to the following Microsoft website: 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 have Service Pack 1 for Windows 7 or Windows Server 2008 R2 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

↑ Back to the top


File information
The English (United States) 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 and 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 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.

    VersionProductSR_LevelService branch
    6.1.760
    1.
    22xxx
    Windows 7 and Windows Server 2008 R2SP1LDR
  • 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 7 and Windows Server 2008 R2" 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
Tcpipreg.sys6.1.7601.2257835,84022-Jan-201401:25x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Tcpipreg.sys6.1.7601.2257845,56822-Jan-201401:47x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Tcpipreg.sys6.1.7601.2257891,13622-Jan-201401:16IA-64

Additional file information

Additional file information for Windows 7 and Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File nameX86_375747bf2ebdec20aebc99c2a611aaed_31bf3856ad364e35_6.1.7601.22578_none_557a7d2c40092ee8.manifest
File versionNot Applicable
File size717
Date (UTC)22-Jan-2014
Time (UTC)07:30
PlatformNot Applicable
File nameX86_microsoft-windows-l..istry-support-tcpip_31bf3856ad364e35_6.1.7601.22578_none_887145af7cf9dcdd.manifest
File versionNot Applicable
File size7,032
Date (UTC)22-Jan-2014
Time (UTC)03:59
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 7 and Windows Server 2008 R2
File nameAmd64_1d4841569d620fb77227bc12b0cf4079_31bf3856ad364e35_6.1.7601.22578_none_10bac8b1104a6cb4.manifest
File versionNot Applicable
File size721
Date (UTC)22-Jan-2014
Time (UTC)07:30
PlatformNot Applicable
File nameAmd64_microsoft-windows-l..istry-support-tcpip_31bf3856ad364e35_6.1.7601.22578_none_e48fe13335574e13.manifest
File versionNot Applicable
File size7,034
Date (UTC)22-Jan-2014
Time (UTC)03:10
PlatformNot Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_5146917b1a288dcb27d6dba6069e4638_31bf3856ad364e35_6.1.7601.22578_none_74f71512cada7843.manifest
File versionNot Applicable
File size719
Date (UTC)22-Jan-2014
Time (UTC)07:30
PlatformNot Applicable
File nameIa64_microsoft-windows-l..istry-support-tcpip_31bf3856ad364e35_6.1.7601.22578_none_8872e9a57cf7e5d9.manifest
File versionNot Applicable
File size7,033
Date (UTC)22-Jan-2014
Time (UTC)02:35
PlatformNot Applicable

↑ 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


References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2923884
Revision : 1
Created on : 1/7/2017
Published on : 4/8/2014
Exists online : False
Views : 259