Skwarkman

Yup : Back and happy. : Just spare a thought for the bod who woke up to the day from hell - we have all (those coders amongst us) been there, and if it was not malicious or gross negligence then it is "stuff that happens" : I don't care if you are MS or a one person band Indy - it happens... you try to prevent it .. but stuff happens.

Don't get me wrong - I hope it does work 100% : But whilst there are problems elsewhere - I am just thankful for my layered approach: the 'ghost in the machine ' can be a tricky so and so... :-)

because Humans write code - (mostly)... and machines interpret it... Machines don't conform to people's logic based assumptions. Ok - what if this problem has broken MBAMS ability to determine who should NOT be encrypting files ? . Encryption protection would work - just not effectively ... just a thought...

in a (wary) programmer's lexicon :- assumption = bad.

with the scanning broken - how do you know that other protection is still functioning ?: you are just repeating explanations without empirical evidence that it is working. I have debugged enough code in my time to know I need test units - that's why I said "prove it" (and it was a tongue in cheek)

;-) prove it.... ;-)

... just wait a minute until it tries to update ...

for the apologists : It was less than a week ago that Malwarebytes had a front page sales blurb trumpeting (sorry) the effectiveness of the protection against the recent crypto-locking outbreak : this is a publicity nightmare for them at a sensitive time - of course, people are paranoid !: I am, I am trying to work on client accounts which are the core to the success of our business and the last thing I need is to know that my machine may be insecure. I want to get back to work - Not sit here waiting for a solution.... (sorry: bit heated - but nevertheless totally true...)

I gather an "email" has been sent to QA... "twiddle thumbs" :- ... smart phones... amazing things - apparently some still have the ability to make phone calls ;-) ;-) - with a FUBAR like this maybe it is time to figure out which app does the dialing ;-)

Same here - Including Updating to 3.1 & same Scans fail... Could somebody pop round - give a knock on their door (at home?) - wake em'up and tell them what is happening: this appears to be ALL users (that are paying attention)... :-)