nogard0
Aug 10 2009, 12:10 AM
i keep getting autocheck lsdelete appending evrytime i have items adaware finds something.
first time it is
autocheck lsdelete
then
autocheck lsdelete / autocheck lsdelete
autocheck lsdelete / autocheck lsdelete / autocheck lsdelete
autocheck lsdelete / autocheck lsdelete / autocheck lsdelete / autocheck lsdelete
autocheck lsdelete / autocheck lsdelete / autocheck lsdelete / autocheck lsdelete / autocheck lsdelete (garbage like characters.)
i think when i start up system used to say lsdelete.exe not found
so i copied it to system, windows, and c:
what is lsdelete and why does it insist on getting appended?
spybot s&d finds this appending.
visitor
Aug 10 2009, 06:41 AM
FYI, I have lsdelete.exe in 3 locations on XP:
C:\Windows\system32
C:\Program Files\Lavasoft\Ad-Aware
C:\Documents and Settings\All Users\Application Data\Lavasoft\Ad-Aware\Update
Spybot is probably just noting that the file is being accessed when Ad-aware calls for it. When Spybot loads, it has a warning about incompatibility with Ad-aware - both have real-time protection, and it's recommended that you only have 1 real-time protection program running. Try turning off one of them:
Ad-aware: Settings - AdWatch Live! - General, uncheck all modules
Spybot: Advanced Mode - Tools - Resident, uncheck SDHelper and TeaTimer
The other thing you can try - when Spybot's TeaTimer gives you the popup message, click to allow and remember your decsion. Doing that should stop the messages, but there will still be a conflict in the background as long as both are running real-time.
srou
Aug 18 2009, 04:09 PM
I just upgraded from Adaware personal to Anniversary edition (freeware) on my XP machine. Spybot is also on this machine, and it gave me a warning: BootExecute entry, changed from: autocheck autochk *\ to: autocheck autochk *\lsdelete\. I denied the change. Adaware seems to work. Was this the correct response to Spybot's question?
GoddersUK
Aug 18 2009, 08:18 PM
I'm confused about what exactly is going one here?
Spybot S&D TeaTimer is picking up these attempted registery changes by Ad-Aware? (note: You should be aware of possible incompatibilities between AAW and Spybot's Tea Timer feature.)
If so you should allow them - otherwise proper cleaning of malware may not take place. If this is producing errors post back here and we will be able to help you further.
Thanks, GoddersUK
visitor
Aug 18 2009, 08:23 PM
QUOTE(srou @ Aug 18 2009, 08:09 AM)

I just upgraded from Adaware personal to Anniversary edition (freeware) on my XP machine. Spybot is also on this machine, and it gave me a warning: BootExecute entry, changed from: autocheck autochk *\ to: autocheck autochk *\lsdelete\. I denied the change. Adaware seems to work. Was this the correct response to Spybot's question?
Can't really answer your question since I'm not sure what lsdelete.exe does for Ad-aware. Generally, you should allow trusted processes. It's up to you if you want to change Spybot from block to allow - now or later if you encounter problems. As long as I know it's something I installed, I usually accept changes. Regardless, I still recommend running only 1 real-time protection as described above.
casey_boy
Aug 18 2009, 09:24 PM
FYI lsdelete is the tool which deletes infections on system reboot if they could not be removed after a scan.
visitor
Aug 18 2009, 10:44 PM
Thanks Casey, I had a feeling that's what it was for, but wasn't sure. That must be the exe which writes to the aaw7boot.log which LS_Laleh said couldn't be changed since it's related to delete-on-reboot.
srou, in light of GoddersUK and Casey's input, you should definitely remove the Spybot block.
srou
Aug 19 2009, 02:53 PM
Thanks, guys, that answers my question.....
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.