Jump to content

eddyg

Members
  • Posts

    16
  • Joined

  • Last visited

Reputation

0 Neutral
  1. I scan weekly and this week had the same detection on two computers on different networks, one Win 7 and the other Win 10. From the properties info the files are NOT new, the one on the Win 10 computer was created/modified the same time I installed the OS in June 2016 . I did some searching on the net and the more intelligent sites corroborated my guess that these are non-malicious files put in the system during installation of the OS. Can a moderator please confirm that this is a false positive?
  2. Hi All, After updating the virus defs to v2013.02.15.04 and running my weekly scan all of my computers are showing dozens of exe files as being infected by Trojan.Backdoor.MRX. By chance on one computer I ran a scan yesterday with yesterday's database which showed 0 infections so I am guessing that there is an issue with the virus definition database. Please confirm that this is a false positive issue. Eddy Goldberg PS I am a l o n g t i m e user of Mabam; over the years I can count on the fingers of one hand the issues I have had. I have nothing but praise for the software and the people behind it.
  3. Indeed, after updating the virus definitions MB no longer flags the file _ISDel.exe in any way. Thanks for the quick fix!
  4. I also had MB flag this file, though on my computer it is in a different location (a deep sub-folder of "Norton Bootable Recovery Disk". File properities show it to be copyrigted by InstallShield and it has been on my computer for about 2 years. FP?
  5. Hi Maurice, The XP SP3 machines all have 1 gig of RAM and the only resident security software that runs is Norton: 2 computers have Norton Internet Security 2012 (recently updated from NIS 2011) and my laptop at work had Norton Endpoint Security which I think is the same AV engine in an enterprise package. Both programs have integrated firewalls and the settings have not been changed for quite a long time. Up till now I never had a problem with any version of mbam. I should point out that I also have 3 Win 7 machines running Norton Internet Security and none of them had problems with the automatic update to 1.60.0.1800. Maurice, you are certainly dedicated; I will raise a toast to you tomorrow night! Happy New Year! eddyg
  6. Hi Maurice, I think the Z-Alarm/Avast connection to the problems many XP SP3 machines are having is a red herring; I have 3 XP machines and 3 Win 7 machines, none of the XP machines have either Zone Alarm or Avast (all run NIS) but all 3 machines had problems with the 1.60.0.1800 update and none of the Win 7 machines did. I have gone over alot of the posts and IMHO there seems to be some kind of XP SP3 specific bug that affects many users; since the mbam-clean.exe uninstall and reinstall sequence seems to work for most (including me) my guess is is there is a problem with the uninstall routine written into the updater. I have been using Mabam as an additonal scanner for years and am both appreciative and respectful of your efforts in supporting freeware. I hope that you will not go Apple's way of stonewalling an obvious problem. eddyg
  7. FIXED! using the mbam-clean.exe sequence as suggested by Maurice. BTW, I had the same problem on another XP SP3 machine; I still think there is an XP SP3 specific bug in the uninstaller of the 1.60.0.1800 update. Thanks, eddyg
  8. Thanks, Maurice, I will run the sequence as you described later today.
  9. I also had a problem on an XP SP3 machine at work where I use Mabam only for occasional scanning: v1.51 ran perfectly but after the updater installed v 1.60.1800 the app crashed on startup everytime with a Windows error. Unlike the other posters, however, the only background app running is Norton Endpoint Protection which I doubt is causing the problem. Tried downloading the full app and installing over the updated version with no luck, then tried uninstalling and re-installing with the same result. Finally reverted my disk with Go-Back (once THE best a**-saving software for obsessive tinkerers, too bad Norton didn't upgrade it for Win 7) and am back with 1.51. Tomorrow I will try running Mabam-CLEAN file and then re-install and report back. BTW 1.60 running is fine on my Win 7 machine which leads me to suspect an issue with XP SP3.
  10. Me too...1.51 ran perfectly under XP SP3 but after the updater installed 1.60.1600 the app crashed every time and showed a Windows error. Tried downloading the full app and installing over the updated version with no luck, then tried uninstalling and re-installing with the same result. Finally reverted my disk with Go-Back (once THE best a**-saving software for obsessive tinkerers, too bad Norton didn't upgrade it for Win 7) and am back with 1.51. Unless someone knows a fix I think I guess I'll just have wait for the next upgrade and hope for the best. (BTW 1.60 running fine on my Win 7 machine).
  11. I had the same problem as Rox829 and Moeff, 1.51 ran perfectly under XP SP3 but after the updater installed 1.60.1600 the app crashed every time and showed a Windows error. Tried downloading the full app and installing over the updated version with no luck, then tried uninstalling and re-installing with the same result. Finally reverted my disk with Go-Back (once THE best a**-saving software for obsessive tinkerers, too bad Norton didn't upgrade it for Win 7) and am back with 1.51. Unless someone knows a fix I think I guess I'll just have wait for the next upgrade and hope for the best. (BTW 1.60 running fine on my Win 7 machine).
  12. EXEFIL~1.ZIP Hi Rich! As per your request attached are the 4 exe files that are getting tagged by malwarebytes as "trojan.agent". You have the scan report in my previous message. Once again, thanks in advance for all your help!
  13. Hi, I scan with Malwarebytes once a week, for the past couple of weeks I have been getting "infected" results for 4 exe files, all of them seem to be connected to a Thinstall installation of Word 2007 (probably a portable version). I don't even have Word 2007 on my computer but vaguely recall trying a portable version a long time ago, certainly not in the last year. I'm fairly sure the files have been on my computer for a long time and I never got any infected results for them so I think it may be a false positive. Attached is the log file, thanks in advance for you help! MBAM_L_1.ZIP
  14. Thanks for the quick response!
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.