Winsock 2 LSP Stack Registry Corruption

Windows Tutorials - Herong's Tutorial Examples

∟Winsock 2 LSP Stack Registry Corruption

This section describes how Winsock 2 LSP stack entries can be corrupted by incomplete application un-installations or spyware removal processes. Corrupted LSP stack entries can be restored or fixed by tools

Because the Winsock 2 LSP stack entries are maintained as Windows registry key values, they can be easily corrupted - stack entries exist but DLL files are missing. There are reasons for this corruption:

A new LSP entry was added and linked to a new LSP DLL file, when a networking application was installed. Later, when you uninstall the application, the un-installation process deleted the SLP DLL file, but failed to remove the related SLP stack entry in the registry.
A new LSP entry was added and linked to a new trojan LSP DLL file by a spyware. Later, an anti spyware tool detected and deleted the trojan DLL file, but failed to remove the related SLP stack entry in the registry.
An existing LSP entry was modified and linked to a new trojan LSP DLL file by a spyware. Later, an anti spyware tool detected and deleted the trojan DLL file, but failed to relink the SLP stack entry to correct LSP DLL file.

If LSP entries are corrupted, Internet applications will not work any more. You need to fix them by a tool or repair them manually.

On a Windows XP system, you can use the netsh command to reset all LSP stack entries back to Windows default values. Here is the netsh command syntax, but I have never used before: