Jump to content

neilski

Members
  • Posts

    14
  • Joined

  • Last visited

Reputation

0 Neutral
  1. OK, so my fully protected MS installation had been running all night without a problem, so this morning I rebooted the PC and MW ran up all the protection services without a problem - see screenshot. I can't give a definitive solution to the problem, but the following notes might help... MW version 3.0.6 installed without complaint After installation, MW notified me that some of the real-time protection services, in my case the Web Protection Service was turned off. If I tried to turn this service on, it went into a continuous 'starting service' condition (and continued to notify about the condition). Rebooting the PC and trying to turn the service on after a 'fresh boot' failed in the same manner. The fix for me was to reboot the PC (not sure this was necessary now) and allow all services to load and stabilise (i.e. wait 5 minutes). Close the MW application and re-launch it. Configure protection settings as required/recommended. My hunch is that the PC's service loading order is, in some way significant (either by service dependency or collision) and restarting the MW service-stack on a 'stabilised' operating system seemed to help. All this is conjecture of course - maybe Microsoft ran in a Windows update that fixed the problem - I don't know. If anything changes, or the real problem becomes apparent, then I will report back to this forum.
  2. Yes, missed that - doah! Have turned it on now and MW seems happy. I'll let it 'soak' overnight and, if all is well, reboot in the morning and see if the config and the associated services run up correctly. Will keep you posted. Thanks for your help.
  3. This is odd... Rebooted with 'Web protection' turned off. After a minute or so received nag dialog Stopped and restarted MW Enabled 'Web protection' service appeared to start and run A couple of minutes later received another nag dialog - even with the 'Web protection apparently running - see screen shot. UPDATE - this may be because Ransomware protection may have turned itself off?
  4. I can turn it on after stopping and restarting the application, but if I reboot, it either resets to off or fails to load.
  5. I have exactly this problem on a Windows 10 Professional desktop (also running Kaspersky 'Small Office Security' if that might be significant).
  6. HI Bob, I ran a full scan again Database Version 2015.03.30.05 and it completed successfully without error. Thank you for your fast response. Regards. Neil.
  7. Thank you DaleDoc1 - you have been very supportive - much appreciated. No great rush from this end, it would just be good to get it sorted. Enjoy the rest of your weekend!
  8. Whilst I can see downgrading as a temporary fix, it's not really a long term solution as it prevents you from benefitting from product updates in the future. Better, I think, to try and resolve the issue.
  9. Thanks DaleDoc1, as suggested I ran ChkDsk on both dives (C: and D:) and both came up error free.
  10. I'm pretty sure that I performed the reboot both after the MBAM Cleanup and after the new installation, but perhaps not. Rebooted and re-ran mbam-check-2.1.1.1001.exe and also attempted another Malwarebytes scan. As before the application failed with attached Windows error message during the final Heuristic Analysis. ErrorMessage.txt CheckResults.txt
  11. I have been running Malwarebytes Premium edition for some time on my Windows 8.1 desktop PC. After recently updating to build 2.1.4.1018, MB crashes during a full/scheduled scan. I have uninstalled and reinstalled the latest version as described in the MBAM Clean Removal Process 2x but still the problem persists. I have attached the three recommended log files for reference. Any help/advice would be much appreciated. Addition.txt CheckResults.txt FRST.txt
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.