Skip to main content
January 16, 2026
Solved

Windows Hello opens in background and doesn't function correctly

  • January 16, 2026
  • 33 replies
  • 2126 views

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 just occurred again with my system.  I am on Win 11, with the latest updates, no VPN, using Chrome with the browser extension.  

I then get repeated requested to enter my full 1Password credentials.  However after an hour, the timeout for 1Password, the same problem occurs.  

I have tried un enabling and then re enabling 1Password, to no effect.   I also rebooted and then ran a full Microsoft Virus scan, but nothing was found.  

Best answer by 1P_Dave

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

 

33 replies

alcyone7
January 21, 2026

1Password has always, when prompted to unlock, has brought the Windows Hello authentication window to the app location and brought it into focus.  Now this behaviour is broken and it often remains below other open windows, not focussed, and on the default screen location, not the screen it was initiated from.  This is with the browser plugins for Brave and Firefox, both the most recent versions. The desktop app continues to work correctly however.  

Is this a known issue, or has something changed? Two different browsers, two different platforms... so it isn't the browser(s).

Nusaram
January 21, 2026

Hi @alcyone7,

Same here for me with Edge.

It used to happen very infrequently in the past but now, as you stated, it seems to be the standard behavior.

I think, maybe, only for my first unlock it appears in the foreground but thereafter, I always have to look at and use the taskbar to bring it to the foreground.  The bottom line is that for me, the situation has reversed and the window now very infrequently appears in the foreground and in focus.

January 21, 2026

Just to say, happening to me as well for past couple of weeks at least. Glad to hear there's something in the works.

January 22, 2026

You just need to update to  the latest version, it's fix. 

January 22, 2026

Maybe fixed for you, not for me and many others. 1Password updates itself, and, yes, it's at the latest released version. There's a beta with fix that's being tested (read above) but I'm waiting for a release. Thank you.

January 22, 2026

I am still having problems with 1Password even after the latest update of app and browser extension.

The Chrome browser extension keeps asking for my 1Password credentials even though I am using Windows Hello.  The browser extension rejects my credentials at the same time the desktop lets me in.  I tried uninstalling the browser extension and reinstalling it, but to no avail.  Can you help me?

January 22, 2026

Exactly! Same here. It's still a mess.

January 22, 2026

Sorry, still NOT fixed here. When coming out of sleep mode, I click on the 1Password browser extension to unlock, instead of just going to Windows Hello, it gives me a 1Password dialog with an unlock button. Upon clicking that, BOTH the 1Password dialog AND the Windows Hello dialog pop up. It's a mess and it needs to be fixed.

January 22, 2026

Hello, I've never had this issue happen before, however since a few days ago this started happening. I have no keyboard input in the Windows Hello form that opens up when I trigger the Chrome Extension. If I focus away it looks like I'm writing in all caps. If I just press and release left-shift, then I can write in the Windows Hello field.

1P_Dave
1Password Employee
January 22, 2026

Hello everyone, 

Our development team is currently aware of an issue where Window Hello input is disrupted when unlocking 1Password. Improvements were released in 1Password for Windows version 8.12.0 which addressed issues like the apparent triggering of caps lock when the Windows Hello prompt was shown. If you haven't yet updated to 8.12.0 then please do so: How to keep 1Password up to date

That being said, after updating, you may still run into an issue where Windows Hello appears behind apps and browsers when unlocking 1Password. Our development team is currently investigating the issue.

For the time being, you can do the following: 

  1. Open and unlock the main 1Password desktop app first, then use 1Password in the browser (rather than unlocking 1Password in the browser first). 
  2. If you try to unlock 1Password in the browser and Windows Hello is hidden, click on the Windows Hello icon in your task bar to focus Windows Hello: 


I'm sorry for the continued inconvenience. 

-Dave

Nusaram
January 22, 2026

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.

January 23, 2026

Hi,

I’m seeing a similar issue on Windows 11 Pro 25H2 with Chrome 143 and the 1Password extension. When clicking the 1Password icon, I now first get an “Open 1Password” window, then the Windows Hello prompt appears behind a separate window asking for the 1Password master password. I have to close that window to access Windows Hello. This used to be a single-step unlock before.

See screenshots below:

 

January 24, 2026

The Windows Hello prompt opens in the background, and I have to switch window focus to it before I can use it. Is there anyway I can make the prompt open in the foreground, so that I can go straight to scanning my fingerprint without having to change windows?

January 25, 2026

I have been experiencing this same issue for the last week or two also. I have confirmed that it happens in both Chrome and Firefox using Windows 11 24H2.

It seems to be a browser/extension related issue, because if I open the 1Password program while locked, the Windows Hello prompt appears on top of 1Password as intended.

January 27, 2026

What I have found after 1Password v8.12.0 update is that the prompt for the Windows Hello unlocking is no longer brought to focus (using Edge or Chrome extensions) so even it recognizes you (facial unlocking) it is not working. After accepting, a new 1Password window is opened asking for the complete password.

But if you bring the Windows Hello prompt to focus before it recognizes you, the unlocking works.

Anyway, this is very unconfortable and I hope the team can fix it ASAP.

First time working with 1Password with an issue like that...

January 27, 2026

gcr5 is exactly right...it works, but the prompt lies hidden/underneath...you have to click on the sys icon in the tray to bring it up. It's a solution that gets us past what was broken but only half-way to restoring the functionality/experience we knew prior to this issue.