Conrad Sallian's community posts

Hello,

We've updated the following packages:

Viewer (deb)
Viewer (rpm)
Host (deb)
Host (rpm)

Feel free to download the updated files on this page:
https://www.remoteutilities.com/download/linux.php.

Hello Emiliano,

Yes, we are currently looking into this issue. Sorry for the inconvenience.

Hi M P,

Since Bazzite uses an immutable (rpm-ostree) system, installing the Host via RPM can cause version conflicts.

Please try installing the Host from the binary archive instead:

1. Download the archive:
https://www.remoteutilities.com/download/host1.0.23.b23.tar.xz

2. Extract it and run the installer as root:

tar -xf host1.0.23.b23.tar.xz
cd host1.0.23.b23
sudo ./host -install

Let us know if you run into any issues.

Hello John,

Thank you for your message.

No, you don't have to install Viewer. The exe file is a wrapper over the msi, so this error indicates that there's an issue with installing an msi package on this computer.

Please, refer to this MS knowledge base article, it may help to resolve it:
https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d

Hi Jim,

Thank you for the feedback. Unfortunately it's a current limitation of the beta version.

Dear users and beta testers,

We have released the first beta version of Remote Utilities Host for macOS. Feel free to download and test it — we appreciate your feedback.

P.S. The version number is beta 23 so that it matches the rest of the macOS and Linux modules.

Hello,

You can simply add the folder from which you run the Agent (after downloading it) to your antivirus exceptions.

If you're using the Host (the persistent module), make sure to whitelist the following folder:
C:\Program Files (x86)\Remote Utilities - Host\

Hello,

Remote Utilities Host runs as a Windows SYSTEM service. When the Host needs to “enter” a different Windows session, Windows uses the standard token duplication mechanism to create a session-appropriate process under the SYSTEM account.

This isn’t privilege escalation — the Host already runs with SYSTEM privileges as a service. Microsoft Defender sometimes flags this pattern generically because it can also appear in malware, but in this context it is part of normal, documented Windows functionality for remote-access and RMM tools.

Hope that helps.

Hello Mike,

Thank you for your message.

We haven’t received any similar reports so far. Could you please try changing the input method in the connection properties to see if that resolves the issue?

Hi John,

Unfortunately, there’s no built-in way to immediately detect when a remote Host goes offline—there’s no continuous monitoring. The only indication is the status icon in the address book.

There is a kind of workaround—you can open a View-only connection, and if the Host goes down during the session, the Viewer icon will start flashing/blinking on the taskbar. It's not a guaranteed method, but it can serve as a basic indicator.