@Copilot I think this was reported on GitHub a few times. Usually a deinstallation and clean reinstallation fixes this.
If you do that, make sure that the local storage of the desktop app is deleted before you reinstall. (i.e. delete the respective folder manually, if it didn’t happen automatically)
You have to log in again to the desktop app after that procedure.
When you reinstall, you can also install the latest version 2025.12.0 then.
Beyond what @Nail1684 suggested above, please also confirm that the setting for “Timeout action” has been set to “Lock”, not “Log out” (under File > Settings). What you’ve described is normal behavior when the “Timeout action” is set to “Log out”.
Our accounts at work also use login with trusted devices. That means our accounts (which are not owners or admins of the enterprise organization), by default, have no master password.
In this case, the default timeout action is “Log out” (only after the user sets a PIN he is able to change that timeout action to “Lock”).
Wait, there literally is no master password for the account? How do you configure this?
I am unable to reproduce this on an Individual account that is not part of an Enterprise plan (although it is the owner/admin of a free organization), and which does have an associated master password. If I set the timeout action to “Log out”, then log out and log back in using “Login with Device”, I am still able to unlock with the account’s master password.