חיפוש בתמיכה

יש להימנע מהונאות תמיכה. לעולם לא נבקש ממך להתקשר או לשלוח הודעת טקסט למספר טלפון או לשתף מידע אישי. נא לדווח על כל פעילות חשודה באמצעות באפשרות ״דיווח על שימוש לרעה״.

מידע נוסף

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

  • 1 תגובה
  • 2 have this problem
  • 7 views
  • תגובה אחרונה מאת 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: