CWShredder v2.18- Finding CWS.Qttasks 'False Positive'??

I saw that particular write-up when I started researching this particular detection. None of the listed problems are present on this machine..There's no such registry entry nor is there a "qttasks.exe" file on the computer.

I'm still unsure why it's being detected other than the possiblity of the new version of Quicktime.

Strange indeed.

Grif

...Repeated scans with 2.18 this morning continue to show the false positive..A scan with the 2.16 version turns up nothing...As I posted to Marianna above, there are no such registry entries on this machine..Likewise, there are no symptoms and there is no "Qttasks.exe" file on the machine either..

Clearly, it's not the "real" thing but I'm just curious about what's being detected?

Thanks.

Grif

was added to the new version according to Bubba at Wilders.
There are [5] new variants supported in this version. The new variants include:

1. CWS.SnugWeb
2. CWS.CoolSearchA
3. CWS.EZSearch
4. CWS.CraftSearch
5. CWS.FindOnline

It's the 2nd post on this link which is the updates forum at Wilders.
http://www.wilderssecurity.com/showthread.php?t=103793

For what it's worth. I got NO false positives but I also have NO version of Quicktime.

it doesn't show to us the registry that it detects or fixed. It simply say there is a detection

I have received same reports from other users who have QuickTime. Some of them allow CWShredder to fixed it and find no problem in using QuickTime then they run another scan, it detects no more. This means CWShredder 2.18 definitely "fixed" what if find because the 2nd scan find no more CWS.Qttasks infection.

If CWShredder will only show what triggers it

..because I always run the basic "Scan Only" option first. I don't want it to fix something that's not broken.

Grif

I scan only and if it find any, I try to lookup using other tools for any suspicious or unwanted entries in areas where the said "find" may appear.

I've been getting CWS.Look2Me and CWS.MSConfig false positives in earlier versions of CWShredder during ast scan only (not fixing it). The next scan, no more detection.

With this new version, I'm still getting CWS.MSConfig on first scan again then the next scan finds nothing.

I let CWS fix the problem and it went away. I have a basic freebie version of Quick Time.

and not qttasks.exe?

...for the Quicktime programs start up..If you UNCHECK the Quicktime startup option in "msconfig", then restart the computer, the registry entry is removed from the "Run" location in the registry...As a result, CWShredder 2.18 does not detect CWS.Qttasks.exe. AFter you once again run Quicktime or re-enable the start up in "msconfig", then the registry entry appears and is detected.

In addition, if you let CWShredder "fix" the problem, the registry entry is removed but as mentioned above, the next time you run Quicktime, the registry entry will be recreated..Therefore, running CWShredder after running Quicktime, will always come up with a hit for CWS.Qttasks.

Clearly, this is a bug in the program since it should be looking for the "Qttasks.exe" file NOT the "Qttask.exe" file.

Hope this helps.

Grif

I decided to ''play'' a little. Shredder did not pick up CWS.Qttasks at first. I originally had qttask disabled at start up, since I hardly use Quicktime. Because I had similar issues with Shredder and CWS.Msconfig, I decided to enable it at start up and see if Shredder would recognize it as the CWS variant. And it did. (I may have done it in reverse of what you posted, but I think the conclusion is the same.) I ''think'' what Shredder finds as CWS.Msconfig is based on the same premise. You would know that better than I.

I deleted one false positive in my short computing experience.. and hope to NEVER let it happen again. I'll be doing some heavy soul-searching before I delete anything again...

Carol