Windows Hello opens in background #8689

Closed
opened 2026-01-31 01:35:34 +00:00 by claunia · 3 comments
Owner

Originally created by @piotrmocko on GitHub (May 30, 2020).

Environment

Windows build number: 10.0.18363.836
Windows Terminal version: 1.0.1401.0
Ubuntu 20.04 / 18.04 / 16.04 on WSL1
Windows Hello PAM for Linux 1.2

Steps to reproduce

  1. Install and configure Windows Hello PAM for Linux 1.2 on Ubuntu 20.04 / 18.04 / 16.04 https://github.com/nullpo-head/WSL-Hello-sudo
  2. In Windows Terminal on Ubuntu run for the first time any sudo command.
  3. Windows Hello opens in the background and fingerprint scanner gets activated, but Windows Hello does nothing until you activate the window with Windows Hello.

I'm experiencing this issue since I started using Windows Terminal 0.6, while it works without any issue in ConEmu 191012[64] or any earlier version that I used since 3 years.

hello-in-background

Expected behavior

Windows Hello opens in the foreground and recognizes the fingerprint from the scanner.

Actual behavior

Windows Hello opens in the background and fingerprint scanner gets activated, but Windows Hello does nothing until you activate the window with Windows Hello.

Originally created by @piotrmocko on GitHub (May 30, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.18363.836 Windows Terminal version: 1.0.1401.0 Ubuntu 20.04 / 18.04 / 16.04 on WSL1 Windows Hello PAM for Linux 1.2 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1. Install and configure Windows Hello PAM for Linux 1.2 on Ubuntu 20.04 / 18.04 / 16.04 https://github.com/nullpo-head/WSL-Hello-sudo 2. In Windows Terminal on Ubuntu run for the first time any `sudo` command. 3. Windows Hello opens in the background and fingerprint scanner gets activated, but Windows Hello does nothing until you activate the window with Windows Hello. I'm experiencing this issue since I started using Windows Terminal 0.6, while it works without any issue in ConEmu 191012[64] or any earlier version that I used since 3 years. ![hello-in-background](https://user-images.githubusercontent.com/977916/83323005-09016a00-a25c-11ea-8b96-d4d7eaabf568.png) # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Windows Hello opens in the foreground and recognizes the fingerprint from the scanner. # Actual behavior <!-- What's actually happening? --> Windows Hello opens in the background and fingerprint scanner gets activated, but Windows Hello does nothing until you activate the window with Windows Hello.
claunia added the Resolution-Duplicate label 2026-01-31 01:35:34 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Jun 1, 2020):

I'm gonna guess that this is is actually #2988. That's the issue tracking most of the z-order problems the Terminal sometimes has.

/dup #2988

@zadjii-msft commented on GitHub (Jun 1, 2020): I'm gonna guess that this is is actually #2988. That's the issue tracking most of the [z-order](https://github.com/microsoft/terminal/issues?q=is%3Aissue+%22z-order%3A+is%3Aclosed) problems the Terminal sometimes has. /dup #2988
Author
Owner

@ghost commented on GitHub (Jun 1, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jun 1, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Author
Owner

@piotrmocko commented on GitHub (Nov 13, 2020):

After updating Windows 10 to 20H2 and installing the following two updates, the problem has disappeared for me

@piotrmocko commented on GitHub (Nov 13, 2020): After updating Windows 10 to 20H2 and installing the following two updates, the problem has disappeared for me - https://support.microsoft.com/en-us/help/4578968/kb4578968-cumulative-update-for-net-framework - https://support.microsoft.com/en-us/help/4579311/windows-10-update-kb4579311
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#8689