Conrad Sallian's community posts

We have updated Remote Utilities to version 7.2.2.0. There are no more false detections by Microsoft. Besides, Viewer and Host have been added to Microsoft Store - the links are available on the download page.

You are encourated to update your installations.

Thanks, everyone. Mysteriously, the host-7.2.1.0.msi is perfectly ok with Microsoft. It's only the .exe version that Microsoft isn't happy about.

As of 23 Oct 2023, if you are trying to download the host-7.2.1.0.exe file from our website, Microsoft Edge blocks it with a message saying that the file was blocked as unsafe. We have already sent a false positive submission to Microsoft but we will appreciate it if our users also report the file as safe because this detection is 'reputation-based' and the SmartScreen simply blocks a previously unknown file.

Here are the steps to do that:

1. First, try to download the host-7.2.1.0.exe in Edge.

2. When the file is blocked, click on the Download icon, then click on the three dots icon and select 'Report this file as safe'.



3. A new tab will open with a feedback form. Fill in the details and click Submit.




Note: This issue is only with Microsoft Defender SmartScreen. The Windows Defender desktop client treats the file as clean.

Hello Gary,

Thank you for your message.

We have sent several false positive reports to Microsoft and are still waiting for them to remove the detections. We are sorry that Microsoft Windows Defender is incapable of distinguishing legitimate and digitally signed software from malware.

As for connectivity issues - you may find the following troubleshooting guides useful:
https://www.remoteutilities.com/support/kb/cannot-connect-using-internet-id-connection/
https://www.remoteutilities.com/support/kb/cannot-connect-using-direct-connection/

Depending on which connection method you use.

Hope that helps.

Hello Mike,

Thanks for the update. So the version you are rolling out sets the recovery option in the host service to run the exe with the -restart flag (like what is configured by your CMD file?

Not only that. The bulk logoff bug will also be fixed.

As for AV false detections, it seems Google or Windows Security is blocking my current custom EXE installer v7.1.7.0. Does the code signing certificate expire?

The expiration date for the certificate only matters for signing. The expiration of the certificate does not invalidate the signature for the files already signed.

If this is Microsoft detection, I recommend that you send a false positive report on this page https://www.microsoft.com/en-us/wdsi/filesubmission

Hi Mike,

Actually we are ready to release, we are just waiting for some test results on this issue.

Also, given how intolerant and indiscriminate antiviruses have become, this time we'll have to first initiate the virus checks and  make sure that at least the most critical false detections are removed before we make the version public. This may delay the release from a few days to a week, but this is a necessary evil.

Hello Matthew,

Yes, of course. In the Host log it should say that the Host has been restarted.

Hello Everyone,

Have you had a chance to test the Hosts running with the new settings applied by the script? Please, let us know. Thanks.

Hi Tom,

Actually you must be able to submit a ticket. Any user with a commercial license can submit tickets. And your status says 'Starter' (see the label at the top right corner of the forum message window) which means that support tickets are available to you.

Let us investigate why your ticket wasn't working properly and get back to you.

UPD: I've sent you a message via the ticket you created. If you cannot answer, please update this thread. You can send a screenshot of the error message directly to [email protected] for further investigation.

Hello Tom,

Thank you for your report.

We understand your frustration and we are also concerned by the quality of modern antivirus software, which fails to do a simple task of distinguishing legitimate, digitally signed program from malware.

Of course I can't make exceptions for every temp case because the paths and files are often random names. I can't fix this from my end.

Neither can't we. It's the antivirus software vendor that can fix their errors (but they never acknowledge them). We do our best to alleivate this situation by sending false positive reports.  If you as their customer would send a false positive report and specifically mention that faulty operation of their software distrupts your work process, the issue would certainly be resolved faster.