QUOTE (Cristi Raducu @ Feb 13 2011, 12:39 PM)
This is the behaviour of a buggy program and it should be solved by their developers.
Also this can happen to any ordinary program.
In this case you can either contact them for support on this matter or simply uninstall their application.
Indeed. But, as I have said before; which application.
All that Reactor is telling me is that there is an unregistered verion of their assembly being used in a .Net application.
Which .Net application? Reactor doesn't tell me and I have dozens on my machine.
There are a number of issues here:
1. Someone distributed an application with an unregistered copy of Reactor.
2. Reactor reacts (sorry) by creating a process with a random .exe name which nags the unspecting end user.
3. BitDefender doesn't stop this at all.
Now the thing to do is to uninstall the offending.Net application. Yes, I would do. But which one? I have dozens on my machine as I expect that you have too. In fact, I don't know what applications I have here is written which with language/framework. Do you?
So saying that I ought to contact these mysterious 'them' doesn't help. What I want to know is how I can get Bit Defender to stop random processes being started.
Yes, the fault is with the .Net developer. But at the end of the day the Malware actions are clearly performed by Reactor and BitDefender won't stop this.