[Bug] v1.4.2 & v1.2.3 Installers Ignore Command-Line Parameters and App Overwrites Config File on Launch #3681

New issue

Closed

opened 2026-02-21 01:32:49 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-21 01:32:49 -05:00

Owner

Originally created by @mhdm2512-dot on GitHub (Sep 23, 2025).

Bug Description

Hello, we are trying to deploy RustDesk in a corporate Active Directory environment to standard (non-admin) users, and we have found that it's currently impossible due to two main issues:

The installers (both v1.4.2 and v1.2.3) ignore configuration parameters like --key and --relay-server during a silent installation.
The application actively overwrites any pre-configured RustDesk2.toml file with a default one upon launch.

This makes automated, pre-configured deployment for standard users impossible.

Environment

RustDesk Version: 1.4.2 (rustdesk-1.4.2-x86_64.exe) and 1.2.3 (rustdesk-1.2.3-2-x86_64.exe)
Operating System: Windows 10 Pro (OS Build 19045)
Deployment Method: Group Policy (GPO) and manual command-line tests.

Steps to Reproduce

We have confirmed this failure with two different methods:

Method A: Installer Parameters (Fails)

On a clean machine, run the following command from an Administrator command prompt:
rustdesk-1.4.2-x86_64.exe --silent-install --key "SUA_CHAVE_AQUI" --relay-server "SEU_SERVIDOR_AQUI"
After the installation completes, open the RustDesk client.

Method B: Configuration File Placement (Fails)

Install RustDesk normally.
Use a script to create a perfectly valid RustDesk2.toml file in the %APPDATA%\RustDesk\config directory.
We confirmed the file is correct and exists before launching the application.
Launch the RustDesk application.

Expected Behavior

For both methods, the RustDesk client should start up pre-configured with the specified public key and relay server, and be ready to connect.

Actual Behavior

Method A: The application installs successfully, but it is completely unconfigured. The --key and --relay-server parameters are ignored by the installer.
Method B: Upon launch, the RustDesk application immediately deletes or overwrites our pre-configured RustDesk2.toml file and replaces it with a default, unconfigured one.

We also noted that changing the network settings via the GUI requires administrator elevation (UAC prompt), which is the core reason why deployment for standard users is so difficult. Our GPO automation (which runs with SYSTEM privileges) successfully installs the app, but the installer itself does not apply the configuration.

Thank you for your help.

How to Reproduce

We have confirmed this failure with two different deployment methods in our Active Directory environment.

Method A: Installer Command-Line Parameters

On a clean machine, run the following command from an Administrator command prompt:
rustdesk-1.4.2-x86_64.exe --silent-install --key "SUA_CHAVE_AQUI" --relay-server "SEU_SERVIDOR_AQUI"
After the installation completes, open the RustDesk client.
Result: The application installs but is completely unconfigured. The --key and --relay-server parameters are ignored.

Method B: Configuration File Placement

Install RustDesk normally.
Use a script to create a valid RustDesk2.toml file in the %APPDATA%\RustDesk\config directory. We have confirmed the file is present and correct before launching the application.
Launch the RustDesk application.
Result: Upon launch, the RustDesk application immediately deletes or overwrites the pre-configured RustDesk2.toml file and replaces it with a default, unconfigured one.

Expected Behavior

For both methods, the RustDesk client should start up pre-configured with the specified public key and relay server, and be ready to connect to our self-hosted server.

Operating system(s) on local (controlling) side and remote (controlled) side

Remote (controlled) side: Windows 10 Pro (OS Build 19045) * Local (controlling) side: (Not relevant for this deployment bug, can be any OS)

RustDesk Version(s) on local (controlling) side and remote (controlled) side

Remote (controlled) side: 1.4.2 (Installer: rustdesk-1.4.2-x86_64.exe). We have also tested and confirmed the same installer parameter failure with version 1.2.3. * Local (controlling) side: (Not relevant for this deployment bug)

Screenshots

Additional Context

No response

Originally created by @mhdm2512-dot on GitHub (Sep 23, 2025). ### Bug Description ### Bug Description Hello, we are trying to deploy RustDesk in a corporate Active Directory environment to standard (non-admin) users, and we have found that it's currently impossible due to two main issues: 1. **The installers (both v1.4.2 and v1.2.3) ignore configuration parameters** like `--key` and `--relay-server` during a silent installation. 2. The application **actively overwrites any pre-configured `RustDesk2.toml` file** with a default one upon launch. This makes automated, pre-configured deployment for standard users impossible. ### Environment * **RustDesk Version:** 1.4.2 (`rustdesk-1.4.2-x86_64.exe`) and 1.2.3 (`rustdesk-1.2.3-2-x86_64.exe`) * **Operating System:** Windows 10 Pro (OS Build 19045) * **Deployment Method:** Group Policy (GPO) and manual command-line tests. ### Steps to Reproduce We have confirmed this failure with two different methods: **Method A: Installer Parameters (Fails)** 1. On a clean machine, run the following command from an Administrator command prompt: `rustdesk-1.4.2-x86_64.exe --silent-install --key "SUA_CHAVE_AQUI" --relay-server "SEU_SERVIDOR_AQUI"` 2. After the installation completes, open the RustDesk client. **Method B: Configuration File Placement (Fails)** 1. Install RustDesk normally. 2. Use a script to create a perfectly valid `RustDesk2.toml` file in the `%APPDATA%\RustDesk\config` directory. 3. We confirmed the file is correct and exists *before* launching the application. 4. Launch the RustDesk application. ### Expected Behavior For both methods, the RustDesk client should start up pre-configured with the specified public key and relay server, and be ready to connect. ### Actual Behavior * **Method A:** The application installs successfully, but it is completely unconfigured. The `--key` and `--relay-server` parameters are ignored by the installer. * **Method B:** Upon launch, the RustDesk application immediately deletes or overwrites our pre-configured `RustDesk2.toml` file and replaces it with a default, unconfigured one. We also noted that changing the network settings via the GUI requires administrator elevation (UAC prompt), which is the core reason why deployment for standard users is so difficult. Our GPO automation (which runs with SYSTEM privileges) successfully installs the app, but the installer itself does not apply the configuration. Thank you for your help. ### How to Reproduce We have confirmed this failure with two different deployment methods in our Active Directory environment. **Method A: Installer Command-Line Parameters** 1. On a clean machine, run the following command from an Administrator command prompt: `rustdesk-1.4.2-x86_64.exe --silent-install --key "SUA_CHAVE_AQUI" --relay-server "SEU_SERVIDOR_AQUI"` 2. After the installation completes, open the RustDesk client. 3. **Result:** The application installs but is completely unconfigured. The `--key` and `--relay-server` parameters are ignored. **Method B: Configuration File Placement** 1. Install RustDesk normally. 2. Use a script to create a valid `RustDesk2.toml` file in the `%APPDATA%\RustDesk\config` directory. We have confirmed the file is present and correct *before* launching the application. 3. Launch the RustDesk application. 4. **Result:** Upon launch, the RustDesk application immediately deletes or overwrites the pre-configured `RustDesk2.toml` file and replaces it with a default, unconfigured one. ### Expected Behavior For both methods, the RustDesk client should start up pre-configured with the specified public key and relay server, and be ready to connect to our self-hosted server. ### Operating system(s) on local (controlling) side and remote (controlled) side * **Remote (controlled) side:** Windows 10 Pro (OS Build 19045) * **Local (controlling) side:** (Not relevant for this deployment bug, can be any OS) ### RustDesk Version(s) on local (controlling) side and remote (controlled) side * **Remote (controlled) side:** `1.4.2` (Installer: `rustdesk-1.4.2-x86_64.exe`). We have also tested and confirmed the same installer parameter failure with version `1.2.3`. * **Local (controlling) side:** (Not relevant for this deployment bug) ### Screenshots ### Additional Context _No response_