Then I unchecked the mentioned items, and chkdsk dit it again.

And after it, I had to put my Drive Image back so as to be able to use chkdsk. As I said in my report, I tried it several times, all to no avail. I am very sorry to say I do not intend to set everything back yet. Would you please set everything back to the way it was in MBAM and retry chkdsk again and reply to this topic with your results? i.e. Since you state chkdsk was able to run, did that five stage utility find/repair any issues with the C: partition? P.S.- A friend of mine has the same problems. The question for me is: can this be fixed? I do not want to wag my finger at either Malwarebytes or Avast. Let me reiterate that this did not happen between Malwarebytes this and previous versions and Avast versions before their latest release. Then I had Malwarebytes scan the computer.Īs far as this 76-year-old can understand, there is a conflict between Malwarebytes' Heuristics and this Avast release. It so happened I unchecked some items in your Malwarebytes settings “Detection and Protection” : Advanced Heuristiscs and Archives. Unfortunately enough the blocking program was not named. Never in my computer life seen that happen before.

And so I did.īut alas! the chkdsk could not do its job, as some other installed program blocked this. You know, to chkdsk c:, one has to start up again. See, I regularly make an Acronis Drive Image, and before I start doing so, I chkdsk drive C:

1143).īut I do have them after I installed Avast’s latest release. (and previous releases) and Avast! Free dating before its latest release (2015. I had no problems whatsoever between Malwarebytes 2. My Malwarebytes packet: 2., with the most recent updates. My present OS: a fully updated Windows 7 Utimate Service Pack 1 and 64-bit Operating System. I’d like to tell you about my latest “frustrations” in Windows-land, and this time between the products displayed in the subject.

Avast trial ends in 14 days