[Bug]: Installer fails to run, creates and deletes a temporary folder immediately

[nadidazwad]

Version

Version 0.4.7.1 (Official Build, Chromium 140.0.7339.185) (64-bit)

Have you tested that this is not an upstream issue or an issue with your configuration?

• I have tried reproducing this issue in Chrome and it could not be reproduced there
• I have tried reproducing this issue in ungoogled-chromium and it could not be reproduced there
• I have tried reproducing this issue in Helium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there

Description

When attempting to run the manual installer for the Helium browser, the process fails immediately. Instead of launching the installation wizard and updating my browser, a temporary folder (In the downloads folder where I run the installer) briefly appears and is then deleted. The browser remains unupdated. I have already tried common troubleshooting steps, including running the installer as an administrator.

How to Reproduce?

1. Navigate to the official Helium browser GitHub repository releases page.
2. Download the latest installer executable for Windows (e.g., helium-browser-installer-win64.exe).
3. Right-click the downloaded file and select "Run as administrator".
4. Observe the behavior. A temporary folder is created in the user's Temp directory and quickly removed. No installation wizard appears.

Actual behavior

The installer fails silently, creating and deleting a temporary folder, and no update occurs.

Expected behavior

The installer should launch a setup wizard, allowing the user to proceed with the installation or update process.

Additional context

[nadidazwad]

Inside the Temp Folder:

[Martyrer]

@nadidazwad I noticed that if you close the helium after the folder is created - the browser will update itself and remove the folder. I do not think that this is the expected behavior, but still, you can use this as a workaround for now.

Probably this is something related to the auto-update functionality; other chromium-based browsers update themselves in a similar manner, here tho this is a half-manual process atm.

[boopboopboop]

$\text why tf does this browser not have auto update^{why tf does this browser not have auto update}$

[mickes66]

Exactly the same thing happens to me i latest Win 11.