I tested it on my phone with Firefox, and it works without any problems.
However, on the desktop version for Windows, I’ve tested it with four different browsers, and I get the same error message every time. It worked perfectly fine a few weeks ago.
The error message also appears immediately after the page loads when I try to retrieve my security key, and every time I click “Retrieve Key.”
Has anyone else experienced this problem? Or is it a bug in the current version?
I can’t log in to the browser extension anymore either. I can authenticate with my email and password, but when I try to retrieve the security key, I get this message in Firefox.
I don’t want to log out of the desktop version because I’m afraid the login won’t work.
Oddly enough, it works on my phone, but it doesn’t work on my PC with four different browsers installed (I just uninstalled and reinstalled them all, and the problem persists).
Yes, it worked perfectly on my phone; the key was read and I was logged in.
I successfully reinstalled Windows 11. Now everything works again without any problems, and I was able to log in without any errors.
But it was strange because even after reinstalling the browsers, it still didn’t work and kept showing me the error message shown above. Was definitive a windows Problem.
What I just noticed when I logged in again is that the error from the first image with the red box appears when I click on “Read key”; it’s displayed immediately. The message also appeared when I loaded the page normally.
After Reinstallation of Windows A Windows pop-up appears asking which security key to use; this didn’t happen before the Windows reinstallation.
So I think something went wrong when Bitwarden was supposed to send the request to Windows, since no pop-up appeared.
However, if I click “Cancel,” I get the same error message as in the original post.
I am guessing this just for “fun.” I can get the error in the first post by: 1) canceling when the Windows Hello dialog shows, and 2) not having the browser in the foreground when Windows Hello would have shown (I got the error right away). The fact that OP’s reinstallation worked may mean that some part of Windows Hello’s component is corrupted. I would have suggested for people who aren’t so handy with Windows reinstallation, as OP is, to:
Run the usual corruption fix commands by starting “cmd” in admin mode:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
If the above doesn’t fix it, the easiest thing to do is: System > Recovery > Fix problems using Windows Update
Beyond this the options are usually: 1) factory reset, 2) upgrade in place, and 3) clean reinstallation
Anytime you find yourself in this situation, it is a great time to create a zipped export of your vault and store it on an offline USB drive. Keeps things from getting worse, and makes one fear disappear.
