BoardForge AI installer handling
Installer Return Codes
This page documents the BoardForge AI standalone EXE installer behavior used for Microsoft Store package validation. The installer supports silent installation with /S and does not require sign-in during installation.
Package details
- Current package
- BoardForgeAI-Setup-0.1.0-x64.exe
- Architecture
- x64
- Silent install
- BoardForgeAI-Setup-0.1.0-x64.exe /S
- Silent uninstall
- BoardForgeAI-Setup-0.1.0-x64.exe /S /uninstall
- SHA256
- 0248270A648E81A4056C000A3334B53C226DB88B771B9FACE1798494F9128A29
- Signing status
- Unsigned controlled-release package; production release requires Authenticode or Microsoft Trusted Signing.
Standard install scenarios
| Scenario | EXE return code | Meaning |
|---|---|---|
| Installation canceled by user | 1 | The installer did not complete. The user or calling process cancelled installation. |
| Application already exists | 0 | The installed version is already present or the install target is already current. |
| Installation already in progress | 1 | Another installer operation is running. Retry after the active install completes. |
| Disk space is full | 1 | The installer could not write the local BoardForge payload. Free disk space and retry. |
| Reboot required | 0 | BoardForge does not require a reboot for normal install. If Windows requests one externally, the app is still installed. |
| Network failure | 1 | The installer is offline and does not download payloads. A network failure usually means the package URL could not be downloaded before launch. |
| Package rejected during installation | 1 | Windows or device policy blocked the unsigned or untrusted package. Use a signed installer for production distribution. |
| Installation successful | 0 | BoardForge AI installed successfully. |
Miscellaneous failures
Any unclassified install failure returns 1. Review Windows security policy, disk permissions, package integrity, and Authenticode signing status before retrying.
Installer signing note
The current package is installer-ready but unsigned. A production Microsoft Store submission should use a CA-trusted Authenticode certificate or Microsoft Trusted Signing before final validation.