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.

Verify the exact installer and first launch

The project changelog records signed 1.1.11 and 1.1.12 releases after product-owned optimizer, fitness, money-management, commission, and related runtime defaults were added. It also records a validated Python Research Runtime and WebView2 prerequisite initialization in the signed 1.1.12 MSI.

Those project release records are not an independent certification of the installer currently offered for download. Verify its Windows digital signature, confirm the installed version in Help > About, and confirm first-launch compilation and module discovery before relying on Validator, Optimizer, or Research Lab. If a required module is missing, collect diagnostics and contact support; do not download or import an untrusted module as a workaround. Research Lab remains a Preview feature even when its runtime is installed correctly.

Update​

HyperionX checks its update policy during startup and through Help > Updates. Older builds can direct you to a browser download; the reviewed 1.1.27 source includes the download-and-verify workflow below. Check the documentation version map and Help > About for the installed build.

For an optional update:

  1. Save open work and stop active strategies before accepting installation.
  2. Select Help > Updates and review the version and release information.
  3. Accept the update to download the MSI. HyperionX validates its SHA-256, Windows publisher signature, product identity, and version before launching it.
  4. Approve the Windows installer prompt. After launching the installer, HyperionX closes so the installer can update the application.

When the policy requires a newer minimum supported version, an older installation cannot complete startup. The required-update prompt offers download/verification or exit. A failed download or verification does not launch the installer; retry or exit. A previously verified cached policy can still require an update when the policy endpoint is unavailable.

In the reviewed 1.1.27 source, an unavailable policy endpoint can also block startup when the last successful policy check is more than 24 hours old, or no valid prior check exists. Within that offline grace period, startup can continue unless the cached policy requires an update. Outside it, use Retry after restoring connectivity or exit, even if the installed version may still be supported.

Updates do not silently replace the running application. If the installed build instead opens a download page, follow that release's manual installation flow and verify the downloaded installer's Windows signature before running it.

Bundled Custom Script Synchronization​

The reviewed desktop source includes a startup synchronizer that 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.

Confirm this synchronization behavior with the exact installed build. Source presence does not prove that a particular downloaded installer contains or enables it.

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. HyperionX data can remain in these user-profile roots:

LocationNotable retained data
Documents\HyperionXMain database, connections, custom scripts, workspaces, logs, chart images, research/validation data, reports, and exports.
%APPDATA%\HyperionXAI/Rion license and settings state, protected chat history, Agent Builder profiles, Local Desktop API audit logs, Trade Copier configurations and reconciliation journal, OCO presets, and update-check state.
%LOCALAPPDATA%\HyperionXCode Lab terminal/WebView2 data, Research Runtime, WalletConnect sessions, Marketplace device/session state, recent instruments, application user settings, and provider/UI caches.
%TEMP%\HyperionX\CodeLab\WebView2A temporary Code Lab WebView2 fallback that can be used when the normal local-app-data folder is unavailable.

Some security-sensitive subpaths deserve separate attention:

  • %APPDATA%\HyperionX\AIAgent can contain protected cloud/license state, AI settings, chat history, readable Agent Builder profiles, and Local Desktop API audit records.
  • %APPDATA%\HyperionX\TradeCopier contains copier configurations and reconciliation state.
  • Signed 1.1.12-era Code Lab builds can place the Local Desktop API bearer token in %LOCALAPPDATA%\HyperionX\CodeLab\Terminal\hpx-codelab-profile.ps1. The reviewed post-1.1.12 development build no longer serializes the token there, but an older profile can remain after upgrade; inspect it before sharing or retaining the directory.
  • %LOCALAPPDATA%\HyperionX\WalletConnect contains DPAPI-protected mainnet and testnet WalletConnect session files.
  • %LOCALAPPDATA%\HyperionX\Marketplace can contain Internal Marketplace device-connection state.
  • %LOCALAPPDATA%\HyperionX\RecentInstruments.json contains the recent-instrument list and provider identifiers.

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 all four locations in the table. Close the wallet worker before removing WalletConnect data, and close Code Lab and its terminal before removing Code Lab data.
  5. Remove only the exact HyperionX files or roots you intentionally want to discard. Deleting %APPDATA%\HyperionX or %LOCALAPPDATA%\HyperionX resets all listed features in that root, not just one feature.
  6. If the Code Lab terminal token profile existed, restart HyperionX so an app-generated token changes. If HYPERIONX_RION_LOCAL_TOKEN supplied a stable token, rotate that user environment value separately; deleting the profile does not revoke it.

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.