June 5, 2004
How to determine and recover from Winsock2 corruption
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMSWhen you try to release and renew the IP address using the Ipconfig program, you may receive the following error message:
An error occurred while renewing interface 'Internet': An operation was attempted on something that is not a socket.When you start Internet Explorer, you may receive the following error message:
The page cannot be displayedWhen you use your computer, you may receive the following error message:
Initialization function INITHELPERDLL in IPMONTR.DLL failed to start with error code 10107Additionally, you may have no IP address or no Automatic Private IP Addressing (APIPA) address, and you may be receiving IP packets but not sending them.
CAUSEThese issues may occur if the Winsock registry keys are damaged or corrupted.
RESOLUTIONWARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
How to determine whether the Winsock2 key is corruptedTo determine if the symptoms are caused by a problem with the Winsock2 key, use one of the following methods.
Method 1: Use the Netdiag toolTo use the Netdiag tool, you must install the Microsoft Windows XP Support Tools. To do so, follow these steps:
Note If you already have Support Tools installed, go to the second procedure in this section.
Note If you do not have Support Tools installed and you do not have the Windows XP Setup CD, go to Method 2.
Method 2: Use the Msinfo32 programNote Use this method only if you do not have a Windows XP Setup CD and you do not have Support Tools installed.
If you have a third-party add-on installed, the name of the add-on will replace the letters "MSAFD" in the list.
If there are more than ten sections in the list, you have third-party additions installed.
If there are fewer than ten sections, there is information missing.
Note These entries represent an installation with only the TCP/IP protocol installed. You can have a working Winsock and see additional entries if another protocol is installed. For example, if you install NWLink IPX/SPX, you will see 7 additional sections, for a total of 17. Below is an example heading of one of the new sections:
MSAFD nwlnkipx [IPX]Also, each of the new sections that are created by installing NWLink IPX/SPX start with "MSAFD." Therefore, there are still only two sections that do not start with those letters.
If the Netdiag test fails, or if you determined that there is Winsock corruption by looking at Msinfo32, you must repair the Winsock2 key by using the steps in the next section.
How to Recover from Winsock2 corruptionTo resolve this issue, delete the corrupted registry keys, and then reinstall of the TCP/IP protocol.
Step 1: Delete the corrupted registry keys
Step 2: Install TCP/IP
The information in this article applies to:
If you have any questions or problems, please feel free to contact me by Email or by phone.
© Davis M McCarn 2004 All Rights Reserved