Jump to content

rvmlister

Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About rvmlister

  • Rank
    New Member
  1. No threats found by MBAM! Wonderful. Have downloaded Avira Free and am presently running that as well. Maybe I can take a big breath now, TwinHeadedEagle :-) Many, many thanks for your kind help. It looks like you've solved it! Do you happen to know what might have caused all this in the first place? Knowing this might help me avoid getting into this kind of trouble again... All best wishes, Ralph
  2. Bingo! Having run FixExec and re-booted, I ran the previously-downloaded MBAM installer, and still got the "corrupted" error message. So, not to be outdone, I then re-downloaded a fresh version of MBAM installer from the MB site, which overwrote the last download, and ran that. It then installed perfectly, and, as I write, I'm carrying out a full Threat Scan on the infected computer. It's scanning the files now, and will begin the heuristic phase of the scan in a short while, no doubt. So far, no infections logged. I will let you know what the scan finds, if anything, when it's finis
  3. I have now uninstalled all components of Avira using Control Panel, and have re-booted (twice). MBAM still says it's set-up file is corrupted, and mbam-cleaner still responds saying it is not a valid Win32 application. So removing Avira does not seem to help. Now I no longer have Avira OR MBAM on my infected unit!
  4. So, I re-started the infected PC, booting as per normal. I then downloaded a fresh version of MBAM (to re-install it after uninstalling a week ago, when the problem arose), and attempted to run it: same error message came back as before - the file is "corrupted". That seems strange. I then tried to run mbam-cleaner (which, admittedly, I had downloaded last week), and, as before, back came the message that this not "a valid Win32 application". Is there something I am missing? I can hardly believe the new MBAM setup would be "corrupted"...
  5. Here's the fixlog.txt in its entirety: Fix result of Farbar Recovery Tool (FRST written by Farbar) (x64) Version: 16-05-2015 02 Ran by SYSTEM at 2015-05-19 11:43:02 Run:1 Running from g:\ Boot Mode: Recovery ============================================== Content of fixlist: ***************** Startup: C:\Users\Ralph Lister\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\Dropbox.lnk [2015-05-05] ShortcutTarget: Dropbox.lnk -> (No File) S4 APNMCP; C:\Program Files (x86)\AskPartnerNetwork\Toolbar\apnmcp.exe [168400 2013-07-26] (APN LLC.) C:\Program Files (x86)\AskPartnerNetw
  6. Making some progress! Yes, this way I was able to run FRST - at last :-) Here's the log, copied and pasted in its entirety. Thanks for your ongoing help, TwinHeadedEagle - much appreciated. Ralph Scan result of Farbar Recovery Scan Tool (FRST) (x64) Version: 16-05-2015 02 Ran by SYSTEM on MININT-EKIF8NA on 18-05-2015 23:16:01 Running from g:\ Platform: Windows 7 Home Premium (X64) OS Language: English (United States) Internet Explorer Version 8 Boot Mode: Recovery The current controlset is ControlSet001 ATTENTION!:=====> If the system is bootable FRST must be run from normal or Sa
  7. Heya - I entered Safe mode and attempted to run FRST from there, but no luck, again, the same error message: not a Win32 application. So, no, I can't run FRST from Safe mode. Interestingly, I also tried to run the MBAM setup file (which I had downloaded earlier) while I was still in Safe mode, and the error message for that was that the file was "corrupted" and it couldn't run - not that it was "not a Win32 application", as per all the other error messages I've been getting. I got the MBAM installer from the MBAM site, so hardly likely that that file is corrupted?
  8. No, I did not. Good call. So, I temporarily deactivated Avira (umbrella down), then tried to run FRST again, and the same error message "FRST64.exe is not a valid Win 32 application" came up after I'd hit the Run button on the FRST launch, not allowing me to go further, the only option being to close out of trying to run it. So Avira off, same result. MBAM is now off my system (I have been unable to re-install it - same problem). Also, when I was re-installing Malwarebytes, I got the same error message... I would think that Avira would operate with MBAM without that kind iof message
  9. Hi there TwinHeadedEagle, Many, many thanks for your help. I tried this before, and I tried it again - always hopeful! I downloaded FRST (for my 64-bit OS), saved the .exe file, attempted to run it, and was blocked (again) by the same error message as before, namely, that "FRST64.exe is not a valid Win 32 application". I just can't seem to run any .exe files! All best wishes, Ralph
  10. Hi there, good MBAM folk :-) I am directed by one of the kind MBAM moderators to open a new thread after initially posting under the incorrect catregory. Here goes: Computer: PC, Windows 7 Home Premium, 64 bit. Malwarebytes Free, Avira Pro. Note: I have chosen NOT to install the Windows Updates - this may/may not be relevant. I first noticed there might be a problem when I was attempting to download regular definition Updates for Malwarebytes. The download could never quite complete - it froze up 3/4 of the way through. Same result after several attempts. I then uninstalled Mal
  11. Hi there, good MBAM folk :-) PC, Windows 7 Home Premium, 64 bit. I have chosen NOT to install the Windows Updates - this may/may not be relevant. Malwarebytes Free, Avira Pro. I first noticed there might be a problem when I was attempting to download regular definition Updates for Malwarebytes. The download could never quite complete - it froze up 3/4 of the way through. Same result after several attempts. I also noticed the internet was running very slowly (and normally it's pretty quick). Another change in behavior. I uninstalled Malwarebytes using Control Panel. I also downl
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.