Download and updates

Get the official release from support. Follow the instructions below for a new installation or an existing setup.

Software delivery and updates

TongPin FX for Windows

The public download will appear after its version and location are confirmed, together with file size, release notes and a SHA256 checksum.

Published version
Contact support
Platform
Windows desktop
Download address
Contact support
Checksum / file size
Published with the release
The download action will be enabled once publication is confirmed. Back up your original folder before upgrading. Public packages contain no customer account data.

First installation

  1. Use the confirmed release package

    Obtain the file from the official release location, check its version and checksum, and follow the instructions for a writable application folder.

  2. Check your environment

    Use a stable network and a supported Windows environment. Refer to the release instructions for runtime and system requirements.

  3. Activate and connect your accounts

    Follow the activation and connection instructions. Product licensing and broker/account access are separate requirements.

  4. Verify the copying rules first

    Check sizing, symbols, direction, SL/TP and actual responses in a demo environment before further use.

Updating an existing setup

Follow the instructions for the specific upgrade. Preserving account data matters more than copying a file into an arbitrary directory.

  1. Find your existing application folder

    Use your current shortcut or the app working directory to avoid upgrading an unrelated empty folder.

  2. Back up and exit the old version

    Back up the complete original folder and exit the old application before replacing files.

  3. Replace only the specified program files

    Retain db, config, diagnostics, account and licensing data. Follow the release instructions for any files with matching names.

  4. Launch and verify

    Check the version, accounts, copying relationships and settings. Keep the backup and logs if anything differs.

Public upgrade packages must contain no other customer's accounts, passwords, databases, licence caches or personal settings. Compatibility is verified between specific versions, not arbitrary folders and files.

Release notes

Published notes will describe feature changes and upgrade impact, rather than vague claims of comprehensive improvement.

  • Features and workflows

    See what changed in the controls, manual actions and automatic workflows.

  • Compatibility and data continuity

    See the verified compatibility of account passwords, settings, licensing and previous versions.

  • Validation and file integrity

    Distinguish isolated tests from runtime and broker results, and check the package checksum.

Application folders and backups

Locate account, configuration and licensing data before replacing files.

Read the upgrade FAQ

↑ ↓ Select · Enter Open · Esc Close

Software interface illustrations
Offline demonstration of the Chinese-language application