starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-04-17 11:41:04 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

After Windows 11 Wake, Brief Window Pops Up #16751

New Issue
Closed
opened 2026-01-31 05:21:39 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 05:21:39 +00:00
Owner
Copy Link

Originally created by @MikeMcCollister on GitHub (Feb 11, 2022).

Windows Terminal version

1.11.3471.0

Windows build number

10.022000.0

Other Software

No response

Steps to reproduce

This started happening 2+ months ago for me.

  1. Bring the computer out of sleep and unlock the screen.
  2. Watch the screen for up to 5 minutes.

Wait Unlock After logging in or unlocking after sleep, within 1-2 minutes a window will briefly show up. If I am working on something when that happens, my focus will

Expected Behavior

I expected a clean screen an no window pop ups.

Actual Behavior

Within those first 5 minutes a window will briefly pop up. If I am working on something, then the focus sometimes goes away from what I am doing.

I had a PowerShell up and running ready to see the events that ran. As soon as I saw the window pop up, I hit enter. This way I can see what happend over the last second. It looks like Windows Terminal has something to do with this.

Here is the result of the last second of Get-WinEvent

PS C:\Users\Mike> date ; Get-WinEvent

Friday, February 11, 2022 2:04:36 PM

TimeCreated : 2/11/2022 2:04:35 PM
ProviderName : Microsoft-Windows-AppModel-Runtime
Id : 211
Message : Added process 16368 to Desktop AppX container aca013a7-8915-11ec-9e11-a4c3f0e59146 for package
Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe.

TimeCreated : 2/11/2022 2:04:35 PM
ProviderName : Microsoft-Windows-Store
Id : 8001
Message : Skipping license manager: PFN Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe
Function: InvokeLicenseManagerRequired
Source: onecoreuap\enduser\winstore\licensemanager\apisethost\activationapis.cpp (373)

TimeCreated : 2/11/2022 2:04:35 PM
ProviderName : Microsoft-Windows-AppModel-Runtime
Id : 211
Message : Added process 7356 to Desktop AppX container aca013a7-8915-11ec-9e11-a4c3f0e59146 for package
Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe.

TimeCreated : 2/11/2022 2:04:35 PM
ProviderName : Microsoft-Windows-Store
Id : 8001
Message : Skipping license manager: PFN Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe
Function: InvokeLicenseManagerRequired
Source: onecoreuap\enduser\winstore\licensemanager\apisethost\activationapis.cpp (373)

TimeCreated : 2/11/2022 2:04:35 PM
ProviderName : Microsoft-Windows-WMI-Activity
Id : 5857
Message : CIMWin32 provider started with result code 0x0. HostProcess = wmiprvse.exe; ProcessID = 7968; ProviderPath =
%systemroot%\system32\wbem\cimwin32.dll

Originally created by @MikeMcCollister on GitHub (Feb 11, 2022). ### Windows Terminal version 1.11.3471.0 ### Windows build number 10.022000.0 ### Other Software _No response_ ### Steps to reproduce This started happening 2+ months ago for me. 1. Bring the computer out of sleep and unlock the screen. 2. Watch the screen for up to 5 minutes. Wait Unlock After logging in or unlocking after sleep, within 1-2 minutes a window will briefly show up. If I am working on something when that happens, my focus will ### Expected Behavior I expected a clean screen an no window pop ups. ### Actual Behavior Within those first 5 minutes a window will briefly pop up. If I am working on something, then the focus sometimes goes away from what I am doing. I had a PowerShell up and running ready to see the events that ran. As soon as I saw the window pop up, I hit enter. This way I can see what happend over the last second. It looks like Windows Terminal has something to do with this. Here is the result of the last second of Get-WinEvent ------------------------------------------------- PS C:\Users\Mike> date ; Get-WinEvent Friday, February 11, 2022 2:04:36 PM TimeCreated : 2/11/2022 2:04:35 PM ProviderName : Microsoft-Windows-AppModel-Runtime Id : 211 Message : Added process 16368 to Desktop AppX container aca013a7-8915-11ec-9e11-a4c3f0e59146 for package Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe. TimeCreated : 2/11/2022 2:04:35 PM ProviderName : Microsoft-Windows-Store Id : 8001 Message : Skipping license manager: PFN Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe Function: InvokeLicenseManagerRequired Source: onecoreuap\enduser\winstore\licensemanager\apisethost\activationapis.cpp (373) TimeCreated : 2/11/2022 2:04:35 PM ProviderName : Microsoft-Windows-AppModel-Runtime Id : 211 Message : Added process 7356 to Desktop AppX container aca013a7-8915-11ec-9e11-a4c3f0e59146 for package Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe. TimeCreated : 2/11/2022 2:04:35 PM ProviderName : Microsoft-Windows-Store Id : 8001 Message : Skipping license manager: PFN Microsoft.WindowsTerminal_1.11.3471.0_x64__8wekyb3d8bbwe Function: InvokeLicenseManagerRequired Source: onecoreuap\enduser\winstore\licensemanager\apisethost\activationapis.cpp (373) TimeCreated : 2/11/2022 2:04:35 PM ProviderName : Microsoft-Windows-WMI-Activity Id : 5857 Message : CIMWin32 provider started with result code 0x0. HostProcess = wmiprvse.exe; ProcessID = 7968; ProviderPath = %systemroot%\system32\wbem\cimwin32.dll
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 05:21:39 +00:00
claunia commented 2026-01-31 05:21:40 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 11, 2022):

Do you have Terminal set as your default console host application? If so, Terminal will pop up in the same circumstances as an old console window would. This includes instances where login/unlock scheduled tasks would present a console window.

@DHowett commented on GitHub (Feb 11, 2022): Do you have Terminal set as your default console host application? If so, Terminal will pop up in the same circumstances as an old console window would. This includes instances where login/unlock scheduled tasks would present a console window.
claunia commented 2026-01-31 05:21:40 +00:00
Author
Owner
Copy Link

@MikeMcCollister commented on GitHub (Feb 11, 2022):

This might have something to do with setting the default terminal application to Windows Terminal. If I set it to Windows Console Host then I don't get the pop up.

@MikeMcCollister commented on GitHub (Feb 11, 2022): This might have something to do with setting the default terminal application to Windows Terminal. If I set it to Windows Console Host then I don't get the pop up.
claunia commented 2026-01-31 05:21:40 +00:00
Author
Owner
Copy Link

@MikeMcCollister commented on GitHub (Feb 11, 2022):

Do you have Terminal set as your default console host application? If so, Terminal will pop up in the same circumstances as an old console window would. This includes instances where login/unlock scheduled tasks would present a console window.

Yes, I do have the default terminal application set to Windows Terminal.

Is there a way to list all login/unlock scheduled tasks?

@MikeMcCollister commented on GitHub (Feb 11, 2022): > Do you have Terminal set as your default console host application? If so, Terminal will pop up in the same circumstances as an old console window would. This includes instances where login/unlock scheduled tasks would present a console window. Yes, I do have the default terminal application set to Windows Terminal. Is there a way to list all login/unlock scheduled tasks?
claunia commented 2026-01-31 05:21:41 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 15, 2022):

There's a pretty solid write-up over here on StackOverflow. All told, you'll need to enable process logging and then come back after the issue reproduces to see whose fault it is that a console window was spawned.

Alternatively, you can change the "close on exit" behavior in Terminal (Profiles > Defaults > Advanced > Termination Behavior) to "always close" so that the window goes away when the process exits.

Terminal defaults to "only if the process exited successfully" so that in case of a misconfiguration it doesn't just flicker open and closed. 🙂

@DHowett commented on GitHub (Feb 15, 2022): There's a pretty solid write-up [over here on StackOverflow](https://superuser.com/questions/1052541/how-can-i-get-a-history-of-running-processes). All told, you'll need to enable process logging and then come back after the issue reproduces to see whose fault it is that a console window was spawned. Alternatively, you can change the "close on exit" behavior in Terminal (Profiles > Defaults > Advanced > Termination Behavior) to "always close" so that the window goes away when the process exits. Terminal defaults to "only if the process exited successfully" so that in case of a misconfiguration it doesn't just flicker open and closed. 🙂
claunia commented 2026-01-31 05:21:41 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 20, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Feb 20, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 05:21:41 +00:00
Author
Owner
Copy Link

@MikeMcCollister commented on GitHub (Feb 20, 2022):

There's a pretty solid write-up over here on StackOverflow. All told, you'll need to enable process logging and then come back after the issue reproduces to see whose fault it is that a console window was spawned.

Alternatively, you can change the "close on exit" behavior in Terminal (Profiles > Defaults > Advanced > Termination Behavior) to "always close" so that the window goes away when the process exits.

Terminal defaults to "only if the process exited successfully" so that in case of a misconfiguration it doesn't just flicker open and closed. 🙂

Thanks for the link. Unfortunately, the computer that I am running Windows 11 on is the Home edition and gpedit.msc is not included. I know that this is a way to install gpedit but I am not comfortable doing that on that machine.

Knowing that this is not a Windows Terminal issue is good to know.

Thanks all for the help.

Mike

@MikeMcCollister commented on GitHub (Feb 20, 2022): > There's a pretty solid write-up [over here on StackOverflow](https://superuser.com/questions/1052541/how-can-i-get-a-history-of-running-processes). All told, you'll need to enable process logging and then come back after the issue reproduces to see whose fault it is that a console window was spawned. > > Alternatively, you can change the "close on exit" behavior in Terminal (Profiles > Defaults > Advanced > Termination Behavior) to "always close" so that the window goes away when the process exits. > > Terminal defaults to "only if the process exited successfully" so that in case of a misconfiguration it doesn't just flicker open and closed. 🙂 Thanks for the link. Unfortunately, the computer that I am running Windows 11 on is the Home edition and gpedit.msc is not included. I know that this is a way to install gpedit but I am not comfortable doing that on that machine. Knowing that this is not a Windows Terminal issue is good to know. Thanks all for the help. Mike
claunia commented 2026-01-31 05:21:42 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 22, 2022):

Thanks for following up; sorry we couldn't be of better help!

@DHowett commented on GitHub (Feb 22, 2022): Thanks for following up; sorry we couldn't be of better help!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Question Needs-Tag-Fix Resolution-Answered
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#16751
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?