I ended up uninstalling Alchohol trial version today but same alert is coming everytime I re-start the computer… now what? this is really anoying! I asked Avast to delete the file but every time I re-start the computer it comes back.
False positive with certainty, and so searched the forum Daemon T. this file
is used to secure the registration of the program, and also connected to this virtual drive.
I’ll stick with the option to ignore until the next update…
If it is a real Trojan why Avast doesn’t do anything about it, I have deleted the file and made 4 boot scans according Avast recomendations but still there.
Mbmam does not detect it, Superantispyware is not detecting it either.
Please let me know the real way to get rid of this thing that it is really anoying me…rm
Which was a bit of a pointless exercise as this is the anti-rootkit scan that is flagging this, something which can’t be run from VT. So I wouldn’t expect it to find anything and that is the same reason why the standard scans of avast don’t detect anything.
What is considered suspicious I don’t completely know, but most certainly it must be a hidden process/driver, why it needs to be run hidden is beyond me.
As for why after asking avast to delete it and it coming back, well I don’t know if avast is only removing the hidden driver and not the actual file from the system32\drivers folder. So there is some program which uses this driver and is reloading it. Finding what that might be is going to be the hard part.
I don’t have the sptd.sys file on my XP Pro SP3 system, is your alert on the XP or win7 system ?
The alert is only in Windows 7 for the moment, in that computer I installed Alchohol 3 days ago, Now as I said I uninstalled it but the alert is still driving me crazy…rm
Let’s wait an answer for Avast tomorrow, I will ignore the alert and will ask my friends in the forum in Spanish (forospyware) to wait, since there are several threads there waiting for an answer on this…rm
Avast has released 2 updates and the problem still here with 110601-1… and I still don’t know if it is a FP or is it a real virus? anyone from Avast to answer the question and what is being done?
You need to be cautious I have just cleaned a system with an infected sptd.sys that was masking a TDL4 bootkit. aswMBR was the only programme that flagged it. After I removed the file I was then able to cure the TDL4. So it might be worth while checking it with aswMBR
Hi guys; I’ve had the same problem and solved it by uninstalling Daemon tools (i didn’t almost use it) and then deleting the sptd.sys file, since this one didn’t dissapear after the uninstallation.
Do you know if Avast is already aware of this problem…?
I got tired of waiting, the two new update did not work, so I decided to uninstall the SPTD driver normally my system (do not delete the Avast does not exclude manually, does not exclude Daemon tools) excludes only the driver for your uninstaller.
After it rebooted my system and voila, I was no longer with the driver but with this action the program Daemon T. would not work more then I discovered that searching the Daemon T. provides a driver similar to SPTD.SYS authored DTSOFTBUS01.SYS own driver who once again did not run the Daemon and not found the driver SPTD.SYS, it offers the driver DTSOFTBUS01.SYS.
Then there is tip for those who want to solve your problem without uninstalling the program Daemon.