Skip to content

FileLocker V1.2.0.0

Choose a tag to compare

View all tags
@jeremymhayes jeremymhayes released this 23 May 04:55
· 12 commits to main since this release
v1.2.0.0
fe6c92b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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
Assets 4
Loading