Recovery mode means the app cannot read the operating-system key that protects your proxy passwords and sign-in; fix the cause and restart the app, or reset if the key is gone for good.
Applies to: Agilelogin for Windows (first release); the macOS notes apply once the macOS build ships.
What does the screen say?
The app opens on a screen titled Agilelogin can’t reach its encryption key. Your local data is encrypted with a key kept in the operating system’s key store: the Windows user’s data-protection key on Windows, the login keychain on macOS. This copy of the app could not read that key.
While the screen is showing, Profiles do not launch and sync is paused. Nothing is deleted.
What is affected?
The key protects the fields the app stores encrypted: proxy passwords and your account sign-in. Profiles, fingerprints, groups and proxy addresses are stored normally and are not affected. Cookies are protected separately, by each Profile’s own key, and are not touched by a recovery reset unless you choose to reset.
What should you try first?
The screen lists the usual causes:
- Windows: the key belongs to a different Windows user or a different computer, or an administrator reset your account password. If you copied only the roaming
%APPDATA%folder from another PC, the key stayed on that PC in%LOCALAPPDATA%. - macOS: if macOS asked for permission to use your keychain, reopen the app and choose Always Allow. If your login password was reset recently, your login keychain still uses the earlier password; unlock it in Keychain Access with that password.
After you fix the cause, restart the app. The Try again button on this screen does not re-read the key store in this release, so a fix made in the system only takes effect on the next start.
Reset
If the key is gone for good, choose Reset. Resetting creates a new encryption key. Your proxy passwords and your current sign-in are cleared, and the login state of every Profile on this computer is reset. Each Profile’s own cookie key is protected by that computer key as well, so a new key cannot open the login state saved under the old one. When you sign in again, proxy passwords come back from your synced copy; on an account that does not sync, you type them again. The app walks you through the passwords that still need attention.