v0.1.55 — Windows PostgreSQL port control

Native Windows users can now change the private PostgreSQL port in Settings → General → Windows connection ports, alongside the application port.

• Choose an unused port from 1024 through 65535, different from the application port, then select Change PostgreSQL port and restart.
• ALPR checks conflicts, saves a protected configuration recovery copy, coordinates both services and verifies the restarted database and application. Failed or interrupted changes restore the previous connection.
• PostgreSQL stays local to the computer. Your browser address, Blue Iris URLs, credentials, records and images stay the same.
• Updates, software rollback and retained-data reinstall preserve the selected database port.
• Windows updates tolerate temporary progress-file locks without interrupting the update worker.
• User Guide 3.23, Windows installation and maintenance guidance, the roadmap and wiki are updated.

Update through Settings → Software Updates or use the Windows installer asset. After a UI update from an older release, restart Windows once if General asks you to activate the new port control. Finish or recover any pending software update before changing connection ports.

Windows installation · Windows maintenance · Linux installation · Wiki

v0.1.54 - Windows migration ports and UI guidance

Windows installations can now select unused application and database ports during fresh setup or migration. This allows an existing Docker installation to stay on port 3000 while native Windows ALPR uses another port, such as 3001, and its own PostgreSQL 17 database.

Existing native Windows users can change the application port in Settings → General → Windows connection port. The restricted updater verifies the port, preserves database and local-network settings, updates ALPR shortcuts, restarts the application and provides the new address. Failed or interrupted changes restore the previous port. Update Blue Iris's destination port after a successful change. An older running updater service may need one Windows restart after this update to enable the new control.

The Windows UI now identifies Setup-managed database and Blue Iris settings correctly, shows native Windows release and recovery instructions, and links to the Windows update guide. Maintenance wording also follows the installed platform.

User Guide 3.22, Windows installation and migration guides, the README and roadmap explain the independent databases, port selection and later port changes. Existing installations retain their configured ports during updates and retained-data recovery.

Download ALPR-Community-0.1.54-Windows-x64-Setup.exe for a fresh Windows installation or to enable UI updates on an older installation. Existing supported installations can use Settings → Software Updates. Linux installation and update instructions are linked from the README.

v0.1.53 - Automatic Linux update helper setup

Fresh Linux installations and activated migration targets now set up the restricted Software Updates helper automatically on systemd hosts. Setup enables startup after reboot for the actual installation owner and verifies a fresh heartbeat from the running service before reporting readiness.

Matching existing helpers and their configuration are preserved. If setup needs attention, ALPR and its data stay in place and the installer prints the manual recovery command. Isolated migration review never starts an updater. The command ./alpr-community agent install remains available for older installations and recovery; hosts without systemd can keep the terminal updater or their existing service supervisor.

User Guide 3.21, installation, migration, bootstrap, update guidance, roadmap and wiki navigation cover the new behavior. Existing Windows installations continue to use Settings → Software Updates with their separate native updater service.

Download the Windows Setup.exe for graphical installation; the Update.zip is consumed by the Windows UI updater. Linux users can follow the installation guide and update guide. The standalone User Guide PDF and checksums are attached.

Validation includes the full test and security gates, Linux service and unattended startup checks with a disposable account, database integration fixtures, Docker runtime verification and native Windows runtime checks. See implementation and checks.

v0.1.52 — Windows installation and help documentation

Make Windows setup and support instructions easier to find and follow.

• User Guide 3.20 adds native Windows installation, the four Setup choices, first sign-in, local-network access, camera setup order, portable backup, Linux-to-Windows migration, and UI-update acceptance.
• A new step-by-step Windows guide is linked from README, the installation/migration guides and GitHub issue chooser.
• The roadmap and compatibility/deployment pages now describe the shipped stable Windows installer and updater, with the actual validation scope preserved.
• The Community wiki provides installation, backup/migration and troubleshooting navigation while detailed instructions remain in the versioned repository guides.
• GitHub bug forms include native Windows 10 and Windows 11 options.

This is a documentation update. Database SQL, runtime dependencies and Windows maintenance/service code are unchanged from 0.1.51. Existing installations can update through Settings → Software Updates. Complete the displayed checks and select Accept update. Passwords, API key, records, images and settings carry forward with the normal recovery backup.

New Windows users should download the Windows-x64-Setup.exe asset and follow the Windows installation guide. The attached User Guide PDF is also available in the application under Help.

v0.1.51 - Windows update data preservation

Fix Windows updates that rolled back after database count validation.

• Skip byte-identical verified schema and migration files instead of replaying historical cleanup against an existing native database.
• Check every database table before restarting the application. Keep durable record and image preservation checks after startup, while allowing normal completion of temporary direction work and expiration of authentication state.
• Keep failed before/after counts and affected table names through automatic rollback, so a further failure can be diagnosed from the support report.

The correction passed native Windows regression checks, populated PostgreSQL reproduction, isolated actual Windows service update/rollback/reinstall and UI-update tests. The Windows installer and package are verified separately; exact acceptance on the affected Windows 10 VM remains an operator check.

For an existing Windows installation, keep your database and run this release's graphical Setup, choosing Update ALPR already installed on this computer. Verify 0.1.51 under Settings → Release after Finish. Existing passwords, API keys, records, images and settings are retained with a recovery backup. Windows installations with the updater service can then use Settings → Software Updates for later releases.

v0.1.50 — Windows update file-lock recovery

Windows updates now retry temporary release-folder sharing/access failures for up to 30 seconds. Each retry checks that the target release is inactive and the directories remain valid. Persistent denial stops safely and preserves the existing application and all release copies.

Use the Windows Setup executable once to update installations that do not yet have the updater service. Choose Update ALPR already installed on this computer. Existing credentials, API key, settings, database records and images are retained, with a verified recovery backup during the update. After finishing, confirm Settings → Release shows 0.1.50. Future updates are available through Settings → Software Updates.

The filesystem error alone does not identify a locking process. Keep the support log if access remains blocked; do not delete your database or disable antivirus to work around it.

Windows 10 22H2 x64 and Windows 11 x64 remain the targets. Linux behavior is unchanged. See Windows installation and troubleshooting.

v0.1.49 - Reliable Windows update retries

This release fixes a Windows update that could leave ALPR on the old version while Setup displayed a successful finish screen.

If your Windows update stayed on 0.1.47: run ALPR-Community-0.1.49-Windows-x64-Setup.exe and use Update ALPR already installed on this computer. Keep your existing installation and data. Setup creates a recovery backup and preserves your password, API key, database, images, settings, ports and network preference.

The updater verifies and reuses a complete release copy left by an earlier attempt. Incomplete copies are preserved before a verified replacement is prepared. Setup now stops on maintenance errors, even when a child process returns zero, and checks the exact installed release and its running listener before showing success.

Once the one-time installer enables the Windows update service, use Settings → Software Updates for future stable releases. Complete the real-use checks before selecting Accept update.

Compatible with Windows 10 22H2 x64 and Windows 11 x64. The ZIP and JSON assets are used by ALPR's updater; users should run the Setup executable.

Windows installation and update guide · Corrective change

ALPR Database Community v0.1.48 — Windows updates from Settings

Windows Community updates are now available in Settings → Software Updates.

Existing Windows installations: download and run ALPR-Community-0.1.48-Windows-x64-Setup.exe once. Setup detects the installed application and selects Update ALPR already installed on this computer. It creates a recovery backup and preserves your database, images, settings, passwords, API key, ports and network preference. Do not uninstall or delete your data.

After this one-time update, future stable Windows releases can be checked and installed inside ALPR. The page shows download and installation progress, reconnects after restart, and provides acceptance and rollback. Failed or interrupted maintenance automatically restores the previous release. Finish the real-use checks before accepting an update.

This release also corrects a PowerShell 5.1 issue that could report a migration backup as failed after the backup had completed successfully.

Supports Windows 10 22H2 x64 and Windows 11 x64. The ZIP and update JSON assets are managed by ALPR's update service; users should run the Setup executable.

Validation includes passing security and Linux/Windows CI, 1,278 regression tests, all three CPU models, 28 Settings routes, ingestion/images, direction/timing persistence, actual Windows service upgrade and rollback, retained-data reinstall, and authenticated Settings-driven update acceptance.

Windows installation and update guide · Changes

ALPR Database Community v0.1.47

ALPR Database Community 0.1.47 adds native Windows installation alongside Linux.

• Windows 10 22H2 x64 and Windows 11 x64: download ALPR-Community-0.1.47-Windows-x64-Setup.exe, run it and follow the graphical setup. Administrator approval and an internet connection for PostgreSQL/FFmpeg prerequisites are required. Docker, WSL and developer tools are unnecessary.
• Migration and recovery: import a verified ALPR portable logical backup from Linux or Windows into an empty installation, or restore ALPR data retained on the same Windows computer. Reinstall verifies a protected recovery backup and preserves passwords, API keys, records, images, settings and LAN preference. Back up before removing an existing preview; uninstall keeps its data, then the new setup offers retained-data recovery.
• Vehicle setup: choose LPR or overview images per direction, configure timing tolerance, and use improved saved-state feedback and diagnostics. Concurrent registration of identical images is fixed.
• Startup and maintenance: normal automatic Windows services with database readiness checks, graceful Live Feed shutdown, protected service accounts, and working portable backup tooling.
• Security: updated Next.js/Tailwind dependencies; the dependency vulnerability gate passes without advisory suppression. Chrome/Edge 111 or Firefox 128 or newer is required.

Windows 10 Pro and Windows 11 Home installation/restart checks passed. Actual isolated Windows service upgrade, rollback and retained-data reinstall passed, alongside model, ingestion, Settings, PostgreSQL, Linux and Docker checks. These functional checks do not establish a general ReID accuracy benchmark.

The Windows installer is unsigned. Its SHA-256 checksum and build metadata accompany the download. Windows Server, ARM64, 32-bit Windows and LTSC certification are outside this release's target. Native Windows maintenance instructions are in WINDOWS_NATIVE.md.

ALPR Database Community v0.1.46

Resilient Community updates

• Retries bounded transient DNS, timeout, connection, rate-limit, and server failures while downloading the checksum-pinned OpenVINO runtime.
• Automatically restores the exact previous release and application if an update fails before database migration begins, without replacing the unchanged database.
• Preserves failure and rollback records for diagnosis while leaving the prior release usable and retryable.
• Updates the maintenance launcher, manual 3.11, update guidance, roadmap, installation examples, and regression coverage.

Existing installations should use Settings → Software Updates. Complete Technical system checks and the five real-use checks before accepting the update.