FOLDPAIR / RELEASE 0.2.501
Foldpair 0.2.501
Get the update.
Get Foldpair 0.2.501 for your devices.
Download FoldpairChoose a platform · Version 0.2.501
- Windows
- macOS · Apple Silicon
- macOS · Intel
- Linux · x64
- Linux · ARM64
- Android
- iPhone / iPadNot available for this release
WHAT’S NEW
A quick look at this update
Foldpair 0.2.501 packages the latest documented beta improvements across relay resilience, network fallback, storage, and encrypted sync.
Full release notes
Highlights
- Windows setup now retries transient legacy-tree file locks.
After stopping the obsolete updater, both Setup and the one-line installer retry removal of its LocalAppData application tree for up to 15 seconds. A short-lived archive or process handle can no longer turn a successful updater shutdown into an immediate restart-required installation failure.
- After stopping the obsolete updater, Setup and the one-command installer retry removal of its LocalAppData application folder for up to 15 seconds. This gives temporary file locks time to clear before the installer reports that removal failed.
Pages reached through the CIS mirror now show mirror-hosted one-line installer URLs, and /get.ps1 plus /get.sh default their release-feed requests to that same mirror ingress and use the mirror artifact URL returned by the feed. Mirror deployment and release verification reject either script if it contains a primary-domain dependency.
- Windows upgrades now retire even an already-running legacy beta updater.
Setup disables and removes the old scheduled task, terminates its active PowerShell/VBS process tree, verifies the scheduled task is actually absent, and refuses to continue if the obsolete LocalAppData application copy cannot be removed. This closes the race that could restore and launch an old beta one second after a successful Program Files installation while preserving settings and synced folders.
- One-command Windows upgrades handle running beta clients
The PowerShell flow downloads a clearly named installer, closes running launcher and agent processes, waits for Setup, checks the installed version, and opens its launcher from Program Files. Packaging also checks launcher and agent FileVersion values against the installer version to help catch stale components.
Fixes
- Windows setup now retries transient legacy-tree file locks. After stopping the obsolete updater, both Setup and the one-line installer retry removal of its LocalAppData application tree for up to 15 seconds. A short-lived archive or process handle can no longer turn a successful updater shutdown into an immediate restart-required installation failure.
- RecruitLead download instructions no longer depend on the primary domain. Pages reached through the CIS mirror now show mirror-hosted one-line installer URLs, and /get.ps1 plus /get.sh default their release-feed requests to that same mirror ingress and use the mirror artifact URL returned by the feed. Mirror deployment and release verification reject either script if it contains a primary-domain dependency.
- Windows upgrades now retire even an already-running legacy beta updater. Setup disables and removes the old scheduled task, terminates its active PowerShell/VBS process tree, verifies the scheduled task is actually absent, and refuses to continue if the obsolete LocalAppData application copy cannot be removed. This closes the race that could restore and launch an old beta one second after a successful Program Files installation while preserving settings and synced folders.
- Windows one-line upgrades now complete cleanly over running beta clients. The PowerShell flow downloads a recognisably named installer, closes existing launcher and agent processes, waits for setup to finish, verifies the installed binary version, and explicitly opens the matching launcher from Program Files. The release packager also rejects stale launcher or agent payloads whose FileVersion does not match the installer version, so a current filename cannot conceal old application bytes.
- One-command Windows upgrades handle running beta clients. The PowerShell flow downloads a clearly named installer, closes running launcher and agent processes, waits for Setup, checks the installed version, and opens its launcher from Program Files. Packaging also checks launcher and agent FileVersion values against the installer version to help catch stale components.
- Folder and account contention can be isolated. The optional sharded lock manager separates write contention by folder and account. A fair-share throttle slows an overactive account, and per-account lock metrics are available on /metrics. These controls reduce the risk that one account delays the rest of the service.
- PostgreSQL is now a supported metadata backend for the relay (selectable by configuration), alongside the existing SQLite store which remains the default for local and self-hosted use. Includes a one-shot SQLite→Postgres data migration tool with row-count reconciliation.
- Support for Cloudflare R2 and S3-compatible blob storage. The relay can store encrypted blobs in R2 and provide presigned downloads. Storage health checks and a global storage cap help detect failures and limit usage. The integration was tested with an S3 server.
- Storage maintenance can run after startup. The startup storage audit can run after the server begins listening, allowing health checks to respond while storage cleanup continues. FOLDPAIR_STARTUP_AUDIT_MODE selects background (the default), off, or blocking for the earlier pre-listen behaviour.
- End-to-end encryption for synced folders and clipboard. File contents are encrypted on the sending device with AES-256-GCM in authenticated frames before upload. Folder keys are delivered to devices in sealed ECDH envelopes; the relay has no unwrapped content keys. Clipboard items are encrypted per event with the account key. For these protected payloads, the relay stores ciphertext without a decryption path. Uploads wait if a participating device does not yet support E2E, so update every device in the folder before transfers resume. Clipboard E2E has been enabled by default since 2026-06-15.
- Remote file access hardened alongside folder encryption.
Known issues (1)
Known issues
- macOS beta packages are unsigned and not notarized; follow the documented Gatekeeper first-launch steps.
Checksums and verification
- Windows
177f53e2149bfcd2d5f1f36e37d060d983208f0c0c535a90d70c6dcc24e1fb39 - macOS · Apple Silicon
3c5c187e066bf307938b45a70faf775746a077d8aa0283c55d33d752627db4ca - macOS · Intel
973556d6b9435b13edeea966778b51da82f5fc26b03317dac424d005821ea67d - Linux · x64
9a3935d54af131fad3598b2a0e84b1f607e45790c79a2928a9607e1007479da8 - Linux · ARM64
f5c31441d67a54dfa9c9d4a5b22ad7c2fb69c295552d0607da5ca1b4d0e8ea1c - Android
47d5bcb6feb8ee2f7b0e525fefb9fc6c411029515f22ee6e94c191e00230c31f
GET THE UPDATE
Update your other devices.
Download Foldpair 0.2.501 for each of your devices.
Download FoldpairChoose a platform · Version 0.2.501
- Windows
- macOS · Apple Silicon
- macOS · Intel
- Linux · x64
- Linux · ARM64
- Android
- iPhone / iPadNot available for this release