Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Charleyrich
19 days agoNew Contributor
Windows Hello opens in background and doesn't function correctly
The last 3 days windows hello (in use with 1 password) doesn't accept input. And somehow caps lock is on even though the keyboard doesn't show it on. I saw that this was an issue a year ago, but it...
- 7 days ago
Hello everyone,
Thank you for your patience. Our development team has released a fix for the issue in the latest update to 1Password for Windows (8.12.1):
We’ve fixed an issue where Windows Hello prompts could appear behind app and browser windows.
Please update to the latest version of 1Password for Windows: How to keep 1Password up to date
If you're still seeing issues with Windows Hello appearing behind other apps/windows after updating then please let me know by replying to this post.
-Dave
Nusaram
12 days agoDedicated Contributor
Though I can only speak for my situation, currently I am left with the feeling that the keyboard issue was caused by 1Password and not the January update, per se, and leaning me to the same conclusion for the out-of-focus Windows Hello authentication window.
Per my other post, I experienced the Shift/Caps Lock issue in another app and, I'm sure, only because I wasn't interacting with 1Password at the time. I was able to reproduce this multiple times via system restores, which initially led me to believe that the root cause was the January Windows Update.
However, after 1P_Dave posted about the keyboard fix and after the fix was installed on my PC, I decided to resume Windows Updates and the January Updates were installed. They're the exact same Windows updates and this time around, no more keyboard issues!
So, same Windows Updates installed, but this time with the new version of 1Password and that can only lead me to conclude that the root cause was 1Password.
Again, this is just my experience on my PC and yours may/will vary, but I am currently left with the conclusion that this mess was caused by 1Password and not Microsoft.