Seerr 3.4.1 — Windows installer

Packages seerr-team/seerr v3.4.1 as a self-contained Windows service. No Docker, no PostgreSQL.

Security: this build includes the upstream v3.4.0 fix for CVE-2026-73291 (path traversal → RCE in the image proxy). If you run the 3.2.0 installer, upgrade.

What's in the box

• Seerr v3.4.1 (built from source on windows-latest)
• Node.js 22.19.0 (embedded; uses no system Node)
• NSSM wrapping Seerr as the Seerr Windows service
• SQLite database (default: C:\ProgramData\Seerr\db\db.sqlite3, selectable in the wizard)

Upstream changes since 3.2.0

• v3.3.0 — server-side i18n for notifications, Plex ratingKey in webhooks, many availability-sync and request fixes. Breaking for webhook consumers: discordID (string) became discordIDs (string[]).
• v3.4.0 — CVE-2026-73291 patch, Jellyfin/Emby Quick Connect login, Discord thread IDs, admin quota bypass, option to disable the version check.
• v3.4.1 — keep requests when media is removed from Radarr/Sonarr; handle already-removed media on delete.

Install / upgrade

1. Download Seerr-3.4.1-windows-x64-setup.exe below.
2. Run it. SmartScreen will warn — click More info → Run anyway (the installer is unsigned).
3. Pick a data directory. On upgrade the wizard defaults to your existing path (read from HKLM\SOFTWARE\Seerr\DataDir), so the database is kept.
4. Pick a port (default 5055).
5. The service is re-registered and started; your browser opens to Seerr. Database migrations run on first start and can take a minute.

Manage the service with:

sc query Seerr
sc stop Seerr
sc start Seerr

Logs: <your data dir>\logs\ (rotated at 10 MB).

Packaging changes since the 3.2.0 installer

• Ship next.config.ts (upstream renamed it from next.config.js in v3.3.0; Next.js reads it at service start).

Pre-release status

Marked as pre-release until end-to-end verified on a clean Windows box, same as 3.2.0.

Verification

sha256: b92aae500d38b9bbac3ff97b12f2ab32aba8fd692635eb55e6a7b09375fe0918
size:   168 MB (176,121,980 bytes)

Known limitations

• Unsigned installer (SmartScreen warning expected)
• x64 only
• Service runs as LocalSystem (NSSM default)
• No automated migration path from a Postgres deployment
• Network paths (UNC \\server\share) rejected as the data directory — SQLite WAL is unsafe over SMB

See the README for details.

Seerr 3.2.0 — Windows installer

First Windows installer build for Seerr.

Packages seerr-team/seerr v3.2.0 as a self-contained Windows service. No Docker, no PostgreSQL.

What's in the box

• Seerr v3.2.0 (built from source on windows-latest)
• Node.js 22.19.0 (embedded; uses no system Node)
• NSSM wrapping Seerr as the Seerr Windows service
• SQLite database (default: C:\ProgramData\Seerr\db\db.sqlite3, selectable in the wizard)

Install

1. Download Seerr-3.2.0-windows-x64-setup.exe below.
2. Run it. SmartScreen will warn — click More info → Run anyway (the installer is unsigned for now).
3. Pick a data directory (where the SQLite DB, logs, and settings.json will live). Default is C:\ProgramData\Seerr — change this if you want the database on a different drive.
4. Pick a port (default 5055).
5. Browser opens to the Seerr setup wizard.

The chosen data directory is remembered in the registry, so re-running the installer defaults to your existing path instead of orphaning the database.

The service auto-starts on boot. Manage it with:

sc query Seerr
sc stop Seerr
sc start Seerr

Logs: <your data dir>\logs\ (rotated at 10 MB).

Pre-release status

Marked as pre-release until end-to-end verified on a clean Windows box. Each re-spin tightens the install path; flip to stable when you've confirmed a clean run.

Fixed since the previous build of this asset

• First-run service start is no longer reported as a failure. SCM's global 30s service-start timeout is short on first install while Seerr creates the SQLite DB, runs all TypeORM migrations, and warms the Next.js handler cache (AV scanning the freshly extracted node_modules doesn't help). The installer now kicks the service via sc start and polls for RUNNING for 30 s. If it gets there, success. If not, you get an informational dialog (not an error) with sc query Seerr as the diagnostic — the service is still registered with Startup type: Automatic so it'll come up on its own or at next boot.

Fixed since the v3.2.0 first build

• Real nssm.exe shipped instead of the chocolatey shim.
• install-service.cmd is self-contained and pre-flight checks nssm.exe / node.exe / dist\index.js exist.
• Install errors surface as MsgBox instead of being swallowed by runhidden.
• Data directory picker added to the wizard, persisted to HKLM\SOFTWARE\Seerr\DataDir.

Verification

sha256: 7e53a34caaced1fa9c6ffe48aca5de300bd1610457abb49290dd63bec1522cc9
size:   198 MB

Known limitations

• Unsigned installer (SmartScreen warning expected)
• x64 only
• Service runs as LocalSystem (NSSM default)
• No automated migration path from a Postgres deployment
• Network paths (UNC \\server\share) rejected as the data directory — SQLite WAL is unsafe over SMB

See the README for details.