Bitdefender Installation Troubleshooting – Exit Codes

Bitdefender Installation Troubleshooting - Exit Codes

https://www.bitdefender.com/support/troubleshooting-best-unsuccessful-deployments-1550.html#winlnk

Exit codes are the “install status” of the installation. They indicate success or reason of failure of the installation.

Exit Codes show up in the Agent Procedure Logs for machines. Agent Procedure logs are located under Agent – Agents – Agent Logs – Agent Admin Logs – Procedure History.

Most Common Codes:

0, 183, 16 = Installation was successful!
1= Uninstall failed
31 = Uninstalling a competitor product failed. Manually remove previous AV, reboot, & retry the installation
86 = Uninstall fail due to password protection or no password provided.
101 is a more exotic (rare) BD installer exit code, which appears when the installer cannot copy the files into the installation folder.
Since the error is quite rare, it would be useful for us to have some logs from any of the machines which encountered it.
Here’s the KB on how to extract the required info:https://www.bitdefender.com/business/support/en/77209-90394-use-the-support-tool-log.html#UUID-7fc6466e-73f3-9c59-ab5e-77f38aecac76_UUID-6fdf7fdc-b9fc-74b4-b050-4b4f39db2377(see section Generate Support Tool log).
112 = Installation failed, not enough disk space
3010, 16003 = Successful maintenance/step; reboot required to complete installation.
3017 = Competitor AV found / installation halted. No auto removal of competitor attempted. Remove previous AV, reboot, & retry the installation. Also try a GZ BD installation package.
1627 = This is a general error, and is not listed in the above doc. The BD installer crashing. Could be an infection, security software of some kind, or an issue with the OS. Please attempt to clean-up the machine, removing any traces of Bitdefender from the registry and temp directories, sfc scan, etc.

16003 = installation package present, but previous try failed.
1633 = OS version not supported

16000 = failed to download package (security-based)
16001 = download failure – config file (was machine offline?)
16002 = Installer extraction failed
16003 = installation package present, but previous try failed.
16004 = Installer setup failed
16005 = OS Version not supported
16010 = Product not installed
16021 = RMMT Download failed. RMMT could not be downloaded: the file might be present on disk, but the size/contents indicate a download failure. Try again.
16022 = RMMT missing. RMMT is not present in the kworking folder
16023 = RMMT Invalid Version. The RMMT version is not updated to the latest. Make sure the VSA BD module is up to date and try again.
16024 = RMMT Invalid signature. Generic invalid signature code. Make sure the VSA BD module is up to date and try again.
16026 = Operation not supported. The procedure tried to us RMMT to run an unsupported operation.
16100 = Procedure failure. Generic code for unexpected failures
17000 = No signature or invalid subject or issuer. This is a Certificate issue on the machine. Follow the steps in this article: https://www.bitdefender.com/business/support/en/77209-79896-troubleshooting.html#UUID-00f7f52f-8cd4-b01b-a851-b5a4f1c0a517
17001 = Powershell not Found
17002 = Certificate chain validation failed. This is a Certificate issue on the machine.