FileLocker v1.3.1.0

FileLocker 1.3.1.0

FileLocker 1.3.1.0 is a patch release for the updater downloader. It fixes a Windows file-locking error where the in-app updater could fail while handling a temporary .download file.

What's Fixed Since 1.3.0.0

• Fixed the updater download path so the temporary .download file is closed before SHA-256 verification and installer promotion.
• Keeps the GitHub Releases installer flow with a versioned Inno Setup executable and matching .sha256 sidecar.
• Preserves the 1.3.0 System Care, Explorer integration, Free-Space Sanitizer, app polish, and updater surfaces.

Install Notes

If an older installed build shows an error like FileLocker-Setup-1.3.1.0.exe.<id>.download is being used by another process, download and run this installer manually from the GitHub release page. After FileLocker 1.3.1.0 is installed, future updater downloads use the fixed path.

Download

Download both release assets:

• FileLocker-Setup-1.3.1.0.exe
• FileLocker-Setup-1.3.1.0.exe.sha256

Verify The Installer

SHA-256:

5bf270cff98b5a98ba55062125ac5ea2ea991783b8cb84cf597291035c40d4df  FileLocker-Setup-1.3.1.0.exe

Installer details:

• Installer: FileLocker-Setup-1.3.1.0.exe
• Size: 74,257,578 bytes (70.82 MiB)
• Installer system: Inno Setup 6.4.3
• Product version: 1.3.1.0
• File version: 1.3.1.0
• Default install location: C:\Program Files\FileLocker

Release Validation

This release was built and checked with the frontend production build, release app build, release test suite, Inno Setup compile, installer checksum generation, and FileLocker release gate.

FileLocker V1.3.0.0

FileLocker 1.3.0.0

FileLocker 1.3.0.0 improves System Care workflows, Explorer right-click integration, free-space wiping, and app polish while keeping the app local-first. Files, settings, cleanup scans, encryption, hashing, metadata review, and secure-delete operations stay on your Windows PC.

What's New Since 1.2.2.1

• Added a FileLocker right-click menu inside the app. Right-clicking no longer shows the default WebView/browser menu; it now offers useful actions such as copy, paste, select field text, clear fields, open Settings, open the Security Guide, return Home, or reload the interface.
• Added Recycle Bin Explorer integration. When Explorer integration is enabled, the Windows Recycle Bin gets a Shred with FileLocker action that opens a focused Recycle Bin cleanup flow in FileLocker.
• Improved Recycle Bin cleanup. FileLocker now attempts a 3-pass overwrite of current Recycle Bin files where Windows allows it, then empties the Recycle Bin and offers a handoff to the Free-Space Sanitizer for already-deleted traces.
• Reworked Partition Cleaner into a clearer Free-Space Sanitizer flow with drive selection, media guidance, estimated write volume, HDD duration estimates, confirmation prompts, live progress, elapsed time, pass status, cancellation, and final reporting.
• Improved free-space wipe reliability. Long-running wipes now continue to report status instead of appearing stuck, and cancellation or app shutdown attempts to stop cipher.exe and report cleanup status for leftover temporary wipe files.
• Added smarter drive media detection for System Care pages. FileLocker now reports HDD, SSD, removable, mixed, or unknown media more clearly, including better handling for NVMe-backed SSD volumes.
• Added clearer SSD and removable-drive warnings before free-space wiping, since TRIM and wear leveling can limit overwrite reliability and add unnecessary writes.
• Made Explorer integration enabled by default for new installs while preserving an existing user's explicit opt-out.
• Added administrator relaunch behavior on startup. FileLocker asks for administrator mode when launched normally, but continues to open if the UAC prompt is declined.
• Added accent color settings so highlights, buttons, and navigation can use a selected app accent.
• Polished System Care screens with denser review tables, clearer filters, safer destructive-action confirmations, administrator prompts, and stronger status/report panels.

Download

Download the installer from the release assets:

• FileLocker-Setup-1.3.0.0.exe
• FileLocker-Setup-1.3.0.0.exe.sha256

Verify The Installer

SHA-256:

c695a53d52989cf29ce7edac1489fe525cc29cf588270e33423018c000f70515  FileLocker-Setup-1.3.0.0.exe

Installer details:

• Installer: FileLocker-Setup-1.3.0.0.exe
• Size: 74,265,405 bytes (70.83 MiB)
• Installer system: Inno Setup 6.4.3
• Product version: 1.3.0.0
• File version: 1.3.0.0
• Default install location: C:\Program Files\FileLocker

Notes

• Free-space wiping and secure delete are best-effort. They are generally more predictable on traditional hard drives than on SSDs or flash storage.
• Some System Care actions require administrator mode because Windows protects the target locations.
• Declining the administrator prompt does not stop FileLocker from opening; features that need elevation will still ask you to relaunch as administrator.
• Existing FileLocker user data remains under local app data during normal upgrades.

Release Validation

This release was built and checked with the frontend production build, release app build, release test suite, Inno Setup compile, installer checksum generation, and FileLocker release gate.

FileLocker V1.2.2.1

FileLocker 1.2.2.1

FileLocker 1.2.2.1 uses Inno Setup as the public Windows installer. The release produces a normal setup wizard, installs application binaries under Program Files, supports upgrades and uninstall through Windows Apps & Features, and keeps FileLocker user data under local app data.

Highlights

• Added an Inno Setup installer script at installer\inno\FileLocker.iss.
• Added scripts\Build-InnoInstaller.ps1 to restore, build, publish, package, and generate FileLocker-Setup-1.2.2.1.exe.sha256.
• Updated scripts\Build-Installer.ps1 and the release gate to validate Inno installer artifacts instead of Velopack packages.
• Removed Velopack from the runtime startup path and package references.
• Updated the in-app updater to find FileLocker-Setup-{version}.exe assets on GitHub Releases, verify SHA-256, launch the installer helper, and let the installer replace installed files.
• Kept local app data, settings, history, cleanup metadata, startup restore data, update downloads, logs, and WebView2 profile data outside Program Files.

Packaging Changes

• Installer system: Inno Setup 6
• Installer filename: FileLocker-Setup-1.2.2.1.exe
• Installer checksum: FileLocker-Setup-1.2.2.1.exe.sha256
• Default install location: {autopf}\FileLocker
• Windows file version: 1.2.2.1
• Main executable: FileLocker.exe
• Build command: .\scripts\Build-InnoInstaller.ps1 -Configuration Release -RuntimeIdentifier win-x64

The generated installer, checksum sidecar, publish staging folder, logs, and other files under artifacts\ are release artifacts and should not be committed.

GitHub Release Notes

Upload these files from artifacts\inno to the GitHub release:

• FileLocker-Setup-1.2.2.1.exe
• FileLocker-Setup-1.2.2.1.exe.sha256

The in-app updater expects the installer asset to use the FileLocker-Setup-{version}.exe naming pattern and verifies the matching .sha256 sidecar when available.

Upgrade Notes

• Fresh installs should use the Inno Setup installer from the GitHub release.
• Upgrade installs should preserve user data because FileLocker stores settings, history, cleanup metadata, startup restore data, update logs, downloads, and WebView2 profile data under local app data.
• Updating directly from an older NSIS or Velopack install should be manually smoke tested before publishing broadly.

Checksums

The package script writes a SHA-256 sidecar beside the installer. Publish the sidecar with the installer so update checks can verify the downloaded setup executable before launch.

FileLocker V1.2.2.0

FileLocker v1.2.2.0

FileLocker v1.2.2.0 is a reliability, security, and update-flow improvement release. This version focuses on making the in-app updater more reliable, improving encryption metadata validation, tightening file-operation safety checks, and cleaning up release files before publishing.

Highlights

• Fixed the in-app updater install flow so the installer launches correctly after FileLocker closes.
• Improved installer cleanup after updates complete.
• Kept AES-256-GCM as the default encryption option.
• Added support for additional modern authenticated encryption options when supported by the local runtime.
• Improved validation for encrypted .locked file metadata.
• Preserved compatibility with existing AES-256-GCM encrypted files.
• Improved validation and error handling across file, folder, hash, metadata, keyfile, and export workflows.
• Removed generated test screenshots and browser automation snapshots from the release branch.

What’s New

Updater Improvements

The update install flow has been improved for both the update popup and the Settings page.

FileLocker now uses a safer helper process that waits for the running app to close before starting the downloaded installer. This makes the update process more reliable, especially when dealing with paths that contain spaces or special characters.

The updater also continues to validate GitHub Releases installer assets before launch and automatically removes the downloaded installer after the update installer exits.

Encryption Improvements

Encryption support has been cleaned up and standardized across the app.

AES-256-GCM remains the default encryption option. FileLocker now also supports additional authenticated encryption options for new .locked files when the local runtime supports them safely, including:

• ChaCha20-Poly1305
• AES-256-GCM-SIV

New encrypted files now include stronger authenticated metadata, including information about the selected algorithm, key size, key derivation settings, nonce data, chunk settings, and key-slot metadata.

Existing AES-256-GCM FileLocker payloads remain decryptable.

File Workflow Improvements

Several file-related workflows now perform stronger checks before actions run.

Improved validation was added for:

• Selected files and folders
• Keyfile paths
• Folder restore package paths
• Metadata workflows
• Hashing workflows
• CSV export values
• Error message redaction

Folder restore safety was also improved so restored package paths stay inside the intended restore location.

CSV export handling was tightened to better protect spreadsheet exports from unsafe control characters and formula-style values.

System Care

The System Care improvements from v1.2.1.0 remain in place.

Custom Clean continues to use real scan results, safety labels, filters, and review-first cleanup controls.

Startup Manager continues to support broader startup-source review with reversible disable metadata where FileLocker can safely provide it.

Registry Fixer continues to review bounded stale entries with details-first cleanup.

App Manager continues to support installed-app inventory, visible uninstall launching, exports, and approved leftover cleanup.

Fixes

• Fixed an issue where the updater install button could fail to launch the downloaded installer.
• Fixed version metadata so the app, manifests, installer config, README, and release notes report 1.2.2.0.
• Removed generated root screenshot files and browser automation snapshots from the release branch.
• Improved handling for malformed paths, invalid metadata, and unsafe export values.
• Improved error handling for invalid keyfile paths before encryption begins.
• Improved temporary text-buffer cleanup during bounded text reading.

Security and Reliability

FileLocker remains local-first. Settings, history, update state, cleanup metadata, startup restore data, update downloads, and WebView profile data remain under local FileLocker app data locations.

New encryption options are authenticated encryption only. FileLocker does not add legacy or unauthenticated algorithms just to increase the option count.

For new .locked files, the selected encryption algorithm is stored in authenticated payload metadata. Wrong passwords, tampered ciphertext, tampered authentication tags, and tampered metadata are expected to fail safely.

Updater downloads continue to come from GitHub Releases and are validated before launch.

Known Limitations

FileLocker cannot recover encrypted files if the password, recovery key, or required keyfile is lost. Keep backups of anything important.

Secure delete is best-effort. On SSDs, wear leveling and device-level remapping can make complete physical removal difficult to guarantee.

Some System Care actions may require administrator permission, including:

• Local-machine startup entries
• Common Startup folder entries
• Protected cleanup locations
• Drive optimization
• Free-space wiping

Vendor uninstallers are controlled by the app publisher after FileLocker launches them.

Custom Clean is intentionally conservative. Some advanced Windows cleanup areas may appear as unavailable or review-only when FileLocker cannot safely clean them through file-based cleanup.

Install and Update Notes

Download:

FileLocker-Setup-1.2.2.0.exe

from this GitHub Release.

Users on FileLocker v1.2.1.0 can update through the in-app updater once this release is published with the installer asset attached.

The installer may request administrator approval.

Existing local settings, history, update preferences, cleanup metadata, startup restore data, and WebView2 profile data remain stored under local FileLocker app data locations.

After updating, open FileLocker and confirm that the app reports version 1.2.2.0.

Checksums

A SHA-256 checksum file should be published beside the installer asset:

FileLocker-Setup-1.2.2.0.exe.sha256

Use this file to verify the downloaded installer.

FileLocker V1.2.1.0

FileLocker 1.2.1.0

FileLocker 1.2.1.0 is a System Care update focused on clearer cleanup decisions, safer startup and registry review, better installed-app management, and more reliable file browsing when FileLocker is running as administrator.

Highlights

Rebuilt Custom Clean into a modern cleanup dashboard with space recoverable, items found, selected cleanup, last cleaned status, and safety/risk status visible at a glance.
Expanded Custom Clean with more Windows, browser, application, gaming, developer, privacy, and advanced cleanup categories.
Improved Startup Manager so startup entries are easier to review by impact, source, publisher, signature, risk, and restore state.
Improved Registry Fixer so it can find more issue types, including Application Paths, ActiveX/COM, file association, shared DLL, help-file, startup, and uninstall problems.
Improved App Manager with clearer installed-app summaries, filtering, sorting, details, export, and uninstall actions.
Fixed Browse Files and Browse Folder failures that could happen when FileLocker was running as administrator.

What's New

Custom Clean

Added grouped cleanup tabs for All, Windows, Browsers, Applications, Gaming, Developer Tools, Privacy, and Advanced.
Added search, category filters, safety filters, and sorting by size, name, category, or safety.
Added Select All, Select Filtered, Clear Selection, and page-level selection controls.
Added a right-side item details panel showing scanned locations, files found, total size, what will be removed, what will not be removed, and a recommendation.
Added safety labels for cleanup items, including Safe, Review, Advanced, Risky, and Privacy.
Added graceful unavailable and not-found states so unsupported or missing cleanup locations do not look like app failures.
Added broader cleanup coverage for browser caches, app caches, launcher caches, logs, shader caches, recent-file traces, developer caches, and other common cleanup targets.

Startup Manager

Added a startup impact summary with high, medium, and low impact counts.
Added clearer tabs and filters for enabled, disabled, broken, advanced, and ignored startup entries.
Added details for startup type, location, command, resolved file path, publisher, signature, impact, risk, and restore records.
Added support for reviewing more startup sources, including Run and RunOnce entries, startup folders, scheduled tasks, services and drivers, shell and Explorer hooks, WMI event consumers, and packaged startup apps.
Added source-opening actions so users can jump to the registry, file location, Task Scheduler, WMI management, or Startup Apps settings when supported.
Added export and copy actions for startup item details.
Added ignore and return-to-review actions for startup entries the user does not want to keep seeing.
Added confirmation-protected removal for broken startup entries that FileLocker can safely manage.

Registry Fixer

Added a clearer Registry Fixer screen with issue counts, selected items, last scan time, registry health, category tabs, severity filtering, and issue details.
Added scanning for stale Application Paths entries.
Added scanning for invalid ActiveX and COM server references.
Added scanning for broken file type associations.
Added scanning for invalid shared DLL references.
Added scanning for invalid Windows help-file references.
Kept startup and uninstall registry issue review in a safer details-first workflow.

App Manager

Added summary cards for installed apps, visible apps, total known size, and large apps.
Added search, app type filters, size filters, and sorting by size, name, publisher, or install date.
Added tabs for all apps, large apps, recently installed apps, Microsoft apps, Store apps, and desktop apps.
Added an app details panel with publisher, version, size, install date, install location, install source, uninstall command, registry entry, and description where available.
Added quick actions to open install locations, copy app details, export the app list, and launch supported uninstallers.

File Workflows

Improved Browse Files and Browse Folder behavior when FileLocker is elevated.
Added a native Windows shell dialog fallback for elevated file and folder selection.
Kept the normal Windows picker behavior for non-elevated runs.
Improved reliability for workflows that depend on selecting files or folders before encrypting, decrypting, hashing, deleting, or reviewing metadata.

App Experience

Added clearer page subtitles for Custom Clean, Registry Fixer, Startup Manager, and App Manager.
Improved System Care pages with calmer tables, summary cards, details panels, and action areas.
Improved selected-row highlights, status badges, filters, and empty states across System Care screens.
Improved administrator-mode feedback for startup management.

Fixes

Fixed elevated Browse Files and Browse Folder requests that could fail with "The request could not be completed."
Fixed Custom Clean selection friction by adding visible select-all controls.
Fixed unsupported cleanup areas so they display as unavailable instead of returning misleading cleanup results.
Fixed missing cleanup paths so they display as not found instead of looking like errors.
Fixed Registry Fixer coverage so registry scans are not limited to simple missing-file pointers.
Fixed startup source actions so supported registry, file, task, WMI, and settings locations can be opened directly from the details panel.

Security and Reliability

FileLocker remains local-first. Settings, history, update state, cleanup metadata, startup restore data, and WebView profile data stay under local FileLocker app data locations.
Custom Clean uses real scan results instead of hardcoded cleanup sizes.
Privacy, developer, advanced, and sign-out-sensitive cleanup items are not selected by default.
Browser cookies, browser history, saved passwords, autofill data, Local Storage, IndexedDB, saved games, mods, worlds, screenshots, configs, and user-created content remain protected by default.
Advanced cleanup actions are clearly marked for review and may require administrator access.
Startup item disabling remains designed around reversible metadata where FileLocker can safely support it.
Broken startup entry removal requires confirmation.
App uninstall actions require confirmation and do not run silent uninstall commands.
System cleanup and registry repair actions stay bounded to safer, explicit targets instead of guessing at broad system locations.

Known Limitations

FileLocker cannot recover encrypted files if the password, recovery key, or keyfile is lost.
Secure delete is best-effort. On SSDs, wear leveling and device-level remapping can make complete physical removal harder to guarantee.
Some System Care actions require administrator permission, including local-machine startup entries, common Startup folder entries, protected cleanup locations, drive optimization, and free-space wiping.
Vendor uninstallers are controlled by the app publisher after FileLocker launches them.
Custom Clean is intentionally conservative. Some advanced Windows cleanup areas are shown as unavailable or review-only when FileLocker cannot safely clean them through file-based cleanup.
Some cleanup results can show unknown size when Windows does not expose a safe or complete file count before cleanup.

Install and Update Notes

Download FileLocker-Setup-1.2.1.0.exe from the FileLocker 1.2.1.0 GitHub release when it is published.
Close FileLocker before installing the update.
The installer may request administrator approval.
Existing local settings, history, update preferences, cleanup metadata, startup restore data, and WebView2 profile data remain under local FileLocker app data locations.
After updating, open FileLocker and confirm the app reports version 1.2.1.0.

Checksums

Use the checksum below to verify the installer you downloaded matches the published release file.

Artifact	SHA-256
FileLocker-Setup-1.2.1.0.exe	a1698b9b0fadaf0fa8431e6ed85a6d5a52ad98c0430c634a9306a5378e8e4f19

FileLocker V1.2.0.0

FileLocker 1.2.0.0

FileLocker 1.2.0.0 is a major update focused on a cleaner app experience, safer system maintenance tools, more reliable file workflows, and a more consistent Windows release process.

Highlights

• Added a new System Care area for reviewing startup items, installed apps, drive tools, and leftover app data.
• Added dedicated pages for FileLocker’s main tools, making encryption, decryption, hashing, text encoding, secure delete, and settings easier to navigate.
• Improved file operation feedback so active work, progress, results, and failures are easier to understand.
• Improved maintenance workflows so errors stay visible instead of disappearing after a short notification.
• Improved installer and version consistency so the app, installer, package metadata, and release files all report the correct version.

What’s New

System Care

• Added Startup Manager for reviewing startup entries and disabling supported items when needed.
• Added App Manager for reviewing installed apps, opening install locations, and launching visible uninstallers after confirmation.
• Added app leftover cleanup for selected cache, log, temp, and stale app-data folders.
• Added clearer status feedback for cleanup, drive tools, startup actions, and app maintenance tasks.
• Added safer handling around maintenance actions that may require administrator permission.

File Workflows

• Improved progress tracking during active file operations.
• Improved selected-file and selected-folder handling, especially when paths use different casing or slash formats.
• Improved hashing and verification reliability.
• Improved operation results so completed work and failures are easier to review.
• Improved output handling to reduce confusing path and naming issues.

App Experience

• Added a cleaner page-based app experience with dedicated areas for core FileLocker tools.
• Improved drag-and-drop handling for file workflows.
• Improved local preference storage for settings, history behavior, output folders, and privacy options.
• Improved in-app feedback for loading, success, failure, and warning states.

Fixes

• Fixed cases where old progress information could appear during a new file operation.
• Fixed maintenance failures that could become hard to review after a notification expired.
• Fixed path-removal issues where the same path could behave differently because of casing or slash differences.
• Fixed release validation issues around installer assets and version consistency.
• Fixed package health issues reported in frontend tooling dependencies.
• Fixed release workflow permissions so validation runs with safer read-only repository access.

Security and Reliability

• FileLocker remains local-first. Settings, history, update state, and WebView profile data stay under the user-local FileLocker app data folder.
• Startup item disabling is designed to be reversible through backed-up registry values or FileLocker-managed disabled shortcut storage.
• App uninstall actions require confirmation and do not run silent uninstall commands.
• App leftover cleanup is limited to approved user and shared-data locations.
• Program Files, Windows folders, and other protected system locations are excluded from recursive leftover cleanup.
• Sensitive operation data receives stronger redaction before errors are shown in the app.
• Destructive or long-running maintenance actions use clearer confirmation and administrator checks.
• Release builds now include synchronized app, package, installer, displayed version, and release-note metadata.

Known Limitations

• FileLocker cannot recover encrypted files if the password, recovery key, or keyfile is lost.
• Secure delete is best-effort. On SSDs, wear leveling and device-level remapping can make complete physical removal harder to guarantee.
• Some System Care actions require administrator permission, including local-machine startup entries, common Startup folder entries, protected cleanup locations, drive optimization, and free-space wiping.
• Vendor uninstallers are controlled by the app publisher after FileLocker launches them.
• System Care cleanup is intentionally limited to safer locations. It is not meant to replace a full system repair tool.

Install and Update Notes

• Download FileLocker-Setup-1.2.0.0.exe from the FileLocker 1.2.0.0 GitHub release when it is published.
• Close FileLocker before installing the update.
• The installer may request administrator approval.
• Existing local settings, history, update preferences, and WebView2 profile data remain under the user-local FileLocker app data folder.
• After updating, open FileLocker and confirm the app reports version 1.2.0.0.

Checksums

Use the checksum below to verify the installer you downloaded matches the published release file.

Artifact	SHA-256
FileLocker-Setup-1.2.0.0.exe	b81289a03b2b4c0ee8b80f5f72519a7f325a3feda17fac79c30ed755a467cbda

FileLocker V1.1.1.0

FileLocker 1.1.1.0

Highlights

• Refined the React/WebView interface into a denser desktop utility layout with flatter workspace surfaces and tighter page hierarchy.
• Added local maintenance tools for Custom Clean, Partition Cleaner, Drive Optimizer, and Registry Fixer.
• Added bridge-contract validation, release-gate checks, staged publish validation, and NSIS installer output checks.
• Expanded automated tests for hashing, manifests, compression advice, payload handling, history export, and update behavior.

Fixes

• Fixed the Custom Clean administrator notice so it uses a compact full-width status row instead of collapsing inside the narrow options pane.
• Improved WebView2 startup packaging by preserving required frontend assets in build and publish output.
• Updated installer metadata, app manifests, and project version fields to 1.1.1.0.

Validation

• Expected installer asset: artifacts\nsis\FileLocker-Setup-1.1.1.0.exe
• Expected digest sidecar: artifacts\nsis\FileLocker-Setup-1.1.1.0.exe.sha256

FileLocker 1.1.0.0

FileLocker 1.1.0.0 Release Notes

These notes cover what changed since FileLocker 1.0.5.2.

Highlights

• Moved FileLocker to a modern full-window desktop interface while keeping sensitive work inside the Windows app.
• Restored and polished the complete tool set: dashboard, encryption, decryption, hashing, text encoding, metadata tools, secure delete, settings, about, and security guide.
• Added a production installer flow for the 1.1.0.0 release with stronger publish-output checks and cleaner Windows registration.
• Removed monetization language. FileLocker remains free.

Interface Improvements

• Rebuilt the main layout with a fixed sidebar, independent page scrolling, and a native title bar that matches the app chrome.
• Restored the dashboard drag-and-drop encryption zone with file and folder support.
• Restored dashboard quick actions for Encrypt Files, Hash Files, Encode Text, Metadata Scrambler, and Secure Delete.
• Restored the recent activity table and empty states so fake sample files are no longer shown.
• Restored right-side dashboard status panels for protected files, saved storage, last operation, and security status.
• Replaced custom file-type image handling with the Classic icon set from file-icon-vectors, with a dedicated lock icon for .locked files.
• Improved text scale, spacing, focus states, and title rendering across the app.

Workflow Fixes

• Restored the Decrypt Files page with file picking, password entry, validation, and operation feedback.
• Made file and folder selection zones clickable and drag-and-drop capable across file-based tools.
• Added selected-file lists with file size display and per-file removal.
• Added show/hide controls for password fields.
• Added confirmation handling for destructive actions such as secure delete and delete-originals-after-encrypt.
• Fixed Settings so values load from the app, save explicitly, and persist when navigating away.
• Replaced output-folder text boxes with folder picker rows.
• Improved success and error feedback for long-running operations.

Security and Reliability

• Kept encryption, decryption, hashing, metadata handling, secure delete, settings, and filesystem access in the Windows app.
• Kept AES-256-GCM encrypted file handling intact.
• Preserved structured request and response handling between the interface and the app.
• Continued blocking unsafe update installs when downloaded release assets cannot be verified.
• Improved empty, loading, error, and completed states so operations are easier to verify.

Documentation

• Updated the README for version 1.1.0.0.
• Refreshed install instructions around the NSIS installer.
• Added clearer user-facing explanations for FileLocker's security model and limitations.

Installer Changes

• Updated app and file versions to 1.1.0.0.
• Updated the NSIS installer version and output naming.
• Aligned the default installer publish folder with the scripted release flow.
• Added validation for the packaged interface files before the installer is built.
• Added a desktop shortcut in addition to Start Menu shortcuts.
• Added Windows uninstall metadata such as install location, help link, README link, and display icon.
• Cleaned stale packaged interface assets before copying the new version during install.

Notes Before Upgrading

• FileLocker is still a local-only app. Files do not leave your machine.
• Forgotten passwords cannot be recovered.
• Keep backups of important encrypted files.
• The installer is intended for 64-bit Windows.

FileLocker V1.0.5.2

FileLocker 1.0.5.2

This release is a small follow-up update focused on updater testing, supportability, and release metadata consistency.

What's new

• Added quick Help menu actions to:
  • open the installed app folder
  • open the updater download cache folder

These shortcuts make it easier to confirm which build is installed and inspect the exact installer downloaded by the updater.

Improvements

• Improved updater support and troubleshooting workflow with faster access to install/update locations
• Refreshed release metadata and versioning to 1.0.5.2
• Updated project documentation so the README matches the current app, installer, and release process

Notes

• GitHub release tags should use the format:
  v1.0.5.2
• The installer asset should be uploaded as:
  FileLocker-Setup-1.0.5.2.exe

FileLocker V1.0.5.1

FileLocker v1.0.5.1

FileLocker 1.0.5.1

Fixes

• Fixed auto update not properly reading Github release tags