RustRover

For scripted RustRover deployment on Windows, use JetBrains’ silent installer options with a config file, for example RustRover-*.exe /S /CONFIG=rustrover_silent.config /LOG=C:\Logs\rustrover_install.log /D=C:\Program Files\JetBrains\RustRover. Set mode=admin in the silent config when you need an all-users install, and use the config file for options such as desktop shortcuts, file associations, PATH updates, and context-menu entries. JetBrains documents these RustRover silent install options.

For managed updates, close active RustRover sessions before launching the installer. The RustRover x64 EXE update can return Exit Code 1618 when the IDE is open, so Intune, ConfigMgr, and PSADT packages should treat RustRover as a conflicting process and prompt, defer, or close it before update installation.

For managed RustRover updates, close the IDE before launching the installer. If RustRover is open, the update can return Exit Code 1618; close the IDE first and run detection again after setup finishes.

Source: RustRover official source.

For managed RustRover updates, close RustRover before starting the Windows installer. The PMPC-documented update path can return Exit Code 1618 when the application is open, so use a pre-close or user-deferral step and rerun detection after setup. Official source: RustRover Windows/download documentation.

Official source: RustRover Windows/download documentation.