JetBrains Rider

Close Rider before running a managed Windows update. The JetBrains Rider EXE package can return Exit Code 1 when Rider is open during an update, so Intune, ConfigMgr, RMM, or PSADT deployments should include a Rider-specific close/prompt rule before launching the installer.

If a Rider update reports Exit Code 1, first treat it as a likely app-in-use condition: have the user save work, exit Rider, then rerun the installer and confirm the installed build. This is especially important on developer workstations where IDEs are commonly left open with active solutions.

Official source context: JetBrains publishes Rider at jetbrains.com/rider, download builds at jetbrains.com/rider/download, and installation guidance in the Rider help at jetbrains.com/help/rider/Installation_guide.html.

For managed Rider updates, close the IDE before launching setup. If Rider remains open, the update can return Exit Code 1618; close the IDE first and verify the installed version after setup exits.

Source: Rider official source.

For managed Rider updates, close Rider 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: Rider Windows/download documentation.

Official source: Rider Windows/download documentation.

For unattended Rider deployments, use JetBrains’ silent installer with a configuration file, for example JetBrains.Rider-*.exe /S /CONFIG=C:\Temp\rider_silent.config /LOG=C:\Windows\Temp\Rider-Install.log /D=C:\Program Files\JetBrains\Rider. In rider_silent.config, use options such as mode=admin, launcher64=0, updatePATH=1, and updateContextMenu=1 only when they match the developer-workstation baseline.

Close Rider before managed updates; Rider packages can fail when the IDE is open, so prompt/defer or pre-close the IDE before retrying. Official source: JetBrains Rider installation guide.