Suddenly, a "wsock.dll" error causing havoc

I booted up and tried to run Nortons Security Suite and got constant errors: C\windows\system32\wsock.dll is either not designed to run on windows or it contains an error.

I cannot get nortons to work or open office. Both freeze with that error.

Upgraded to lasted nortons and scanned the entire computer--all good.
ran malware-anti-malware, all good.

I have done nothing to this wsock thing. Is this related to wireless at all? I once installed an ATT wireless thing to work in the field--worked fine, and not used since, but the ATT icon does load every time. I cannot think of anything esle

WSOCK.DLL is part of the "windows sockets emulator" (winsock) - one of several ways for apps to interface with the network stack and thus send and receive data over the network. Winsock is the network access method of choice for apps like browsers and mail clients, FTP, instant messenger...

I'm not actually sure that the error text you're seeing comes from Windows itself. Is this a popup window showing you the error? Can you paste a screenshot of it?

It doesn't really make any difference I suppose. Winsock is an attack vector for malware, so anti-virus apps frequently insert their own Winsock "filter" drivers (called LSPs) to try to counter the threat. I'd guess that either Norton caused something in Winsock to break, or Winsock is already broken and Norton is just detecting the issue.

Try running this from an elevated CMD prompt (run CMD as admin):

NETSH WINSOCK RESET

It says it's a windows error, and the MSKB lists it, but alas, they don't provide much of a fix. I know it's not the file itself because it has the same size, date, and properties as the same file on my backup drive. I replaced it anyway, no help.

I will try that reset--thanks

Oddly enough, I googled this and found about 20 free apps that claim to fix dll errors. I tried about 5 of them but they all came back and said they don't work on 64 bit

Personally, I'd suggest staying away from automated "optimisers" and "fixers" as if they're the plague - because many of them actually are.

If the winsock reset doesn't help, it would be useful if you could upload the text file that's generated in your temp folder as a result of this:

NETSH WINSOCK SHOW CATALOG >%temp%\winsockcat.txt

Many thanks, I will print and save your ~rec for the "next time" But I got lucky, and recalled my XP days.

"What would I do if this was my XP Pro machine?"

Run sfc /scannow [as admin]

Darned if it didn't FIX it!

Admin, close this ticket and thanks!

So the DLL itself literally got corrupted somehow. Interesting.

Glad to hear its working now.

H2SO4 said:

So the DLL itself literally got corrupted somehow. Interesting.

Glad to hear its working now.

Click to expand...

I don't think so. I replaced the dll file with one from my pristine backup. No help.

The sfc log showed a great many registry errors, not pointing to wsock32.dll, at least that was my impresssion trying to read it.

I was worried about using sfc because in XP, if there is a problem, you have to click to the source of the original file, most often the XP install CD, or winflat, if you stored it there.

I expected sfc to return with a command to click to the newer/better/original file, but no, it just fixed the registry string.