Jump to content

alan_s

Honorary Members
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

1 Neutral

About alan_s

  • Rank
    New Member

Recent Profile Visitors

688 profile views
  1. To prepare for a reinstall I needed to document the settings. Fortunately I had created an image copy of the system immediately before doing the update. So, first a new image copy to be able to get back to the current state. Then I restored to the 'pre update' state where I could document the settings. That done, I thought "why not give it a new try - never know your luck?" So, I did the update again, And hey - it works! The UI launches OK! The only differences between Tuesday's update and today's are these: On Tuesday, I updated Firefox and Thunderbird just before updating Malwa
  2. Right, here is the grab-results file. mbst-grab-results.zip
  3. Yesterday, 2021-05-11, I updated Malwarebytes 4.3.0.98 to component package 1.0.1292 After the update, the Malwarebytes UI doesn't launch succesfully, neither via the notification area icon nor the desktop shoirtcut. Tried a few computer restarts ('proper' restarts – don't use fast startup ) , but it didn't help. Event Viewer shows the following: Environment is Windows 10, 20H2, 64-bit with Windows Updates of April 2021 Security programs are Malwarebytes and Defender Just had a thought: MBAMService.exe is certainly running, but could this problem affect Malwarebyt
  4. Sorry, but I wasn't trying to hijack his thread. And I wasn't seeking assistance for myself - perhaps the wording was misleading. My intent was simply to share a workaround I had discovered that might have been useful for him and for others.
  5. throkr: I too get the problem of mbam.exe not being started on re-boot (my system is Windows 7, 32 bit). In fact, it happens more often than not, and has been going on for months. In fact, I believe since version 2 arrived and it has 'survived' a number of clean removal / re-installs. I haven't reported it myself, partly as (not seeing any reports in the Forum before yours) I assumed it was peculiar to my installation and partly because I don't really expect much enthusiasm on the issue from Malwarebytes. Anyway throkr, two tips: First, try Settings -> Advanced Settings -> De
  6. I don't wish to hijack this thread but, yes bru - it rings a very loud bell! I too was running 2.1.8.1057 and noted the 'stuck blue bar' on October 15, but it probably started earlier. And I too noted that the product had been updated a couple of days earlier (and also read somewhere that the database had been optimized October 13) and drew my own conclusions. It's happened before... I did a little experiment: I had an image copy of my system from when it was working fine so, after saving the current state, restored to it. No difference - still got stuck. So it's not a question of prog
  7. The USB thing was just an attempt to provoke a case of 'failed scan' so I could see how it was handled, not for 'proper' use. For now, I'll see how things go using the settings I have had for the last year or so. If there's problem then I'll certainly take you up on your offer! Again, thanks for your help.
  8. Exactly! That's what I had expected. But it seems that the scheduler is not quite that clever. If the computer is not awake at the scheduled time, the scheduler doesn't make a new attempt when it's turned on. I did a couple of experiments today: At 08:30, I scheduled a daily 'Threat' scan for 09:00 and, 'if missed', run again within 23 hrs. Put the computer into 'sleep'. 09:00 passed uneventfully. 'Woke up' the computer at 11:15 and, hallelujah, it started a scan! It recovered! Working as I feel it should. For some reason, it attempted an update too and this failed 'Couldn't contact t
  9. Oh dear! I certainly meant to re-boot but it seems like it stopped at 'meant to'! Anyway, it's done now. As is disabling 'Check for updates before scanning'. How could I have forgotten that after the earlier discussion? Probably Anno Domini... But 'Delay protection at startup' wasn't set. Thank you for taking care of me!
  10. For 1PW: OK, I've done as you requested: removed everything, then mbam-clean and a new install. Again, I accepted all the installer's default suggestions and I've left the settings as installed - except for setting the repeat time for updates to 2 hours, as reccomended by Gonzo. The mbam-check results are attached. Just for the record this is the 'diary' of what I did: Preparation: * Deleted mbam-setup-2.1.6.1022.exe, mbam-clean-2.1.1.1001.exe and mbam-clean-2.1.1.1001.exe * Downloaded mbam-check-2.1.1.1001.exe via link in https://forums.malwarebytes.org/index.php?/topic/14602
  11. Many thanks for your input, daledoc. I didn't change the scan time setting to avoid any suspicion of a ham-fisted edit, the problem being that recovery from a missed scan was not working. Actually, I suspect that this has been happening for some time as, prior to the re-install (when using 2.0.4.1028) I had it set to 12:45 and if the PC was not live at that time then no re-attempt seemed to occur. Your tip of disabling 'Check for updates before...' was interesting. Not only because of the clash potential (I never thought of that) but also since it surely explains why the old 12:45 sched
  12. Many thanks for your speedy reply! The default setting for updates was hourly, repeating every hour. So I've set it to repeat at 2 hour intervals as you suggest. See what happens! And sorry about the double post. Got 'Failed, try again later' first time and foolishly didn't check if was a false alarm or not - it was.
  13. Wow, that was fast - thanks! Attached the logs requested. And sorry about the double post. Got 'Failed, try again later' first time and foolishly didn't check if was a false alarm or not - it was. Addition.txt FRST.txt CheckResults.txt
  14. Last week (2015-05-21) I re-installed MBAM as I was running 2.0.4.1028. Elected to install from scratch, so did the MBAM Clean Removal Process and installed 2.1.6.1022. Accepted all the default suggestions and, on completion, let it update and scan. Noted that the installer had set the time of the next scheduled scan to 2015-05-22 03:13:35 and that it should run again within 23 hours if it failed. To me, 'Run again within xx hours' means 'If the first attempt isn't possible, I'll try again until it succeeds, until xx hours have elapsed'. But it seems I've misunderstood, as this doesn't h
  15. Last week (2015-05-21) I re-installed MBAM as I was running 2.0.4.1028. Elected to install from scratch, so did the MBAM Clean Removal Process and installed 2.1.6.1022. Accepted all the default suggestions and, on completion, let it update and scan. Noted that the installer had set the time of the next scheduled scan to 2015-05-22 03:13:35 and that it should run again within 23 hours if it failed. To me, 'Run again within xx hours' means 'If the first attempt isn't possible, I'll try again until it succeeds, until xx hours have elapsed'. But it seems I've misunderstood, as this doesn't h
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.