stt
September 30, 2025, 10:06am
1
Unable to edit item on desktop: I can see the password/note but when I try to edit it the window show no inormation, it is blank. Using a second user, it works ok.
Unable to open items on web vault: I click on item but it doesnt pop up, so I cant see the password/note neither edit it. I’ve tried on a second computer and it hasn been successful too.
I turned off vpn, antivirus and firewall withou success. Reinstalled desktop app and also sincronized vault also without success.
On andorid app, I can acess items without issues.
@stt Welcome to the forum!
As you already deinstalled and reinstalled the desktop app, did you make sure that the local storage of the app was also deleted in between? (if you that, make sure you can login again)
Did you try that with a different browser also?
Your BW account is a “cloud account”? Or do you self-host your Bitwarden server?
stt
September 30, 2025, 2:18pm
3
HI, thanks for the tip. I reinstalled and did it some minutes ago but it didn’t help.
stt
September 30, 2025, 2:22pm
4
HI, I’ve tried with differents browsers. If i use a different user it goes ok.
It is a “cloud account”.
It appears to be related with a specific user.
That sounds a bit odd. – For now, I would recommend contacting Bitwarden support .
I don’t know what the problem is, but if I saw this on my account, I would suspect some kind of corruption. So I would definitely export my vault for backup just in case.
Depending on how patient I am with getting a reply from support, I might also try creating a new account and importing the export to see if the problem goes away.
3 Likes
stt
October 9, 2025, 6:21pm
7
HI,
Thanks for your comments.
I’ve contacted Bitwarden support and they found corrupted folders in my vault. They erased all folders preserving data and now I can edit with desktop app and on the Web.
Best regards,
2 Likes
grb
October 9, 2025, 6:54pm
8
Interesting. This is now the second case I’ve seen of folder corruption requiring a manual folder deletion by the Support Team:
Thanks grb, I logged a ticket with support and they fixed the problem.
For reference it turned out to be a problem decryption of my folders which the dev team had to manually delete for me to be able to do anything with my vault again, weird I know!
I wonder if we will be seeing more of these..
I guess this is related to those issues (or rather a “reaction” to them):
main ← vault/PM-26096/folder-failures
opened 11:32PM - 08 Oct 25 UTC
## 🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-26096
## 📔 Object… ive
This fixes a bug preventing any vault items from loading when there is a decryption error for a folder. With this change, we handle the error and hide the offending folder.
## 📸 Screenshots
In this video, note that there is a folder called "Bad Folder" that has a mismatched encryption string, and is failing decryption. The "in bad folder" items are assigned to this folder. I also tested with an account having 500+ folders.
https://github.com/user-attachments/assets/c21aa0a8-8cc3-46fe-ad73-ade336482f5a
## ⏰ Reminders before review
- Contributor guidelines followed
- All formatters and local linters executed and passed
- Written new unit and / or integration tests where applicable
- Protected functional changes with optionality (feature flags)
- Used internationalization (i18n) for all UI strings
- CI builds passed
- Communicated to DevOps any deployment requirements
- Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team
## 🦮 Reviewer guidelines
- 👍 (`:+1:`) or similar for great changes
- 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info
- ❓ (`:question:`) for questions
- 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
- 🎨 (`:art:`) for suggestions / improvements
- ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention
- 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt
- ⛏ (`:pick:`) for minor or nitpick changes
2 Likes
The problem with vault not loading may be related:
opened 10:22PM - 27 Aug 25 UTC
bug
browser
### Steps To Reproduce
1. Follow prompt to unlock the bitwarden extension (usin… g master password or using biometrics does not seem to make a difference)
2. Click on the extension icon to load the popout to interact with the vault
3. Popout does not load correctly, it's just an empty rectangle
4. Sidebar view also does not load
### Expected Result
Be able to open an interaction with the vault after unlocking
### Actual Result
See the screenshot below, it is self explanatory.
<img width="1437" height="1012" alt="Image" src="https://github.com/user-attachments/assets/36e51c81-705d-4f0f-915b-59da1c878a74" />
### Screenshots or Videos
I am not the only person experiencing this, see this extension review posted ~12 hours ago
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/reviews/2484570/
> ...Now, suddenly, I can log in, but after, the little window stays completely empty....
### Additional Context
In the hope this is something to work with to pin this down... Here is the browser console log output when set to use multiprocess mode. These log lines occur whenever opening and then closing the extension popout. The sendRemoveListenter error comes up after clicking the extension icon again to close the popout.
```
WebAssembly is supported in this environment [main.js:856:509556](moz-extension://74859770-fb76-4ccd-8be9-dc278821447e/popup/main.js)
WASM SDK loaded in 36ms [main.js:1:130211](moz-extension://74859770-fb76-4ccd-8be9-dc278821447e/popup/main.js)
State version: 72 [main.js:1:130211](moz-extension://74859770-fb76-4ccd-8be9-dc278821447e/popup/main.js)
sendRemoveListener on closed conduit {446900e4-71c2-419f-a6a7-df9c091e268b}.1511828498077 11 [ConduitsChild.sys.mjs:122:13](resource://gre/modules/ConduitsChild.sys.mjs)
_send resource://gre/modules/ConduitsChild.sys.mjs:122
removeListener resource://gre/modules/ExtensionChild.sys.mjs:715
removeListener resource://gre/modules/ExtensionChild.sys.mjs:971
register chrome://extensions/content/child/ext-storage.js:165
removeListener resource://gre/modules/ExtensionCommon.sys.mjs:2961
revoke resource://gre/modules/ExtensionCommon.sys.mjs:2983
close resource://gre/modules/ExtensionCommon.sys.mjs:2988
unload resource://gre/modules/ExtensionCommon.sys.mjs:983
unload resource://gre/modules/ExtensionPageChild.sys.mjs:279
unload resource://gre/modules/ExtensionPageChild.sys.mjs:322
destroyExtensionContext resource://gre/modules/ExtensionPageChild.sys.mjs:494
observe resource://gre/modules/ExtensionPageChild.sys.mjs:395
```
I also had this warning come up once or twice but it does not seem as easy to replicate
```
downloadable font: Glyph bbox was incorrect (glyph ids 4 5 6 7 13 18 21 22 23 28 35 37 38 54 63 65 66 74 75 78 81 82 88 89 94) (font-family: "bwi-font" style:normal weight:400 stretch:100 src index:1) source: moz-extension://74859770-fb76-4ccd-8be9-dc278821447e/popup/fonts/bwi-font.c53459659794d90d0237.ttf
```
### Operating System
Windows
### Operating System Version
Microsoft Windows 11 Home 10.0.26100 Build 26100
### Web Browser
Firefox
### Browser Version
142.0 (64-bit)
### Environment Versions
This is inaccessible because the popout does not load, but the extension settings in firefox list it as version 2025.8.1
### Issue Tracking Info
- [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
The comments following seem to suggest the source of corruptions, possibly the folder names.
edited: grammar
1 Like
system
November 8, 2025, 9:19pm
11
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.