Motrix 2.0.0-beta.51

English | 简体中文

Motrix 2.0.0-beta.51 enables Windows legacy BitTorrent recovery with the bundled
aria2 1.37.0-motrix.18, fixes Windows task paths and closing animations, and adds
terminal-based Extension pairing for Server operators.

Highlights

• Windows can activate imported legacy BT tasks using native checkpoint and
  torrent metadata recovery. The bundled aria2 1.37.0-motrix.18 provides the
  required capabilities; the app preserves path identity, original file
  selection, durable authorization, and recovery after a lost response or
  restart. Native Windows consumer tests passed on Windows 2022 x64 and
  Windows 2025 x64/ia32; the Motrix desktop package remains x64 only
  (#2397,
  #2399).
• Windows task paths use consistent native separators when displayed or copied.
  Opening files and revealing them in Explorer handles repeated separators,
  drive roots, and UNC paths, including existing task records
  (#2395).
• Closing menus, dialogs, and task forms preserves their visible content and
  dimensions through the exit animation while immediately disabling actions.
  Switching activity charts between recent and lifetime ranges no longer
  replays the previous scale animation on the next sample. Rapidly reopened
  plugin input dialogs reject stale file preparation results
  (#2396).
• Server Extension pairing no longer requires MOTRIX_PUBLIC_URL when the
  WS/WSS endpoint is fully configured. An authenticated operator can use
  motrix-admin extension pair in an interactive local terminal to select a
  pending request and view its short-lived code. Users still enter the code in
  the Extension to authorize pairing. Redirected/JSON code output is refused;
  Web delivery retains its HTTPS or explicit HTTP-consent requirements.
  Operator CLI translations also avoid duplicating complete application
  catalogs in the Server bundle
  (#2400).

Before testing

Back up the v1 profile and downloads, close the old app, and review the selected
tasks. Migration imports paused records and does not start transfers or change
original files. BT activation requires the original torrent metadata, original
file selection and directory, and explicit authorization. Existing pieces are
checked before transfer; after a restart, explicitly resume the paused task.

Windows progress recovery requires a local fixed NTFS volume and appropriate
file ownership and permissions. Network shares, FAT/exFAT, junctions, symlinks,
cloud reparse points, hard-linked files, alternate data streams, and aliased
paths are refused. HTTP records still download into a separate directory; the
assistant does not reuse historical HTTP bytes in place. See the
migration guide
for the exact requirements and recovery behavior. Retain the engine's
pre-schema5 database backup when upgrading.

Explorer behavior on a real Windows SMB share and native fnOS acceptance remain
unverified. Full Chromium Extension download-submission E2E still encounters a
baseline download.rejected failure with the available production Extension;
this release does not claim that suite passes. Server protocol and real HTTP
pairing/reconnect tests passed.

After the protected Snap workflow completes, install the strictly confined build
with sudo snap install motrix --edge. Installations tracking latest/edge
should upgrade to the beta.51 revision set.

Planned downloads after release gates pass

After every container gate passes, use
docker.io/motrixapp/motrix-server:2.0.0-beta.51 or
ghcr.io/agalwood/motrix-server:2.0.0-beta.51. See the
Docker Server guide
for storage, networking, and upgrades.

Distribution notes

• Flatpak bundles use application ID app.motrix.native and the beta branch.
  Install each new bundle with flatpak install --user --or-update; these files
  do not configure a Motrix update remote. Update the Native Host companion
  separately. See the Flatpak guide.
• AppImage desktop integration remains opt-in. Browser cold launch requires the
  separately enabled Native Messaging host and a registered AppImage path;
  reconnecting to a saved pairing also requires a compatible Extension.
• Windows arm64 and all 32-bit app packages are unavailable. Windows packages
  are unsigned and may trigger SmartScreen; use the official published GitHub
  prerelease.
• Beta container tags are immutable and do not change latest, stable, or
  other stable-channel aliases. Snap publication updates latest/edge only.

Feedback

Report reproducible problems through
GitHub Issues, including your OS,
architecture, package type and reproduction steps.

What's Changed

• fix(downloads): normalize windows task output paths by @agalwood in #2395
• fix(ui): prevent overlay exit flicker and chart range replay by @agalwood in #2396
• fix(legacy-import): enable native windows checkpoint activation by @agalwood in #2397
• chore(engine): bundle verified aria2 motrix.18 release by @agalwood in #2399
• fix(server): allow terminal extension pairing without web url by @agalwood in #2400
• chore(release): prepare 2.0.0-beta.51 by @agalwood in #2401

Full Changelog: v2.0.0-beta.50...v2.0.0-beta.51