Search the Community

After first use of Malwarebytes where 200 PUP files were quarantined, I could not log in to Windows 10. I received "We Can't Sign In To Your Account" message. I unquarantined the files, but no change. I've tried changing temporary login files in Regedit and restarted several times, but system unchanged. Not sure if Malwarebytes responsible, but laptop running fine until first use.

Hi there! Throughout the past few months, I've had problems running my Win7 Professional 64-bit PC rig properly. The problem showed as intermittent freezing of the whole operating system every now and then, let's say once in an hour or so, for around 5-15 min at a time. Meaning; I can't click on anything from the task bar, the mouse cursor turns into the spinning circle (as in; waiting, waiting ...); everything that I click on or type is stored in some kind of a buffer that then gets "released" after the clog re-opens. I am running ESET Internet Security 2018 (the latest version; 12.0.27.0) as well as Malwarebytes Anti-Malware Premium (the latest version as well; 3.6.1.2711) I have gone thru the problem on ESET's forums as well; https://forum.eset.com/topic/15962-eset-internet-security-updates-hang-up-as-well-as-sites-like-windows-update/?_fromLogin=1 Sorting out different possibilities within the last few months and I've indeed realized that it's ESET Internet Security 2018 and Malwarebytes Anti-Malware Pro/Premium conflicting with each other. Turning off Malwarebytes actually solved the problem altogether. However, I went thru Malwarebytes' website to see all the listed components of MBAM that should be added to i.e. ESET's exclusion list, and that did NOT solve the problem. Now as I'm running Malwarebytes again, the freeze-up problem has also returned as usual. Disabling MBAM = no problems, no freeze-ups. The two software used to work just fine together before this summer. I've tried googling up the ESET+MBAM combo and potential pitfalls and tried to check that I've got them all in order. These problems didn't start until the autumn of this year, however. Before that, I had been running ESET+MBAM side by side without any problems. So, since I already have the exclusion list done, is there any certain modules in ESET that should NOT be enabled while MBAM is also running? I can't reply to the original thread on ESET's forums [see link above in this post] since the thread has been closed (and I did not receive any messages of anyone actually replying to me), and now I'm wondering what should I do next. The thing is that ESET and MBAM both detect i.e. realtime web threats differently. Throughout the past few years, both of the programs have caught up with potential threats in time, sometimes it's been MBAM, sometimes it's been ESET that has caught the lurking culprit. So, I really wouldn't want to start disabling real-time protection features too heavily. All help is kindly appreciated. Thank you.