winsock lsp

[perdika]

Hi there, I am new to this forum but hope someone can help me. Have been running Spybot for a couple of years with no problems. Today when I go into the programme, I get a message in German Uberschreitet das maximum 17 and then the page I get is Winsock LSP. When I try to run a check it dosen't happen. Please help if you can. Thank you

[PepiMK]

Do you use the German version of Spybot?
Because if not, that sounds more like you're using Spybot-S&D 1.2 or 1.3. Back then, system error messages were still in German, but since 1.4, they're english or localized.

And if it 1.3, did you use the manual updates?

[perdika]

thank you for quick response
no I don't use German version
this is the first time i have had this message today and it comes up every time I open spy bot and when i click OK it goes to this page with Winsock lsp

[perdika]

ps yes I did a manual update just before this came on - it is showing as an error

thank you

[PepiMK]

You missed the important question: are you using version 1.4 or something older?

I asked for manual updates since the 1.3 may not be able to download updates, so you would've installed 1.4 updates on version 1.3. Also, this bug with German error messages is 1.3 only...

So: which version are you using exactly? :)

[spybotsandra]

Hello,

To see which version number and/or updates of Spybot - Search & Destroy you are using please run Spybot-S&D and choose "Help" --> "About" in the menu bar.
There you can see which version you have and which updates are installed.
It should be version 1.4 and the updates from the 2006/12/08.

Best regards
Sandra
Team Spybot

[perdika]

thank you for your patience!

No details of version at all - just Spybot S & D and the registration details of the company at the bottom

[PepiMK]

Ok, here's some more version to identify the version. See where you have to click on the left, then notice
1. The icons
2. The version number
3. The year
Even if the version information is missing, the copyright year and/or icons should make the version clear :)

http://img299.imageshack.us/img299/8956/identifysbsd13lq2.png
http://img299.imageshack.us/img299/3851/identifysbsd14yp2.png

Btw: problem was reproducable with 1.3 here, not with 1.4. Reason found, will be fixed soon, though everyone using 1.3 should really update to 1.4!

[perdika]

Thank you again for very helpful info.

There is no version number but the dates at the bottom are 2000 to 2004

Would it be better for me to uninstall this and then download again do you think.

If so, where is the safest site to download from?

Many thanks

Dee Hickling

[oenophile]

dear pepiMK,
my problems with the program (starting yesterday) are identical to perdika's, and probably to many others'. i look forward to your response, especially leading us through the process to "update to 1.4", if that's what's required.
many thanks,

p.s. otherwise, yours is a fine & robust utility, and your patience admirable.

[oenophile]

ADDENDUM: after some further research through various threads in the last 20 minutes, it's clear that the solution to this particular problem is to uninstall spybot and then reinstall it, thereby securing the new version. i'm puzzled as to why one or another member of team spybot doesn't suggest that course directly, rather than have thread-readers reach only halfway to the solution by messing about with uncovering their current version numbers.

[md usa spybot fan]

oenophile:

Upgrading to Spybot-S&D 1.4 is not the only solution although probably the best. It also appears that downloading the updates again that may also resolve the problem using Spybot-S&D 1.3.

From the following post by PepiMK (http://forums.spybot.info/member.php?u=1) in "Listenindex uberschreitet das Maximum (17)" (http://forums.spybot.info/showthread.php?t=9599):
http://forums.spybot.info/showpost.php?p=57174&postcount=5

Update: Updates have been replaced with a version that should run under Spybot-S&D 1.3 without this problem. Still, I'll repeat that we urgently recommend upgrading :)

[oenophile]

i uninstalled v1.3 and installed the new v1.4
not at all difficult, and i'm back on track.
thanks, all.

[oenophile]

thanks for your additional input, md~man.
i notice that you and the other members of the team have been working overtime in the last few days and weeks addressing this specific problem. why not just consolidate all of the queries into one single thread? i know from my own forum experiences that managing them is like herding cats, but the solution to this problem is so simple (and it's freeware, after all) that bringing the fix(es) into one thread seems like a smart efficiency.