TOTP verification code incorrect in desktop app

Got a bit of a strange one here where the TOTP code in my desktop app doesn’t update the TOTP code correctly when selecting different entries.

I’ve been using BW for a few years now and utilise the desktop and extensions extensively throughout the day, previously without issue. Within the last week I’ve noticed my desktop app on my Windows PC incorrectly shows the same TOTP code on all entries.

I’m able to use the browser extension or the app on my phone to show the correct code but I use the local app a lot for locally installed apps I have that require the TOTP code.

It seems the local desktop app gets stuck on a specific TOTP enty which remains that code on all other entires I click on. Sometimes, upon the 30 second count down, it will change to the entry I’m on but mostly it keeps cycling on the incorrect entry so is very unreliable at present.

I have TOTP specific entries in my database that has no other data but the authenticator key and these are all affected by this same issue.

I’ve tried uninstalling and re-installing the desktop app but that hasn’t resolved the issue. I’ve also tried uninstalling the local app and installing the app from the Microsoft Store but that also has the same problem. My local time is correct and syncing to an online NTP server correctly.

Is there something else I can do to try and resolve this issue? Is there some kind of local cache I can clear in addition to uninstalling?

1 Like

@Jmac That is a current and known bug (PS: both desktop app versions 2025.6.0 and 2025.6.1 are affected, as far as I know):

There already is a fix:

… but the (currently) latest version of the desktop app (2025.6.1) doesn’t contain it. We have to wait for now.

Thanks for the prompt response Nail1684.

I did try to search the forums before posting but didn’t see these mentioned.

I’ve tried to install an older edition of Bitwarden-Portable-2025.5.1.exe to avoid auto-updates, but it has the same issue.

Do I need to clear some kind of local cache to be able to utilise an older version that doesn’t experience the issue?

I honestly don’t know. Could be the case. As long as you can login again (be sure to have your master password and 2FA – or email verification code for the “new device login protection” – at hand), there is no harm in deleting the local storage a given BW app: Data Storage | Bitwarden)

The portable app has its own cache, so it should have started from a fresh user data cache (unless you had previously installed the portable app in the same folder).

FWIW, I cannot reproduce the issue in either version 2025.5.1 or 2025.6.1 of the portable Desktop app (on Windows 11 – 23H2): when I switch from viewing one login item to viewing another login item (in the same Bitwarden vault — not using the account switcher), then TOTP codes change as expected.

I’ve got the portable edition working as expected and will revert back to the latest version once this bug is resolved. Thank you for your assistance.

1 Like

Following this post. I thought I was going nuts, but I’m experiencing the same exact bug.

My Bitwarden desktop application was also generating an incorrect TOTP code, but my mobile devices remained unaffected.

In fact, I went so far as to reconfigure some 2FA TOTP codes on several websites using the desktop application a few days ago.

I hope this does not create any issues for me down the line…

Desktop app 2025.7.0 was released a few hours ago and contains the fix for TOTP codes.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.