Spybot 1.6.2 update and Runtime Error 216

Buster said:
@ NotGeordie Thanks for reporting so quickly. Lets try something else. Please turn off all file sets but the usage tracks.
Click to expand...

Ok, I did that Buster. The Error reports (both "The instruction at; etc." and the "Runtime error 216") did not come up.

My usage tracks were revealed, I shut down - no error reports.

Hmmmm.
 
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 the recent updates also covered that part.

I really can`t believe the errors are due to malware. The pop-ups are generated because process SpybotSD.exe cannot be shut down. So it looks like a bug in the program to me.
 
@ NotGoerdie
Ok, so lets see if this also happens using the old advcheck linked in my last post.

@ Ras1974
If you are experiencing the same as NotGoerdie, please try the old advcheck.dll linked above.
 
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.
 
Buster said:
Another possible reason may be the new advcheck.dll, which has been released last week. Hence we would like you to install the old advcheck.dll, which can be found here. Please download the zip file, unzip and start the included .exe file. Thanks!
Click to expand...

Well, I tried that, but unfortunately, we're not there yet. The same errors came up after running Spybot. I did move the advcheck163.exe and advcheck163.zip into a temp file before executing the .exe you suggested. Should I place them back into their original folder, or is it more complex than that?

Of note, after executing the old .exe from the zip file you recommended there was NO advcheck.exe or advcheck.zip in my Program Files\Spybot-Search & Destroy\Updates folder, which is where the '163' versions did reside. Perhaps the instal didn't work and I should try again? Or is this what you expected to see?

I'll place the '162' versions in there manually, run again and see what happens, just for the heck of it.
 
Last edited:
@ NotGeordie
Sorry, I should have mentioned to end Spybot and Teatimer prior to this. Usually the advcheck.dll should be replaced by this installer. Did you enter the correct program path in the wizzard? The new old advcheck (1.62) should be placed at your Spybot - Search & Destroy program directory, most often "%programfiles%\Spybot - Search & Destroy\advcheck.dll"

@ Ras1974
Thanks, I'll keep waiting for your results. ;-)
 
Buster said:
@ NotGeordie
Sorry, I should have mentioned to end Spybot and Teatimer prior to this. Usually the advcheck.dll should be replaced by this installer. Did you enter the correct program path in the wizzard? The new old advcheck (1.62) should be placed at your Spybot - Search & Destroy program directory, most often "%programfiles%\Spybot - Search & Destroy\advcheck.dll"
Click to expand...

OK, my last attempt, previous post didn't work. I'll undo what I've done, shut down TeaTimer/Spybot and try again. I'll get back to you after I walk the dog (his priority, not mine!).
 
Sorry Buster, no luck. I turned off Teatimer, closed S&D, ran the 1.6.2 advcheck.exe, then a scan. Same error.

I rebooted, ran again. Same error.

I disconnected from the net, turned off My NIS 2009, ran the .exe again, scanned. Same error.

Of note, perhaps, even after running the 1.6.2 advcheck.exe I noticed that the advcheck.dll in my S & D folder reads version 1.6.3.17, created 25/07/2008.

I don't know.

Can you tell me how to restore things back to the way they were? Or, I have a few minutes if you want me to try something else.
 
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 the scan again, wish i was home so that i could also try :sad:
 
Don't know about that RAS.

Got to go to hospital (really, this is giving me the plotz).

I'll check back in about 6-7 hours.
 
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.
 
You can download the latest advcheck.dll here. The date is correct. The file has been created that day, zipped and now "copied" on your system, no need to worry.
Got to go to hospital
Click to expand...
Hope everything is fine under given circumstances.
 
Sorry for my lack of communication in this thread so far! I admit, given some of the odd things I was seeing, my paranoia exceeded my patience. I reformatted my computer, and installed the Win7 7100 RC yesterday. It's been a slow process of getting the machine back together, but I plan to install Spybot S&D and run a test as soon as I have the time.

I figure if I see the same errors on a freshly installed machine running a new x64 OS, then it's safe to say it's not malware.
 
I tried only scanning on the usage tracks as suggested and received no errors upon shut down of Spybot. I unzipped the advcheck162 file in the updates directory and ran the .exe file from there. Afterwards, I ran a complete scan. Upon exiting Spybot, I received the familiar errors. I reinstalled the advcheck163 file the same way, and ran another complete scan. Upon shut down, once again I received the errors.

Has anyone uninstalled Spybot completely, reinstalled, and seen the error again?
 
Terminal man, I did the complete uninstall and reinstall. Still got the 216 error when I exited after the first scan with the new program.
 
I have been unable to reproduce the error on the machine after reformatting and installing Windows 7 RC 7100. I'm running pretty much everything I was under XP, only I've migrated over to NOD32 v4. Since it seemed to be a sporadic issue, I'll certainly report back here if I see it happen again.

Also, kudos to the spybot team again. Not only does Spybot work wonderfully in Win7 (Horray for immunizations on Opera), but your feedback and service here are excellent.
 
Okay, thanks all you for your tests so far.:bigthumb: Looks like this is caused by one of our sbi files. To find out which one is causing this error, please select one by one and run a scan after each selection. Looks like we are getting closer to to find the origin of this Error 216.
 
You must log in or register to reply here.
Back
Top