In SpikerSoft Stacker, the “Salir e Instalar” button (Close and Update) fails to properly execute the update process. When pressed, the app launches a system batch or console window that closes unexpectedly after a few seconds, leaving the user on the same update screen without completing the installation.
Issue Description
The update dialog correctly detects and downloads the latest version (e.g., spikersoft-stacker-2026.10.04i-setup-windows-x86_64.exe). However, when the user clicks Salir e Instalar, the installer fails to run due to insufficient privileges or improper elevation handling. The console returns the error:
The requested operation requires elevation. (os error 740)
This indicates that the update process requires administrative privileges but does not request them automatically, causing the update to abort silently.
Environment
Property
Value
Application
SpikerSoft Stacker
Module
Auto-Update / Installer
Environment
Production
Platform
Windows
Operating System
Windows 11
Version
v2026.09.28a → v2026.10.04i
Device
Desktop
Preconditions
User has downloaded the latest update and clicks Salir e Instalar from the update dialog.
Steps to Reproduce
Launch SpikerSoft Stacker.
Wait for the update prompt to appear.
Click Salir e Instalar.
Observe that a console window opens briefly and closes without completing installation.
The app remains on the same update screen.
Expected Result
The app should close gracefully.
The installer should launch with proper elevation (admin privileges).
The update should complete successfully, replacing the old version.
Actual Result
Console window opens and closes unexpectedly.
Update process fails silently.
User remains on the same version.
Evidence
Screenshot shows the update dialog with the error message: The requested operation requires elevation. (os error 740)
The downloaded installer path is verified but not executed.
Impact
Prevents users from updating the app automatically.
Requires manual installation via file explorer.
Reduces reliability of the auto-update system.
Frequency
Always
Reproducibility
100%
Severity
High
Suggested Fix
Modify the update script to request administrator privileges when launching the installer.
Use Windows API or manifest configuration to trigger elevation automatically.
Add error handling and user feedback (e.g., “Please run as administrator to complete the update”).
Verify that the app closes before executing the installer to avoid file lock conflicts.
## Summary
In **SpikerSoft Stacker**, the **“Salir e Instalar”** button (Close and Update) fails to properly execute the update process. When pressed, the app launches a system batch or console window that closes unexpectedly after a few seconds, leaving the user on the same update screen without completing the installation.
## Issue Description
The update dialog correctly detects and downloads the latest version (e.g., `spikersoft-stacker-2026.10.04i-setup-windows-x86_64.exe`). However, when the user clicks **Salir e Instalar**, the installer fails to run due to insufficient privileges or improper elevation handling. The console returns the error:
> `The requested operation requires elevation. (os error 740)`
This indicates that the update process requires administrative privileges but does not request them automatically, causing the update to abort silently.
## Environment
| Property | Value |
|-----------|--------|
| Application | SpikerSoft Stacker |
| Module | Auto-Update / Installer |
| Environment | Production |
| Platform | Windows |
| Operating System | Windows 11 |
| Version | v2026.09.28a → v2026.10.04i |
| Device | Desktop |
## Preconditions
User has downloaded the latest update and clicks **Salir e Instalar** from the update dialog.
## Steps to Reproduce
1. Launch **SpikerSoft Stacker**.
2. Wait for the update prompt to appear.
3. Click **Salir e Instalar**.
4. Observe that a console window opens briefly and closes without completing installation.
5. The app remains on the same update screen.
## Expected Result
- The app should close gracefully.
- The installer should launch with proper elevation (admin privileges).
- The update should complete successfully, replacing the old version.
## Actual Result
- Console window opens and closes unexpectedly.
- Update process fails silently.
- User remains on the same version.
## Evidence
- Screenshot shows the update dialog with the error message:
`The requested operation requires elevation. (os error 740)`
- The downloaded installer path is verified but not executed.
## Impact
- Prevents users from updating the app automatically.
- Requires manual installation via file explorer.
- Reduces reliability of the auto-update system.
## Frequency
Always
## Reproducibility
100%
## Severity
High
## Suggested Fix
- Modify the update script to request **administrator privileges** when launching the installer.
- Use Windows API or manifest configuration to trigger elevation automatically.
- Add error handling and user feedback (e.g., “Please run as administrator to complete the update”).
- Verify that the app closes before executing the installer to avoid file lock conflicts.
Confirmed and fixed in the stacker repo: spikersoft-stacker#984, PR fix/windows-update-elevation.
Root cause: the app started the installer in a way that can never ask for administrator rights, while the installer requires them, so Windows refused with error 740 instead of showing the UAC prompt. The console window that flashed was the signature check.
After the next shipped release:
updating from the version you have now will show one UAC prompt, then install and relaunch Stacker;
on the new version, declining the prompt leaves the app open with a message instead of closing it.
Please re-test from your current install once the release is out; I'll close this ticket after that.
Confirmed and fixed in the stacker repo: spikersoft-stacker#984, PR `fix/windows-update-elevation`.
Root cause: the app started the installer in a way that can never ask for administrator rights, while the installer requires them, so Windows refused with error 740 instead of showing the UAC prompt. The console window that flashed was the signature check.
After the next shipped release:
- updating from the version you have now will show one UAC prompt, then install and relaunch Stacker;
- on the new version, declining the prompt leaves the app open with a message instead of closing it.
Please re-test from your current install once the release is out; I'll close this ticket after that.
Closing: fix is spikersoft-stacker#984 / PR #985 and ships with the next release. If the update still fails after that release, reopen with a screenshot.
Closing: fix is spikersoft-stacker#984 / PR #985 and ships with the next release. If the update still fails after that release, reopen with a screenshot.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
In SpikerSoft Stacker, the “Salir e Instalar” button (Close and Update) fails to properly execute the update process. When pressed, the app launches a system batch or console window that closes unexpectedly after a few seconds, leaving the user on the same update screen without completing the installation.
Issue Description
The update dialog correctly detects and downloads the latest version (e.g.,
spikersoft-stacker-2026.10.04i-setup-windows-x86_64.exe). However, when the user clicks Salir e Instalar, the installer fails to run due to insufficient privileges or improper elevation handling. The console returns the error:This indicates that the update process requires administrative privileges but does not request them automatically, causing the update to abort silently.
Environment
Preconditions
User has downloaded the latest update and clicks Salir e Instalar from the update dialog.
Steps to Reproduce
Expected Result
Actual Result
Evidence
The requested operation requires elevation. (os error 740)Impact
Frequency
Always
Reproducibility
100%
Severity
High
Suggested Fix
Confirmed and fixed in the stacker repo: spikersoft-stacker#984, PR
fix/windows-update-elevation.Root cause: the app started the installer in a way that can never ask for administrator rights, while the installer requires them, so Windows refused with error 740 instead of showing the UAC prompt. The console window that flashed was the signature check.
After the next shipped release:
Please re-test from your current install once the release is out; I'll close this ticket after that.
Closing: fix is spikersoft-stacker#984 / PR #985 and ships with the next release. If the update still fails after that release, reopen with a screenshot.