So it seems that 2026.4.0 forgets the search vault string when locking now and instead resorts back to a clean slate. I have logged a Github issue: Does not remember folder or search vault settings over lock · Issue #20902 · bitwarden/clients · GitHub and also asked if it can remember the folder as well. Working with multiple logins in a folder is easier than searching, and a lock/unlock of the client should not revert to a newly opened app.
This behavior is not new to version 2026.4.0 of the Desktop app. Do you have any evidence that the search string ever persisted through a lock/unlock cycle?
Only that I have been just using it until the update. After the update it does not work. It should be baked in. I was getting frustrated by it resetting the folder view. It makes it unusable now for me so either I
a) look at another product that can do it
b) hope that it gets resolved (but i dont hold out hope)
I am not sure why resetting the search/where you are between lock and unlock is ever a good thing. Imagine if you unlocked your desktop and it was like you just logged in - all apps closed. Usability factor = 0.
The behavior you describe (remembered search strings after lock/unlock) is not anything that I am able to reproduce using older versions of the Desktop app.
Do you mean locking the Windows account, or locking the Bitwarden vault? It would be helpful if you could describe the exact sequence of steps that you performed when this worked for you.
I’m on version 2026.2.0 and the search state doesn’t persist across app lock. I agree with @grb : AFAIK the desktop app has never persisted search state or folder state across app locks — see the discussion here.
The closest thing added over the last year is the browser extension persisting some states across the extension pull‑down/pull‑up, but that’s also time‑limited.
So on point b) I wouldn’t hold out much hope either, since there doesn’t appear to be even a feature request.
OK - So I have just tested this based on feedback. Here is the interesting bit.
For me, I loaded 2026.3.0 (I think it was) to go back a revision. In the default configuration, locking the vault and then unlocking did not have this feature.
Then I enabled pin code lock (which I use), and then it started working.
So try:
- Set a pin code lock
- Search for an item
- When found, lock the vault (file → Lock → lock vault)
- Unlock with pin
- The search item is there.
Let me know if I need to upload a video of it. This does not work on 2026.4.0.
True enough — I can confirm for 2026.2.0. After enabling PIN unlock instead of the biometrics I normally use, the search state persisted across app lock. (Side note: folder state doesn’t.)
@gooseleggs You should make it very clear in your Github bug report that PIN unlock should be used, and add your finding about 2026.3.0 2026.3.1 so BW can reproduce the problem. We’ll see what they say.
P.S.: Master password unlock by itself doesn’t show the persisted search state. Master password unlock with PIN unlock enabled shows the persisted search state, but biometric still doesn’t.
Thanks for the additional information; I have also been able to reproduce this now (in version 2026.3.1; there is no 2026.3.0 for the Desktop app).
I also found it necessary to ensure that the option “Lock with master password on restart” is checked — if I uncheck this option, then the search expression is cleared on PIN unlock.