Setupidity validates authoring input before replacing the requested output. Start with the error name and the exact command that produced it.
The usage line appears instead of a build
The command is missing build, a required option, an option value, or a paired --message; or it contains an unknown option. Compare the invocation with the CLI reference. In PowerShell, keep the backtick as the last character on a continued line.
Invalid payload or shortcut target
--payload must name an accessible directory. Shortcut targets are relative to that directory, must resolve to an included .exe, and cannot escape with ... Stage the payload first and inspect its exact paths before authoring shortcuts.
Output already exists
Choose another --output or add --force. Replacement is atomic: Setupidity writes a complete temporary package before renaming it over the destination. Do not delete a known-good MSI merely to retry a failed build.
The MSI builds but does not install as expected
Reproduce on Windows with verbose logging:
msiexec /i dist/app.msi /l*v dist/install.log
For a silent install, add /qn. Confirm elevation, launch-condition properties, the target Windows architecture, free disk space, and code-signing policy. A successful build proves package construction, not application compatibility.
Prepare a support request
Include the Setupidity version, authoring host, complete command with secrets removed, exact error output, and a minimal payload or reproduction. Never send private keys or proprietary files without an agreed secure transfer route. See Support.
Previous: Platforms · Next: Documentation index