Article ID: 892350 - Last Review: October 12, 2006 - Revision: 4.1

After you run Microsoft Windows AntiSpyware (Beta), you have network-related problems, or you receive an error message

View products that this article applies to.
Beta Information
This article discusses a Beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this Beta product. For information about how to obtain support for a Beta release, see the documentation that is included with the Beta product files, or check the Web location where you downloaded the release.

On This Page

Expand all | Collapse all

SYMPTOMS

After you run Microsoft Windows AntiSpyware (Beta), you may receive one or more of the following interactive error messages:
  • Error message 1
    Could not start the Windows Firewall/Internet Connection Sharing (ICS) service on Local Computer. Error 10047: An address incompatible with the requested protocol was used.

    Error message 2
    Windows Firewall settings cannot be displayed because the associated service is not running. Do you want to start the Windows Firewall/Internet Connection Sharing (ICS) service?
  • Error message 3
    This application has failed to start because SPORDER.dll was not found.
  • Third-party networking products may not function correctly.
  • Computers may not be able to connect to the network because they cannot obtain an IP address.
  • You may receive the following error message when you are using Microsoft Internet Explorer:
    Error 404: Page cannot be displayed.
Back to the top

CAUSE

There are known spyware programs that install layered service providers (LSPs) on client computers to gather user data. When Windows AntiSpyware (Beta) removes spyware programs, it also removes the spyware-based LSPs. However, Windows AntiSpyware (Beta) does not restore any LSPs after it removes the spyware.
Back to the top

RESOLUTION

Windows XP SP2

To resolve this problem if you are running Microsoft Windows XP Service Pack 2 (SP2), follow these steps:
  1. Rebuild the Winsock LSP chain. To do this, follow these steps:
    1. Log on to the Microsoft Windows XP workstation as an administrator.
    2. Click Start, click Run, type cmd, and then click OK.
    3. At the command prompt, type the following, and then press ENTER:
      netsh Winsock reset
      When the program is finished, you will receive the following message:
      Successfully reset the Winsock Catalog. You must restart the machine in order to complete the reset.
      If you receive this message, go to step 1d.

      If you are not logged in as an administrator, you will receive the following error message:
      Unable to reset the Winsock Catalog. Access is denied.
      If you receive this message, log off the computer, and then log back on by using an account with Administrator access. Typically, the first user account that was created has Administrator access. Then, repeat steps 1b and 1c.
    4. Restart your computer.
  2. Test each of your third-party programs that are known to use LSPs.
  3. Reinstall any malfunctioning third-party programs that are known to use LSPs.
Back to the top

Windows XP, Windows XP SP1, and Windows 2000

To resolve this problem if you are running the release version of Microsoft Windows XP, Microsoft Windows XP Service Pack 1 (SP1), or Microsoft Windows 2000, follow these steps:
  1. Rebuild the Winsock LSP chain. To do this, follow the steps in the "Resolution" section of the following Microsoft Knowledge Base article:
    817571  (http://support.microsoft.com/kb/817571/ ) You receive an "An operation was attempted on something that is not a socket" error message when you try to connect to a network
  2. Test each of your third-party programs that are known to use LSPs.
  3. Reinstall any malfunctioning third-party programs that are known to use LSPs.
Back to the top

MORE INFORMATION

The Winsock API lets Windows-based programs access transport protocols such as Transmission Control Protocol (TCP). An optional LSP can be inserted between Winsock and the underlying protocol stack if it is required by a program. Programs chain LSPs so that all programs that need access to the network can access it.
Back to the top
APPLIES TO
  • Microsoft Windows AntiSpyware (Beta)
Back to the top
Keywords: 
kbdefenderrtwswept kbdefenderrtwno kbtshoot kbprb KB892350
Back to the top
 

Get Help Now

Contact a support professional by E-mail, Online, or Phone

Article Translations