-
v1.7.46 Stable
Administrator released this
2026-03-08 02:49:23 +01:00 | 432 commits to main since this release- Prefer Rar.exe over UnRAR.exe for native RAR extraction\n- Add deeper per-attempt extractor error logging
Downloads
-
v1.7.45 Stable
2026-03-08 02:36:11 +01:00 | 434 commits to main since this release- Remove WinRAR.exe from automatic extractor probing to avoid the Unknown option ? popup - Keep UnRAR as the preferred native RAR extractor
Downloads
-
v1.7.44 Stable
2026-03-08 02:28:51 +01:00 | 435 commits to main since this release- Prefer WinRAR/UnRAR over 7-Zip for RAR extraction and log the chosen extractor - Keep duplicate-suffixed multipart RAR copies out of archive candidate selection - Keep fresh direct-link refresh after repeated same-link download failures
Downloads
-
v1.7.43 Stable
2026-03-08 02:18:53 +01:00 | 436 commits to main since this release- Fix repeated same-link download retries by forcing fresh direct links - Fix duplicate-suffixed multipart RAR candidates that caused extraction from the wrong part
Downloads
-
v1.7.42 Stable
2026-03-08 02:03:17 +01:00 | 437 commits to main since this release- Fix extraction retry loop after CRC/password failures and preserve extract errors across restart
Downloads
-
v1.7.41 Stable
2026-03-08 01:41:28 +01:00 | 439 commits to main since this releasePer-package detailed logging release.
Highlights:
- each package gets its own persistent TXT log file
- package context menu can open the package log directly
- logs cover downloads, retries, extraction, password attempts, rename steps and MKV moves
- existing packages continue writing to the same log after app restart as long as the package remains in the saved queue/session
Verification:
- npx vitest run tests/package-log.test.ts tests/session-log.test.ts
- npm run build
- npm run release:win
Downloads
-
v1.7.40 Stable
2026-03-08 01:04:05 +01:00 | 440 commits to main since this releaseFix auto-recovery force re-download for CRC/password errors on encrypted RAR5 archives: when both JVM and legacy extractors fail (suggestRedownload=true), always force re-download once regardless of valid archive signature (with loop protection via per-archive Set). Previously the sibling-items check failed when other episodes were already cleaned up after hybrid extraction, causing auto-recovery to skip re-download entirely. Also lowered suspicious mini-download retry threshold from 100KB to 5KB.
Downloads
-
v1.7.39 Stable
2026-03-08 00:50:33 +01:00 | 442 commits to main since this releaseFix extraction failures on encrypted RAR5 archives with valid file content
- Add 2.5s retry with delay when legacy extraction fails with CRC/password error: allows Windows file handles to fully release before retrying
- Improve auto-recovery: force re-download when known password fails for one archive but works for siblings (detects content corruption behind valid RAR headers)
- Expand auto-recovery trigger to include wrong_password category alongside crc_error for encrypted RAR5
- Add fsync (datasync) after download completes for pre-allocated sparse files
- Fix permanent extraction failure loop: archives with valid headers but corrupt content were previously skipped by auto-recovery
Downloads
-
v1.7.38 Stable
2026-03-08 00:03:34 +01:00 | 444 commits to main since this releaseBoost hybrid extraction speed: switch JVM from SerialGC to G1GC (MaxGCPauseMillis=50) for shorter pause times; increase JVM heap from 8GB to 32GB to reduce GC pressure on high-RAM systems; raise hybrid extraction thread cap from 8 to 12 (uses 75% of CPU cores instead of 50%); refresh daemon process CPU priority before each extraction request for correct hybrid priority
Downloads
-
v1.7.37 Stable
2026-03-07 23:46:53 +01:00 | 446 commits to main since this releaseFix stall-timeout re-download loop for providers that don't report fileSize (e.g. Mega-Debrid Web): (1) Early-exit from download read loop now also uses the raw HTTP Content-Length header as fallback when totalBytes is unknown, preventing the stall timer from firing on the final server-close wait. (2) Stall handler now checks if the file is already complete on disk before deleting and retrying — if the file size matches expectations, the download is treated as successful instead of being discarded and re-queued. This is a belt-and-suspenders fix on top of v1.7.36.
Downloads