ROCm/docs/deploy/windows/cli/uninstall.md

Uninstallation Using the Command Line Interface

The steps to uninstall the HIP SDK for Windows are described in this document.

HIP SDK Uninstallation

The command line installer is the same executable which is used by the graphical front-end. The options supported by the command line interface are summarized in {numref}hip-sdk-cli-options.

:name: hip-sdk-cli-options
| **Install Option** | **Description** |
|:------------------:|:---------------:|
| `-install` | Command used to install packages, both driver and applications. No output to the screen. |
| `-install -boot` | Silent install with auto reboot. |
| `-install -log <absolute path>` | Write install result code to the specified log file. The specified log file must be on a local machine. Double quotes are needed if there are spaces in the log file path. |
| `-uninstall` | Command to uninstall all packages installed by this installer on the system. There is no option to specify which packages to uninstall. |
| `-uninstall -boot` | Silent uninstall with auto reboot. |
| `/?` or /help | Shows a brief description of all switch commands. |

Unlike the graphical installer, the command line interface doesn't support
selectively installing parts of the SDK bundle. It's all or nothing.

Launching the Installer From the Command Line

The installer is still a graphical application with a WinMain entrypoint, even when called on the command line. This means that the application lifetime is tied to a window, even on headless systems where that window may not be visible. To launch the installer from PowerShell that will block until the installer exits, one may use the following pattern:

Start-Process $InstallerExecutable -ArgumentList $InstallerArgs -NoNewWindow -Wait

Running the installer requires Administrator Privileges.

For example, uninstalling all components and

Start-Process ~\Downloads\Setup.exe -ArgumentList '-uninstall' -NoNewWindow -Wait