Installer
Installer build
The installer adds .lbx file association and Explorer folder actions while keeping LockBox per-user and admin-free.
Portable ZIP
The portable ZIP remains unchanged and does not register file associations or Explorer menu actions.
Installer documentation
Extract the installer ZIP and run LockBox.Installer.exe. It copies LockBox.exe into the current user profile.
Step-by-step installation
- Download x64 for normal 64-bit Windows, or x86 only for a 32-bit Windows installation.
- Extract the installer ZIP completely and start the installer executable from the extracted folder.
- Select Install. The app is copied into the current user profile; no administrator prompt is expected.
- Confirm the success log for application files, Start Menu shortcuts, .lbx association and Explorer actions.
- Open LockBox from the Start Menu and create a small test container before removing the downloaded package.
The installer registers only current-user HKCU entries. Other Windows users need
to install LockBox separately in their own profile.
Explorer integration and installed defaults
- Double-click a
.lbxfile to open the extraction workflow. - Right-click a folder to create an encrypted container with the normal wizard.
- Use Quick create only after reviewing defaults in Installed settings.
- If Windows 11 hides classic commands, open Show more options in the context menu.
- Restart Explorer or sign out if a newly registered association is not visible immediately.
Installed settings can contain default master and destruction passwords and layer keys. LockBox encrypts that file with Windows DPAPI for the current user, so it is bound to that Windows profile and is not a portable backup. Treat access to the profile as access to those secrets, and keep a separate protected copy before migrating or resetting the profile.
Quick creation is convenient, but stores passwords and keys on disk, protected by your Windows account. Access to that account may expose your container data. For stronger protection, use the standard wizard with passwords and keys that are not saved in settings.
Verify container
Check metadata, split parts, every encryption layer and file checksums. Available in Free, Pro and Max on Windows, Android and CLI.
- For containers created with layer passwords: Choose Verify container and the base .lbx file. Keep all parts together; on Android select them all. Enter the master password and keys in the original layer order.
- Encrypt with random keys: Load the key archive and enter its password to unlock all layers, or select an individual key file at each decryption step.
- After creation, choose Verify container on the final screen. Explorer quick creation offers a Yes/No check and shows the result in a dialog.
Verify container after creation
Enable verification after creation to check backups automatically. Source deletion runs only after a successful check; failure or cancellation preserves the source. The built-in scheduler still requires Max.
Verification uses memory. No plaintext or report is saved to disk. Android may cache encrypted parts. Verification sessions and reports are not saved. OS swap and dumps remain outside this guarantee.
A valid result confirms archive integrity, not a match with the original folder. The format does not authenticate random padding or the destruction-password verifier. Verification never triggers destruction.
Encrypt with random keys
Windows, Android and CLI: Free, Pro and Max, within edition limits. Unavailable in the scheduler and Explorer quick creation.
No layer passwords to invent or remember. Save the key archive and its password; the metadata still requires a master password.
- Enable random keys on the first wizard screen, then choose the algorithms. After creation, save the key archive and copy its password before closing the app. The master password remains required.
- Save the archive directly to a USB drive or other removable storage to avoid leaving an archive copy on this computer. Keep its password separately. Unpacked keys are never written by LockBox.
- Load the key archive and enter its password to unlock all layers, or select an individual key file at each decryption step.
The AES-256 ZIP contains an encrypted keys.zip: key names and their number are hidden. Other archivers need two extraction steps. key_1.lbxkey is for the first decryption step, the outermost layer. Keep the filenames unchanged for archive import.
Random keys are strong, but losing the archive or its password means losing access to your data. Keep them safe and available. Memorised passwords have an advantage over secrets written down. Random keys cannot be combined with container destruction. This option is disabled in key mode.
Source deletion must wait until the key archive is saved and verified.
Update, repair and uninstall
Run a newer installer to update or repair application files. If integration is damaged, run Install
again and inspect the log. To remove it, start the installer and choose Uninstall integration.
This removes per-user registry entries, shortcuts and installed application files. User-created
.lbx containers and extracted data are not deleted.
Installation succeeds but .lbx does not open
Repeat installation in an unrestricted user session and check whether endpoint security blocks per-user registry changes.
Windows shows an unknown-publisher warning
Confirm that the package came from this site and verify its signature or published checksum before continuing.
I need a fully portable copy
Use the portable Windows package and do not enable Installed settings. Keep all extracted files together.