It's one thing to make rogue software from legitimate software by patching it or putting it in a wrapper - either way is in itself illegal and violates our EULA. We bear no responsibility for the consequences of such abuse of our program, and that is clearly stated in our EULA.
And it's an entirely different thing to provide perfect rogue software out-of-the-box. We don't do that and never will. Remote users must always know that they are being monitored or are about to be monitored. Why would an admin want to hide that fact from a user? An organization must have rules and procedures that allow IT department to remotely log in to employee's computers for maintenance, support etc. So the employees shouldn't be surprised when they see a warning message.
Regardless of how many customers or contracts we may lose, we won't make completely silent rogue-like software. We respect user's privacy, as well as local and international laws. I wouldn't say this is a short sighted strategy. Money is important, but law and respect for ordinary folk is above the money.
Update on this issue. In the upcoming release 6.6 we decided to implement it differently. The program will be installed without requiring a user to accept anything and you 'll be able to get access right away. There will only be an informational message in the bottom right corner that says the program was installed.
That message is necessary to at least somehow let the user know. Once they click "Got it" in the message it'll disappear and will no longer be shown. Their clicking or not clicking the "Got it" button, however, doesn't affect your ability to connect right away. As I said, it's just a warning/informational message.
Thank you for your message. There is already a thread on this topic. We do our best to resolve the issue. Microsoft responds, but the resolution process is kind of slow, perhaps because the company is kind of big :)
Yes, we are aware of that. It was reported in this thread and some tickets. We are in conversation with Microsoft - they are responsive but looks like the issue is back after yesterday's successful attempt to eliminate it.
We'll keep trying to make Microsoft resolve this asap. Sorry for any inconvenience.
This detection was strange from the very beginning. For example, when we tested it yesterday Windows Defender falsely notified as about this "trojan" but still allowed Viewer to run. Then why they call the Viewer a trojan in the first place? :)
Anyway, we have already received a response from Microsoft and they asked some more information. We'll make sure that this issue is resolved soon.
Thank you for your message. Yes, this problem was also reported today by a few other users as well. We have already contacted Microsoft regarding this issue. Hopefully, they will fix it as soon as possible.
I perfectly understand your frustration because we are frustrated with these uncontrolled and irresponsible antivirus software behaviors too.
P.S. I will move this thread to the antivirus sub -forum.