Default Client Settings Cannot Be Re-Enabled After Turning Off

Product: RustDesk Server Pro
Component: Custom client generation (default settings management)
Version: 1.6.3 (Server) 1.4.1 (Client)
Environment: Tested with both client and server builds, on multiple operating systems (Windows, Linux, macOS, Android).

---

Description

When generating custom clients with a customized set of default settings, the settings are correctly applied and appear as enabled (checked) by default.

However, once one of these default-enabled settings is manually disabled, it cannot be switched back on again. The toggle remains one-way (only from enabled → disabled, but not back).

By contrast, settings not included in the default list behave as expected: they can be toggled on and off freely.

This issue occurs across all operating systems in my tests.

---

Steps to Reproduce

1. Generate a custom client with at least one default settings (example):

displays-as-individual-windows=Y

2. Open the client and verify that the Displays as individual windows setting is checked by default.
3. Manually disable it by clicking on it.
4. Try to re-enable it.

---

Expected Result

Settings included in the default configuration should be toggleable both ways (on/off) after client generation.

---

Actual Result

Once turned off, a setting included in the default list cannot be turned back on.

---

Impact

• Users cannot restore critical security or usability features (e.g., privacy-mode, lock-after-session-end) after disabling them once.
• This limits flexibility for admins and end-users.

---

Notes

• The bug affects only default-configured settings.
• Settings not part of the initial default config behave normally.
• Reproduced consistently with multiple settings and across different OS clients.

No files, tests, or entry points are named. Start by locating custom client generation and default-settings handling, then reproduce the steps with displays-as-individual-windows=Y; done means a generated client's default-configured settings can be disabled and re-enabled across the affected clients.