Client SDK for Windows
Developers' Guide
Exit Codes for Programmatic USB Installations and Uninstallations
You can make the installer and uninstaller calls programmatically from your client application. The return and exit codes you should expect are summarized in the following tables:
| 0: Success, no reboot required. Expected on a fresh installation. |
| 1: Success, reboot required. Unexpected, but harmless. |
| 2: Success, installation continues after reboot. Expected when running the installer during an upgrade without rebooting (installing a new version after uninstalling an old version, with no reboot in between). This indicates that while the driver is usable immediately, additional action has been scheduled following the next reboot. This prevents scheduled actions by the uninstaller from disabling the driver. |
| -1: Error, general. An unexpected error occured. The most likely cause is insufficient privileges to install drivers, or another permissions issue. |
| 0: - |
| 1: Success. Expected |
| 2: - |
| -1: Error, general. An unexpected error occured. The most likely cause is insufficient privileges to ininstall drivers, or another permissions issue |
Last updated: Thursday, July 18, 2024