This CSV was generated using arktiv/table-csv-chrome, and cleaned up using the following command:
cat sentinel-exit-code.csv | tr -d $'\x0d' | tr -d $'\xc2' | tr -d $'\xef' | tr -d $'\xbb' | tr -d $'\xbf' > sentinel-exit-code-conv.csvYou can find the relevant documentation at the following link:
https://[instance subdomain].sentinelone.net/docs/en/return-codes-after-installing-or-updating-windows-agents.html##| Value | Scenario | Status | Detailed Status | Description | Next Step | |
|---|---|---|---|---|---|---|
| 0 | Install or Upgrade | Completed | Installation/Upgrade completed | Complete success. Uninstall and re-install were triggered, but the installation completed successfully. | Continue with the procedure. Validate that a new version of the Agent is installed. | |
| 12 | Upgrade | Completed | Upgrade completed | Complete success. Uninstall and re-install were not triggered. | Continue with the procedure. Validate that a new version of the Agent is installed. | |
| 100 | Upgrade | Pending User Action | Upgrade is pending on reboot | The uninstall of the previous Agent succeeded. Reboot the endpoint to continue with the installation of the new Agent. | Reboot the endpoint. | |
| 101 | Upgrade | Pending User Action | Upgrade is pending on reboot | Reboot is required to continue with the installation. | Reboot the endpoint. | |
| 103 | Upgrade | Pending User Action | Upgrade is pending on reboot | Reboot is required to uninstall the previous Agent and install the new Agent. | Reboot the endpoint. | |
| 104 | Upgrade | Pending User Action | Upgrade is pending on reboot | Reboot is already required by a previous run of the installer. | Reboot the endpoint. | |
| 200 | Local Uninstall | Pending User Action | Uninstall is pending on reboot | Cleaning (remove previous installation directories and the current Agent) will be done after reboot.This return code can be returned only when using the clean_only (-c) flag. | Reboot the endpoint. | |
| 201 | Special Flow | Failed taking diagnostics. | Contact Support. | |||
| 202 | Special Flow | Health check deleted old directories successfully. | ||||
| 203 | Special Flow | Health check deleted old directories successfully. | Reboot the endpoint to complete the cleaning. | |||
| 204 | Internal use only. | Nothing. | ||||
| 205 | Install or Upgrade | Canceled | Installation/Upgrade aborted | Aborted by the user (from the endpoint). | Nothing. | |
| 206 | Install or Upgrade | Canceled | Installation/Upgrade canceled | Handled by command line parser. Example: You passed the wrong argument. | Nothing. | |
| 1000 | Upgrade | Canceled | Agent has the same version | Upgrade canceled. Cannot continue with the upgrade. An Agent with the same or higher version is already installed on the endpoint. | Nothing. No upgrade is necessary. | |
| 1001 | Downgrade | Canceled | Agent cannot be downgraded | Downgrade canceled. The version you are trying to downgrade to is too old. | Reboot the endpoint. | |
| 1002 | Install or Upgrade | Canceled | Another installer is already running. | Installation or upgrade canceled. Another installer is already running. | Wait for the previous running to finish. | |
| 1003 | Install or Upgrade | Canceled | Another installer is already running. | Installation or upgrade canceled. Another MSI installer is already running. | Finish the other MSI installer. | |
| 1004 | Upgrade | Not relevant | Upgrade canceled | Upgrade canceled. The arguments given to the Installer (using -a or -- installer arguments) are invalid. | Check the installer arguments. | |
| 1005 | Upgrade | Not relevant | Upgrade canceled | Upgrade Canceled, the passphrase provided is invalid. | Provide the correct passphrase or contact Support. | |
| 1006 | Upgrade | Not relevant | Upgrade canceled | Internal use only. | Contact Support. | |
| 1009 | Install | Failed | Installation aborted | Windows Task Scheduler folders \Sentinel and/or \SentinelOne are inaccessible. For example, if a Task Scheduler task exists at this path. | Delete the existing \Sentinel and/or \SentinelOne folders, or ensure they are accessible (for example, delete the problematic task), then run the installer again. | |
| 2000 | Install or Upgrade | Failed | Installation failed - unexpected error | General failure. Logs and diagnostic data will help you understand this issue, and will be sent automatically to the SentinelOne Cloud. | Collect logs and contact support to troubleshoot. | |
| 2001 | Upgrade | Failed | Installation failed | Upgrade failed. Cannot proceed with the uninstall and re-install. | Collect logs and contact support to troubleshoot. | |
| 2002 | Install or Upgrade | Failed | Installation failed | Installation failed or upgrade failed. The previous Agent was uninstalled but the installation of the new Agent failed. | Collect logs and contact support to troubleshoot. | |
| 2003 | Upgrade | Failed | Installation failed | Failed to uninstall the old Agent. | Collect logs and contact support to troubleshoot. | |
| 2004 | Upgrade, or use the -c parameter | Failed | Installation failed | Retry in Safe Mode. | If you ran the tool without a passphrase (-k) , rerun the tool with the passphrase. If you get this error code again, reboot the endpoint into Windows Safe Mode and try again. | |
| 2005 | Upgrade | Failed | Installation failed | Upgrade authentication error. Failed to get upgrade approval from the Management. | Make sure the upgrade was approved and the endpoint has an internet connection to the Management. | |
| 2006 | Upgrade | Failed | Installation failed | Configuration not found. Unable to proceed with the upgrade. | Collect logs and contact support to troubleshoot. | |
| 2007 | Upgrade | Failed | Installation failed - unexpected error | The upgrade failed. The installer faced an unexpected error. Cannot proceed with the uninstall and re-install. | Reboot the endpoint. If that does not help, contact Support. | |
| 2008 | Install or Upgrade | Failed | Installation failed | Missing site token. | Try again with the site token. From the command line, add the parameter -t <site_token>. | |
| 2009 | Upgrade | Failed | Installation failed | Failed to retrieve the Agent UID. | Upgrade the Agent again with the parameter --dont_preserve_agent_uid or contact Support.Note: If you are uninstalling and reinstalling the same Agent version, you might need to reboot the endpoint before you attempt to reinstall the Agent. | |
| 2010 | Upgrade | Not relevant | Upgrade failed | Interactive desktop required. | Run the upgrade in Quiet mode. Upgrade the Agent again with the parameter -q or --qn.These parameters are available for Agent versions 22.2+. | |
| 2011 | Install or Upgrade | Failed | Installation failed | The installer is not signed correctly. | Download a new installer and verify the certificates are up to date. See How To Solve an Invalid Signature Error. | |
| 2012 | Upgrade | Failed | Installation failed | Could not determine the currently installed Agent version. | Upgrade the Agent again with the parameter†--force†or contact Support. | |
| 2013 | Install or Upgrade | Failed | Installation failed | Insufficient system resources. | ||
| 2014 | Install or Upgrade | Failed | Installation failed | Extract resources general failure. | Collect logs and contact support to troubleshoot. | |
| 2015 | Install or Upgrade | Failed | Installation failed | System requirements not met. | Read the requirement shown in the message. | |
| 2016 | Install or Upgrade | Failed | Installation failed | Microsoft KB2533623 is not installed. | Windows 7 with KB2533623 or†a newer†OS is required. Upgrade and restart your Windows and try again. | |
| 2017 | Install or Upgrade | Failed | Installation failed | Failed to load DLLs safely. | Collect logs and contact support to troubleshoot. | |
| 2018 | Downgrade | Failed | Installation failed | Downgrade failed. | Collect logs and contact support to troubleshoot. | |
| 2019 | Upgrade | Failed | Installation failed | Upgrade authentication error. Failed to get upgrade approval from the Management. | Make sure the upgrade was approved and the endpoint has an internet connection to the Management. | |
| 2020 | Install or Upgrade | Failed | Installation failed | Not enough space on the system drive. | Free space on the disk and try again. | |
| 2021 | Upgrade | Failed | Installation failed | Upgrade authentication error. Failed to get upgrade approval from the Management. | Make sure the upgrade was approved and the endpoint has an internet connection to the Management. | |
| 2022 | Install | Failed | Installation failed | Unable to create an App Container. | Collect logs and contact support to troubleshoot. | |
| 2023 | Upgrade | Failed | Installation failed | Not enough space on the system drive. | Free space on the disk and try again. | |
| 2024 | Upgrade | Failed | Upgrade failed | Cannot open signed message file. | Contact Support. | |
| 2025 | Upgrade | Failed | Upgrade failed | Offline signed message authentication error. | Contact Support. | |
| 2026 | Upgrade | Failed | Installation failed | ISAPI filter removal process failed. | If the upgrade fails, collect logs and contact support to troubleshoot. | |
| 2027 | Install or Upgrade | Completed | Upgrade failed | The Agent was installed and is in Disabled mode. | ||
| 2028 | Upgrade | Completed | Upgrade failed | The Agent was upgraded and the new Agent is in Disabled mode. | ||
| 2029 | Install or Upgrade | Failed to create a working directory under %WINDIR%\Temp. | Verify that the path exists and that you have sufficient privileges. | |||
| 2030 | Install or Upgrade | The installer failed to open one of the files under its own working directory. | Verify that third-party tools are disabled. | |||
| 2031 | Upgrade | Failed | Upgrade aborted | Windows Task Scheduler folders \Sentinel and/or \SentinelOne are inaccessible and could not be removed automatically. For example, if a Task Scheduler task exists at this path. | Delete the existing \Sentinel and/or \SentinelOne folders, or ensure they are accessible (for example, delete the problematic task), then run the installer again. | |
| 2032 | Install or Upgrade | The SentinelOne Installer log could not be opened. | ||||
| 999950 | Upgrade | Scheduled | The Update Timing is set to According to Maintenance Window or custom time range, and the Agent will update in the next available window. | Optional: Make sure the maintenance windows are set correctly in Upgrade Policy. To run the upgrade immediately, cancel the scheduled upgrade. Then select Actions > Update Agent, and in Update Timing, select Immediately. | ||
| 9999300 | Upgrade | In Progress | Waiting for the endpoint to be online. | Wait for the whole upgrade process to complete. | ||
| 9999301 | Upgrade | In Progress | In Queue. Waiting for resources to be available. For example, Maximum concurrent downloads setting is reached, so Agents must wait. | Wait for the whole upgrade process to complete. | ||
| 9999302 | Upgrade | No maintenance window or custom time range is configured. | Set one or more maintenance windows, or a custom time range, in Upgrade Policy. Update Timing is set to According to Maintenance Window or a custom time range, and the Agent will update in the next available window. | |||
| 9999400 | Upgrade | In Progress | Command sent. Only for Agents before 4.1 that do not support the new status reporting. | |||
| 9999401 | Upgrade | In Progress | Download started. Wait for the whole upgrade process to complete. | |||
| 9999402 | Upgrade | In Progress | Download finished. Wait for the whole upgrade process to complete. | |||
| 9999403 | Upgrade | In Progress | Installation of new version started. Wait for the whole upgrade process to complete. | |||
| 9999500 | Upgrade | Canceled | The task was canceled. | |||
| 9999501 | Upgrade | Canceled | The task was canceled. | |||
| 9999502 | Upgrade | Canceled | The task was canceled. | |||
| 99992500 | Install or Upgrade | Failed | Download failed. The download process could not complete. | Check your network connection and try again. | ||
| 99992501 | Install or Upgrade | Failed | Installation failed. Invalid package type. | Use a different package type to upgrade this Agent, for example MSI and not EXE.ORConfigure a network share to grab certificate updates in firewalled and offline scenarios (see Microsoft instructions). See How To Solve an Invalid Signature Error. | ||
| 99992502 | Install or Upgrade | Failed | Installation failed. Corrupt package. | Download the package from the Management Console again. | ||
| 99992503 | Install or Upgrade | Failed | Installation failed. Invalid signature. | Download the package from the Management Console again. | ||
| 99992504 | Install or Upgrade | Failed | Installation failed. File not found. | Make sure that the file exists in the path you specified for the upgrade file. | ||
| 99992505 | Install or Upgrade | Failed | Installation failed. Unexpected error. | |||
| 99992506 | Install or Upgrade | Failed | Unknown status. | |||
| 9999600 | Upgrade | Expired | If the Agent version change task is in progress for 30 minutes with no update received from the endpoint, the task is marked as Expired to make the resources available. | Make sure the endpoint can communicate with the Management. When the endpoint sends an update, the task will change automatically from Expired to the current state. | ||
| 9999601 | Upgrade | Expired | The endpoint is decommissioned. |