Jump to content

alan_s

Honorary Members
  • Posts

    34
  • Joined

  • Last visited

Reputation

1 Neutral

Recent Profile Visitors

901 profile views
  1. Thank you - that fixed it! This solution rang a bell. Found it in my log and it was last August when MWB wasn't updating at all. Anyway, I'll make a big note in the log in case (when?) it happens again.
  2. I'm running Malwarebytes Version 4.6.6.294 | Update package version 1.0.79484 | Component package 1.0.2189 under Win 10 64-bit 2024-01-11 H4VOC announced version 4.6.8.311 component package 1.0.2242 and today I decided to give it a try (I prefer updating manually). The update appeared to go perfectly, but after the restart, “About” reported Version 4.6.6.294 Component package 1.0.2201 which isn't what H4VOC announced. Tried repeating the update but it reported “MWB is up to date”. Just to be on the safe side I restarted the computer (no, I don't use “Fast Startup”...) but the same was reported. I have a fresh image copy and so restored the computer to pre-update status and tried a new update. Same result. Restored the computer again to get a known state. So what can I do to get what H4VOC announced?
  3. I use OpenOffice 4.1.3 As of today, 2023-05-18 c:a 16:45 CET MalwareBytes 4.5.28.266 Component package 1.0.2005 quarantines C:\Program Files (x86)\OpenOffice 4\program\svl.dll reporting Event=RTP detection Event details=Malware AI.2147896167 Have attached svl.dll Never happened before and I used OpenOfice 8 hours ago with no problems. svl.rar
  4. On Friday, I did as you suggested and all went well. Fortuitously, a new update was released which gave an opportunity to see how update works now. No trouble at all. Many thanks for your help, Porthos!
  5. Launched from the UI, Settings > General clicking the “Check for updates” button. The download went fine but the update process went on for ages. Process Explorer showed that dwm.exe was using 5 - 15% CPU, but nothing else was really doing much. No CPU at all used by mbupdatr.exe, MBAMservice.exe, mbamtray.exe. After 20 minutes or so with nothing happening, downloaded and ran the Support Tool to “Gather logs” Attached here as mbst-grab-results_WhileUpdateStillHanging.zip, Then terminated the UI. The icon in the Notification Area had a red cross and hovering the mouse over it showed “Program version 4.4.0 / Protection disabled”. Various programs wouldn't run, even after a restart. The update failure seems to have damaged Malwarebytes. Prudently, I had taken an image copy of the system before attempting the update so restored from that. Tried the update again. Same result, so new restore. System is Win 10 64-bit, 20H2 Only other security program is Defender All help appreciated! mbst-grab-results_WhileUpdateStillHanging.zip
  6. 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 Malwarebytes. Today, I did them after. On Tuesday, when the Malwarebytes update reached “We need a moment...” I clicked the presented “Restart” button as I normally do. Today I let it count down and do the restart itself. What actually caused the problem is a mystery of course but I feel the main thing is that it works fine now. On reflection, I should have done all this before troubling you, but such is hindsight. Thank you for your guidance!
  7. Right, here is the grab-results file. mbst-grab-results.zip
  8. 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 Malwarebytes active protection? If the next step is a Support Tool run, can the mbst-grab-results.zip file be posted here or is it safer to send it? If so, where to?
  9. 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.
  10. 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 -> Delay protection at start-up 30 seconds helped for version 2.1.8.1057 in my installation but 2.2.0.1024 seems to need 60 seconds. If this doesn't help, try patience at logon time! When giving the password, don't press Enter immediately but wait about 20 seconds. That always seems to do the trick for me.
  11. 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 program corruption or a change in my environment. I didn't report the incident as I've done so before (as have others) and assumed that the advice would be the same, namely 'do a clean removal and install the latest version'. Which I did and all is back to normal again. But please Malwarebytes, this is the 4th time it's happened to me since last December. Nuff said...
  12. 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.
  13. 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 the server'. But this feels a minor issue. A manual update was OK and I'm sure the next scheduled update would have succeededIncidently, the update frequency is set to start at 2 hour intervals (even hours) and 'check for updates before scanning' was not set. At 13:30, I changed the scan type to a daily 'Custom' scan of a USB stick, starting today at 14:30 and, 'if missed', run again within 23 hrs. I 'safely removed' the USB and expected the missing scan target would cause the scan to fail. Then I could re-insert the USB and see if a recovery would be run later. But no, the scan ran at 14:30 and classed as a success: No malicious data encountered. Well I suppose that's true in a sense - the data it was to scan wasn't available so it didn't find anything malicious. Not what I expected, but best not to start a semantics discussion! So, if the computer is turned off at primary scan time then, when the it becomes active, the scheduler appears to assume that the scan was done and that everything went well. There doesn't seem to be any check on whether it in fact was done at all. I don't think this is going to be fixed by tweaking settings. And I don't expect it's going to be very high on Malwarebytes 'to do' list. Indeed, it might even be the intended behaviour. I think the most realistic course is for me to set the scheduling parameters to more suitable values and live with it. Or do as with my AV and just run a manual scan now and then. So 1PW, Gonzo and daledoc1, sorry to have lured you into what seems to be a bit of a wild goose chase but I've learned a lot and now have a much better understanding of how it behaves. Thank you for your patience and suggestions. Of course, if anyone should get a good idea... Regards Alan_S
  14. 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!
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.