Troubleshooting

The exe isn't code-signed (that costs money; this project spends zero on it). If you downloaded from the official release page, click "more info → run anyway". Compare the SHA256 from the release notes if you want certainty:

certutil -hashfile Lurelock.exe SHA256

Check the log folder: %LOCALAPPDATA%\Lurelock\Logs\. The newest Lurelock_<timestamp>.log records startup, settings loads and any exception with a stack trace. When reporting a bug, paste that file's content (or the tail of it) into the issue tracker.

The launch lock gates launching Roblox — it never blocks opening the settings window. Open Settings with Lurelock.exe -settings, go to Security and remove the password. Full docs: Security & privacy.

Check check for updates is on in Settings, and that GitHub is reachable. The self-update needs the release to carry an exe asset. If it keeps failing, update manually from the releases page.

Flags: open the FastFlags editor and delete the offending one (or hit restore default). Mods: remove it from the mods list and relaunch. To wipe everything Lurelock-specific: restore official client from the main window.

Occurs when Roblox's CDNs are unreachable or a package fails its checksum. Lurelock retries and then shows a help message. Usually: wait, check your connection/firewall/VPN, and try again. Uninstall-and-reinstall of Lurelock clears stuck state.