Search:

McAfee sometimes loses it`s mind i suppose. yesterday i also got an old version of Ccleaner (227) flagged by McAfee, crazy. McAfee should straiten this kind of mess out. Not much Spybot SD can do...

I renamed the old dll and updated via the regular way on my girlfriends laptop. To avoid confusion it is best to just rename the old dll and use the spybotsd_advcheck-1.6.4.18.exe.

Too cool for school, the team fixed it! Thankssss!

My test scenario:

1. Updated via the usual way. A pop-up appeard stating that the advcheck.dll was read only. There was a retry button to (try...

Thanks but i meant a reply from a Member of Team Spybot when the issue is fixed.

Are you gonna post a reply when it is fixed? Can`t wait! Thanks in advance!

Of course the errors are irritating but they come up after you`ve already done everything you wanted to do with SpybotSD. So there is no loss in functionality because of this errors. Because the...

My test scenario:

1. Booted up the p.c..
2. Started SpybotSD and ran a complete scan.
3. Closed the program and the 2 error pop-ups appeared.

Firefox was not started at all prior to or during...

I did not meant it like that NotGeordie. I am just curious if the SpybotSD team itself is trying to reproduce this error on their own machines. Or if they encountered this error themselves on (one...

is the SpybotSD team itself testing to fix this issue? are you guys able to reproduce this error?

the advcheck.dll solution did not work for me, but thanks though buster.

your service is great buster, can`t wait to get home :thanks:

Never heard of that expression before NotGeordie, but i can imagine how you feel, i`ll give it a go tonight. Just check back later on. Don`t worry, you`ll see, just a bug and no malware.

NotGeordie, should the .dll not have today as created date? What if you rename the current .dll and then again run the .exe to get the new .dll in the SpybotSD program file directory. After that run...

:funny:

Thanks for your super quick reply buster, i will try that tonight @home. I`m at work now. I will post my results tonight in this thread.

I still think it has to do with the recent updates concerning the last part of the scan. I also believe the very last part of the scan includes scanning the downloading directories. I don`t know if...

i guess some part of the definitions of late causes something in the program / process to lock(?) when closing down resulting in a crash. i guess all updates are exactly the same from the different...

same error pop-ups here, i guess the newest definitions are checked last in the scan and in my case more than 566000 items are checked during the scan. when i abort the scan at say 545000 checked...