Skip to main content

Install, Update, And Uninstall

This page describes the current Windows desktop installation and update behavior.

Requirements​

The public desktop package is built for:

  • 64-bit Windows on an x64 processor.
  • A Windows account that can approve a per-machine installation.
  • Microsoft Edge WebView2 Runtime for embedded web content.
  • Internet access for licensing, provider connections, update checks, and cloud-backed features that you choose to use.

The main application package includes its required .NET runtime. The installer checks for WebView2 and may install the Microsoft runtime when it is missing.

Specific brokers, exchanges, data providers, or custom scripts can have additional requirements.

Before Installing​

  1. Download HyperionX only from the official release location.
  2. Check the file's Windows Digital Signatures properties before running it.
  3. Back up Documents\HyperionX before an upgrade when it contains custom scripts, presets, research results, or other work you cannot replace.
  4. Close HyperionX, Code Lab, Research Lab, and related worker processes.
  5. Keep a record of any provider-specific recovery information. Never place API secrets or wallet private keys in the documentation backup.

Install​

  1. Run the signed HyperionX installer.
  2. Approve the Windows administrator prompt.
  3. Allow the prerequisite step to install WebView2 if Windows does not already have it.
  4. Complete the setup and launch HyperionX.
  5. On first launch, wait for custom-script initialization to finish.
  6. Open Logs if a custom script or research module does not compile.

The application is installed under the 64-bit Program Files area. User-created data is stored separately from the application directory.

Candidate research packaging still requires validation

The active release-candidate source contains a candidate fix: product-owned default optimizer, fitness, money-management, and commission modules are registered independently of the custom assembly, and the installer manifest includes the bundled research-extension sources. This source and manifest evidence is not proof that the released installer works on a clean machine.

Treat Validator backtests and Optimizer as unavailable on a fresh public installation until the exact clean, signed installer artifact passes installation, first-launch compilation, discovery, and workflow smoke tests. Research Lab remains Preview and also requires validation of its separately packaged runtime prerequisites. Do not download or import untrusted modules as a workaround.

Update​

HyperionX can check an update manifest during startup and from Help > Updates. When a newer version is available, the application displays release information and opens the download page in your browser if you accept.

The current update flow:

  • Does not download or install the update inside HyperionX.
  • Does not automatically replace the running application.
  • Treats a manifest marked required as a warning; it does not force installation.
  • Does not use the manifest's checksum as an in-app installer verification step.

Download the new installer from the official release page and verify its Windows signature before running it.

Bundled Custom Script Synchronization​

The active release-candidate startup synchronizer tracks product-bundled custom sources and the bundled custom assembly in %USERPROFILE%\Documents\HyperionX\Bin\Custom. This is independent of whether that custom project already contains user files:

  • A missing bundled file is installed.
  • An unchanged product-managed file is updated in place when the bundle changes.
  • A file changed by the user is preserved. The incoming product version is written beside it with an .hpx-update suffix.
  • Product ownership and hashes are recorded in .hyperionx-bundle-state.json at the custom-project root.

Do not edit or delete the state file as a normal update step. If an .hpx-update file appears, compare it with the working file, back up your version, merge or accept the intended changes deliberately, and compile the complete custom project. The side-by-side preview is not an active replacement by itself. Review Logs for the installed, updated, and preserved-user-edit counts.

This synchronization behavior exists in candidate source; it must still be verified with the exact clean, signed installer described above.

Upgrade Checklist​

  1. Save open work and stop active strategies.
  2. Back up Documents\HyperionX.
  3. Close all HyperionX windows and workers.
  4. Run the newer signed installer.
  5. Launch the application and confirm the displayed version in Help > About.
  6. Compile custom scripts and open a saved workspace.
  7. Confirm provider connections, Validator presets, and research data before deleting the backup.

Do not assume that an older installer can safely downgrade data created by a newer version. Keep the backup until the upgrade is verified.

Uninstall​

Use Windows Installed apps or Apps & features to uninstall HyperionX.

The standard uninstall removes installed program files. It does not provide a secure-delete or “remove all user data” option. User-created content can remain in locations such as:

  • Documents\HyperionX
  • %LOCALAPPDATA%\HyperionX\ResearchRuntime
  • %LOCALAPPDATA%\HyperionX\WalletConnect, including DPAPI-protected mainnet and testnet WalletConnect session files
  • %LOCALAPPDATA%\HyperionX\Marketplace, including the Internal Marketplace device-connection state

This retention helps preserve custom scripts and research work across reinstallations. It also means uninstalling the application is not the same as erasing user data.

If you want a complete local reset:

  1. Export or back up anything you need.
  2. Uninstall HyperionX.
  3. Confirm every HyperionX process is closed.
  4. Review the exact folders above. Close the wallet worker before removing WalletConnect data.
  5. Remove only the HyperionX data you intentionally want to discard.

Deleted research datasets, custom scripts, exports, logs, and local session state may not be recoverable. Removing a local WalletConnect or Marketplace file does not revoke provider-side sessions, wallet approvals, agents, orders, or positions. Perform remote revocation and account reconciliation separately. Normal file deletion is not guaranteed to securely erase data from the storage device or backups.

Reinstall Versus Reset​

A reinstall can repair installed program files while retaining user data. It may not fix a problem caused by a custom script, saved workspace, local runtime, or user setting.

Before deleting all data, use Support And Diagnostics to export logs and identify the failing component.