Knowledge Base

How to determine and recover from Winsock2 corruption

Article ID: 811259

Article Last Modified on 10/26/2007

APPLIES TO

Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Microsoft Windows Server 2003, Enterprise Edition
Microsoft Windows XP Home Edition
Microsoft Windows XP Professional

Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

SYMPTOMS

When you try to release and renew the IP address by using the Ipconfig program (Ipconfig.exe), you may receive one of the following error messages.
Message 1

An error occurred while renewing interface 'Internet': An operation was attempted on something that is not a socket.

Message 2

An error occurred while renewing interface Local Area Connection: the requested service provider could not be loaded or initialized.

When you start Internet Explorer, you may receive the following error message:

The page cannot be displayed

When you use your computer, you may receive the following error message:

Initialization function INITHELPERDLL in IPMONTR.DLL failed to start with error code 10107

Additionally, 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.

When you use the ipconfig /renew command, you may receive the following error messages.

Message 1

An error occurred while renewing interface local area connection: an operation was attempted on something that is not a socket. Unable to contact driver Error code 2.

Message 2

The operation failed since no adapter is in the state permissible for this operation.

Message 3

The attempted operation is not supported for the type of object referenced.

In Device Manager, when you click Show Hidden Devices, the TCP/IP Protocol Driver is listed as disabled under Non-Plug and Play drivers, and you receive error code 24.

When you create a dial-up connection, you may receive the following error message:

Error 720: No PPP Control Protocols Configured

CAUSE

These issues may occur if the Winsock registry keys are damaged or corrupted.

RESOLUTION

ACW

Guided Help to determine and recover from Winsock2 corruption

Guided Help is available to determine whether the Winsock2 key is corrupted and to recover from Winsock corruption. Guided Help can automatically perform the steps for you.

The actions that this Guided Help performs can be undone after Guided Help is finished. To undo this Guided Help, run Guided Help again. On the Welcome page, click Undo this Guided Help, and then follow the instructions.

For more information about Guided Help, click the following article number to view the article in the Microsoft Knowledge Base:

915092 Description of Guided Help for Microsoft Knowledge Base articles

Requirements to install and to use this Guided Help

You must be logged on to Windows by using a computer administrator account to install and to use this Guided Help.
You must be running Windows XP Home Edition, Windows XP Professional, Windows XP Media Center Edition, or Windows XP Tablet PC Edition to install and to use this Guided Help.

You must first download Guided Help. To start, click the following link. Download Guided Help

Manual steps to determine whether the Winsock2 key is corrupted

To determine if the symptoms are caused by a problem with the Winsock2 key, use one of the following methods.

Method 1: Use the Netdiag tool

To use the Netdiag tool, you must install the Microsoft Windows XP Support Tools. To do so, follow these steps.

Notes

If you already have Support Tools installed, go to the second procedure in this section.
If you do not have Support Tools installed and you do not have the Windows XP Setup CD, go to Method 2.

Insert your Windows XP Setup CD, and then locate the Support\Tools folder.
Double-click the Setup.exe file.
Follow the steps on the screen until you reach the Select An Installation Type screen.
On the Select An Installation Type screen, click Complete, and then click Next.

When the installation is complete, follow these steps:

Click Start, click Run, type Command, and then click OK.
Type netdiag /test:winsock, and then press ENTER.

The Netdiag tool will return the test results for several network components, including the Winsock. For more details about the test, use /v at the end of the netdiag command: netdiag /test:winsock /v

Method 2: Use the Msinfo32 program

Note Use this method only if you do not have a Windows XP Setup CD and you do not have Support Tools installed.

Click Start, click Run, type Msinfo32, and then click OK.
Expand Components, expand Network, and then click Protocol.
You will have ten sections under Protocol. The section headings will include the following names if the Winsock2 key is undamaged:
- MSAFD Tcpip [TCP/IP]
- MSAFD Tcpip [UDP/IP]
- RSVP UDP Service Provider
- RSVP TCP Service Provider
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
If the names are anything different from those in this list, the Winsock2 key is corrupted, or you have a third-party add-on, such as proxy software, 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.

Manual steps to recover from Winsock2 corruption

Windows XP with Service Pack 2 instructions

To repair Winsock if you have Windows XP Service Pack 2 (SP2) installed, type netsh winsock reset at the command prompt, and then press ENTER.

Note Restart the computer after you run this command. Additionally, for computers that are running Windows XP SP2, there is a new netsh command that can rebuild the Winsock key. For more information, visit the following Web site:

http://technet.microsoft.com/en-us/library/bb457156.aspx

Warning Programs that access or monitor the Internet such as antivirus, firewall, or proxy clients may be negatively affected when you run the netsh winsock reset command. If you have a program that no longer functions correctly after you use this resolution, reinstall the program to restore functionality.

Note If these steps do not resolve the problem, follow the steps in the next section.

Windows XP without Service Pack 2 instructions

To repair Winsock if you do not have Windows XP SP2 installed, delete the corrupted registry keys, and then reinstall the TCP/IP protocol.

Step 1: Delete the corrupted registry keys

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

For more information about how to back up the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up, edit, and restore the registry in Windows XP and Windows Server 2003

Click Start, and then click Run.
In the Open box, type regedit, and then click OK.
In Registry Editor, locate the following keys, right-click each key, and then click Delete:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
When you are prompted to confirm the deletion, click Yes.

Note Restart the computer after you delete the Winsock keys. Doing so causes the Windows XP operating system to create new shell entries for those two keys. If you do not restart the computer after you delete the Winsock keys, the next step does not work correctly.

Step 2: Install TCP/IP

Right-click the network connection, and then click Properties.
Click Install.
Click Protocol, and then click Add.
Click Have Disk.
Type C:\Windows\inf, and then click OK.
On the list of available protocols, click Internet Protocol (TCP/IP), and then click OK.

If Internet Protocol (TCP/IP) does not appear, follow these steps:
1. Click Start, and then click Search.
2. In the Search Companion pane, click More advanced options.
3. Click to select the following three check boxes:
  - Search system folders
  - Search hidden files and folders
  - Search subfolders
4. In the All or part of the file name box, type nettcpip.inf, and then click Search.
5. In the results pane, right-click Nettcpip.inf, and then click Install.
Restart the computer.

Keywords: kbacw kbhowto kbacwsurvey kbnetwork kberrmsg kbprb KB811259

Microsoft KB Archive/811259

Contents