Meant ma3, but it would work with possible conflicts too.
Ya can just quickly 'kill' it.
I'm sure that would work - but of course the question was why MA3 isn't working the way it's supposed to.
My bet is that MA3 is "doing the right thing" and some other application is interfering with it.
Since it's only happening on one system, as far as we know, I automatically win my bet until Arahanto demonstrates that the problem exists with a fresh installation.