搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

exploit-winamp.pls.b.gen keeps appearing in my Firefox profiles file

  • 1 个回答
  • 2 人有此问题
  • 1 次查看
  • 最后回复者为 John99

more options

This is becoming a disabling issue. I may have to uninstall Firefox permanently because it only occurs when Firefox is installed. McAfee finds it and supposedly kills it after a re-boot, but it rebuilds itself. I can look at the file and delete it only to watch it return immediately. None of the other Malware killers I have tried even find the file. It is a very old Trojan that exploited a 2006 version of Winamp (which was never installed on this machine). I am at wits end, but I can't tolerate a forced re-boot every hour or so. If anyone has had any success with this I would be grateful. BTW - Lenovo Laptop, Windows, 8.1, not a problem on my desktop on the same network. Several other folks reported this problem but nobody stated that their repair actions were successful. Thanks.

This is becoming a disabling issue. I may have to uninstall Firefox permanently because it only occurs when Firefox is installed. McAfee finds it and supposedly kills it after a re-boot, but it rebuilds itself. I can look at the file and delete it only to watch it return immediately. None of the other Malware killers I have tried even find the file. It is a very old Trojan that exploited a 2006 version of Winamp (which was never installed on this machine). I am at wits end, but I can't tolerate a forced re-boot every hour or so. If anyone has had any success with this I would be grateful. BTW - Lenovo Laptop, Windows, 8.1, not a problem on my desktop on the same network. Several other folks reported this problem but nobody stated that their repair actions were successful. Thanks.

所有回复 (1)

more options

if you have paid for McAfee software and that detects but fails to properly remove the problem than why not contact McAfee for assistance. They appear to be already aware of this

Someone else reported a similar problem on this forum and apparently resolved the issue using standard advice: