Error 1722
There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected.
The package ran a helper program during installation and that program failed. The MSI itself is usually fine; something it depended on was not available.
What it actually means
Installers frequently run custom actions: registering a service, configuring a database, launching a setup helper. Error 1722 means one of those returned a failure, so the cause lies in what the custom action was trying to do rather than in the package format.
How to fix it, in order
Ordered by how often each one is the answer, not by how clever it sounds.
- 01Run the installer as administrator. Custom actions often need elevation that the launcher did not request.
- 02Produce a verbose log with "msiexec /i package.msi /l*v install.log" and search for "return value 3". The line above names the custom action that failed, which is the actual problem.
- 03Check the prerequisites. Many custom actions call out to .NET, a Visual C++ runtime or a database client, and fail silently when it is absent.
- 04Temporarily disable antivirus, since blocking a helper executable mid-install produces exactly this.
- 05If it is a service registration failure, confirm no previous version of the service is still installed and running.
Common questions
- What does error 1722 mean?
- A helper program that the installer ran as part of setup failed. The package itself is normally fine. Produce a verbose log and search for "return value 3" to find which action failed and why.
Before you retry the installer
If the package came from anywhere other than the publisher, confirm it is the file they actually shipped. Check its SHA-256 against our index, which settles in seconds whether you are debugging an installer or a damaged download.