This is  not a standard known Error.

 

Try running adware /spyware & antivirus.

If issue persist , F8 (BOOT UP)-> Command Prompt -->scanreg

Choose a suitable date when system was running fine.

 

Dr. Mike

Hosenose,

Does the message actually contain WSCGetProviderPath, rather than the one you posted? That one exists in the Winsock 2 "Service Provider" programming interface. What was the exact error message?

Doctor D Mike's advice of running Ad-Aware and Spybot as described in this article is good, since I found at least one post indicating that malware can cause this symptom.

Since the error message refers to something that's part of Winsock 2, also try running lspfix, a Winsock 2 repair utility.

Jim

Rick,

Are you still having the problem? Did you try "lspfix"?

Jim

Never heard of it - - is it a windows system thing or a ISP thing???  s/Rick

Rick,

For information on lspfix, see this link. The name is lspfix, by the way. That stands for "Layered Service Provider" fix.

Jim

Message Edited by jimw on 04-10-2005 09:46 AM