Jump to content

Chuck1

Honorary Members
  • Posts

    32
  • Joined

  • Last visited

Reputation

2 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yes, this update problem has reappeared on my XP SP3 PC as well. This periodic problem reappeared again early yesterday. I have latest legacy version Malwarebytes Premium version 3.5.1.2522 on the XP PC. Please look into the update issue again. Thank you.
  2. Hi TetonBob, It appears that the legacy version of Malwarebytes is not updating from yesterday's protection updates. The red triangle has reappeared like last time and it will not update again. I assume it's the same problem we saw early in September. Thanks for looking into this again. Chuck
  3. Updates now appear to be working. I updated to update package version 1.0.22583. Thanks again, TetonBob. Chuck
  4. My legacy malwarebytes program on a windows XP PC has the same update issue that started a day or two ago. I'm using version 3.5.1.2522, component package version 1.0.365, update package version 1.0.22556. It will not update beyond update package version 1.0.22556. I tried using the clean uninstall utility mb-clean-3.1.0.1035.exe to completely remove all malwarebytes components, then rebooted the PC, then re-installed Malwarebytes version 3.5.1.2522, reactivated the license, attempted to update, but it still did not update beyond update package version 1.0.22556. Can anyone confirm that they've officially ended update support for this legacy version of malwarebytes? If so, I'll need to cancel my subscription for this PC. Will a member of the Malwarebytes support staff please address this issue and provide an answer or a solution to the update problem? Thank you.
  5. Currently I've temporarily installed MBAM 2.2.1.1043 and MB Anti-Exploit 1.12.1.37 along with Avast free Antivirus. I've added MBAM and Anti-Exploit exclusions (exe and sys files) to the Avast exclusion settings to help avoid conflicts. No problems or errors at all so far. When I try installing MBAM 3.3.1.2183 or MBAM 3.4.4.2398-1.0.322 I get the usual error I've been seeing recently. The MBAM service (mbamservice.exe) runs in the background with no errors. I can stop (kill) the MBAM 3 service using process explorer so I assume that means it installs without self protection being activated by default. I wonder if there is another way to activate the self-protection module after installation of MBAM 3 without using the main program GUI. Chuck
  6. I also ran a memory test using a boot disk of Memtest86 to check for memory errors. I ran it for two passes of the various full tests and no errors were listed. Chuck
  7. No Joy. Got the small error window "Malwarebytes has encountered a problem and needs to close..." Information on error showed AppName: mbam.exe AppVer: 3.0.0.1395 ModName: qt5core.dll ModVer: 5.6.3.0 Offset: 001aa816 Further error details show: Exception Information Code 0xc0000005 Flags: 0x00000000 Then it lists details of 54 modules mbam.exe, ntdll.dll, kernel32.dll, QT5Quick.dll, USER32.dll, GDI32.dll, Qt5Gui.dll, ole32.dll.....
  8. Yes, I was thinking the same thing. I should now try the newest version. I think it's a long shot but I'll let you know how it goes. I'll have to upgrade from the earlier MBAM 2.2.1.1043 version which seems to run fine on my system. The MBAM 3.3 version also worked until very recently when the error that we're working on suddenly appeared.
  9. Exile 360, I've mailed you the process monitor zip file created while trying to launch MBAM 3 (latest beta) and getting the usual error. Thanks. Chuck
  10. Today I re-installed Malwarebytes version 2.2.1.1043 and it appears to be running fine using my current license in premium mode. The main program GUI appeared with no problems and it then updated the database. The system tray icon is also running. I ran a threat scan and no malware was found.
  11. I'm not able to run a scan using the regular Malwarebytes 3 program since I get the error when I try to launch it. I can't bring up the main GUI of Malwarebytes 3. I get the same error when I try to load the system tray (mbamtray.exe). Do you think it's worth collecting a process monitor log while trying to launch the Malwarebytes 3 program and then getting the error? Chuck
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.