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

Ghostly 'Close' button hovering on my Desktop #20623

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

Originally created by @strangebit on GitHub (Oct 4, 2023).

Windows Terminal version

1.18.2681.0

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

I'm not sure what's triggering it unfortunately.

Expected Behavior

No response

Actual Behavior

Ever since v1.18.2681.0, I've been getting this issue every day. I never notice when it actually appears, but eventually I notice a ghostly 'Close' button hovering on my Desktop, and it appears to be something attached to Windows Terminal. In the taskbar, I can see it's attached to Windows Terminal and it has the title Pop-upHost. If I try to select it, I get a WindowsTerminal.exe is not responding, and closing it closes my Windows Terminal.

Windows Terminal appears to work fine if I just leave it alone though.

Taskbar:

WT_Taskbar_Pop-upHost

Button over desktop:

Ghostly_Close

Using NirSoft GUIPropView to inspect two different Pop-upHost handles (red sections redacted):

GUIPropView_Pop-upHost_1

GUIPropView_Pop-upHost_2

The process (i.e. 13F0) for the second one is Desktop Window Manager (dwm.exe).

Originally created by @strangebit on GitHub (Oct 4, 2023). ### Windows Terminal version 1.18.2681.0 ### Windows build number 10.0.19045.0 ### Other Software _No response_ ### Steps to reproduce I'm not sure what's triggering it unfortunately. ### Expected Behavior _No response_ ### Actual Behavior Ever since `v1.18.2681.0`, I've been getting this issue every day. I never notice when it actually appears, but eventually I notice a ghostly 'Close' button hovering on my Desktop, and it appears to be something attached to Windows Terminal. In the taskbar, I can see it's attached to Windows Terminal and it has the title `Pop-upHost`. If I try to select it, I get a `WindowsTerminal.exe` is not responding, and closing it closes my Windows Terminal. Windows Terminal appears to work fine if I just leave it alone though. Taskbar: ![WT_Taskbar_Pop-upHost](https://github.com/microsoft/terminal/assets/11712728/88eec2e0-7f72-4f23-8655-2e520cf51428) Button over desktop: ![Ghostly_Close](https://github.com/microsoft/terminal/assets/11712728/31d022d9-7d4e-40a6-af79-80f17f17dcc2) Using NirSoft GUIPropView to inspect two different `Pop-upHost` handles (red sections redacted): ![GUIPropView_Pop-upHost_1](https://github.com/microsoft/terminal/assets/11712728/9301469a-d6a1-42fb-856a-a4beda01ebc3) ![GUIPropView_Pop-upHost_2](https://github.com/microsoft/terminal/assets/11712728/32f1cd34-005d-4fd8-9152-6f59730639f9) The process (i.e. 13F0) for the second one is Desktop Window Manager (`dwm.exe`).
claunia commented 2026-01-31 07:19:23 +00:00
Author
Owner
Copy Link

@strangebit commented on GitHub (Oct 10, 2023):

It appears to be coming from the X button tooltip, as seen here:

close_tooltip

They look the same, and I've verified that a new Popup-Host handle appears in the GUIPropView list when I mouse over the X button, and then disappears when I move the mouse again. Somehow the handles are going rogue and sticking around?

Also I've noticed the ghost ones sometimes go away on their own when I launch a new terminal window, but not always.

EDIT: Just in case it's relevant, I'm also getting #12882. I just took the screenshot before the bottom tooltip appeared.

@strangebit commented on GitHub (Oct 10, 2023): It appears to be coming from the X button tooltip, as seen here: ![close_tooltip](https://github.com/microsoft/terminal/assets/11712728/5e989eba-8d65-45de-94f9-b4b94ee31df0) They look the same, and I've verified that a new `Popup-Host` handle appears in the GUIPropView list when I mouse over the X button, and then disappears when I move the mouse again. Somehow the handles are going rogue and sticking around? Also I've noticed the ghost ones sometimes go away on their own when I launch a new terminal window, but not always. EDIT: Just in case it's relevant, I'm also getting #12882. I just took the screenshot before the bottom tooltip appeared.
claunia commented 2026-01-31 07:19:24 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 11, 2023):

Okay I've got a horrifying thought. This might be related to us refrigerating the old windows, stopping pumping their messages, but leaving them around. I'd bet this only happens when you close one terminal window while another Terminal window is still open.

Can you go install this old Terminal Preview version: https://github.com/microsoft/terminal/releases/tag/v1.18.1421.0/? This is the original Terminal 1.18 Preview that didn't have the window thread refrigeration code. If that doesn't repro this, then I'd bet we could narrow it down to that.

@zadjii-msft commented on GitHub (Oct 11, 2023): Okay I've got a horrifying thought. This might be related to us refrigerating the old windows, stopping pumping their messages, but leaving them around. I'd bet this only happens when you close one terminal window while another Terminal window is still open. Can you go install this _old_ Terminal Preview version: https://github.com/microsoft/terminal/releases/tag/v1.18.1421.0/? This is the original Terminal 1.18 Preview that didn't have the window thread refrigeration code. If that doesn't repro this, then I'd bet we could narrow it down to that.
claunia commented 2026-01-31 07:19:24 +00:00
Author
Owner
Copy Link

@strangebit commented on GitHub (Oct 12, 2023):

All right sounds good. I'm not going to be around for the next few days but I'll let you know after that.

@strangebit commented on GitHub (Oct 12, 2023): All right sounds good. I'm not going to be around for the next few days but I'll let you know after that.
claunia commented 2026-01-31 07:19:24 +00:00
Author
Owner
Copy Link

@strangebit commented on GitHub (Oct 18, 2023):

As discussed, I've been using Terminal Preview v1.18.1421.0 for a few days now and I haven't experienced the issue on it yet.

@strangebit commented on GitHub (Oct 18, 2023): As discussed, I've been using Terminal Preview v1.18.1421.0 for a few days now and I haven't experienced the issue on it yet.
claunia commented 2026-01-31 07:19:24 +00:00
Author
Owner
Copy Link

@strangebit commented on GitHub (Oct 22, 2023):

Yesterday, I switched back to v1.18.2822.0 to see if it was still happening on the latest version, and I did encounter it again, but only at the very end of a long day. I think it was after I closed one of the windows, which suggests you could be right @zadjii-msft , however it defintely doesn't happen every time I close a window with another window still open, and I had opened and closed many windows that day.

Managed to get a video of another bug I've been noticing too, since I've been paying attention: #16211. I'm not sure if that's related to this issue or not, but it feels like it crops up about as frequently, i.e. after opening and closing windows and using Terminal for a while, etc. I can't remember if I ever saw it when I was using Preview v1.18.1421.0 last week though. I'm going to switch back to Preview v1.18.1421.0 again now, and I'll keep and eye out again for if this issue or #16211 ever occurs on it.

@strangebit commented on GitHub (Oct 22, 2023): Yesterday, I switched back to v1.18.2822.0 to see if it was still happening on the latest version, and I did encounter it again, but only at the very end of a long day. I think it was after I closed one of the windows, which suggests you could be right @zadjii-msft , however it defintely doesn't happen every time I close a window with another window still open, and I had opened and closed many windows that day. Managed to get a video of another bug I've been noticing too, since I've been paying attention: #16211. I'm not sure if that's related to this issue or not, but it feels like it crops up about as frequently, i.e. after opening and closing windows and using Terminal for a while, etc. I can't remember if I ever saw it when I was using Preview v1.18.1421.0 last week though. I'm going to switch back to Preview v1.18.1421.0 again now, and I'll keep and eye out again for if this issue or #16211 ever occurs on it.
claunia commented 2026-01-31 07:19:24 +00:00
Author
Owner
Copy Link

@j0eii commented on GitHub (Oct 25, 2023):

experiencing the same issue
image
image

@j0eii commented on GitHub (Oct 25, 2023): experiencing the same issue ![image](https://github.com/microsoft/terminal/assets/13985803/121e697d-d327-48a6-a860-ba3447392e98) ![image](https://github.com/microsoft/terminal/assets/13985803/d4198d26-ef77-4289-aaa3-0940bb407ae8)
claunia commented 2026-01-31 07:19:25 +00:00
Author
Owner
Copy Link

@RKS-labs commented on GitHub (Nov 6, 2023):

Also experienced this on v1.18.2822.0 (Windows 10) with three WT instances and two "PopupHost" close buttons. Attempting to close one of the buttons through the taskbar popped up a "not responding" dialog and killed all three instances of WT.

@RKS-labs commented on GitHub (Nov 6, 2023): Also experienced this on v1.18.2822.0 (Windows 10) with three WT instances and two "PopupHost" close buttons. Attempting to close one of the buttons through the taskbar popped up a "not responding" dialog and killed all three instances of WT.
claunia commented 2026-01-31 07:19:25 +00:00
Author
Owner
Copy Link

@acorderob commented on GitHub (Nov 10, 2023):

I also got this "popuphost" window (with v1.18.2822.0 Win10). And it did happen after i closed a second terminal.

@acorderob commented on GitHub (Nov 10, 2023): I also got this "popuphost" window (with v1.18.2822.0 Win10). And it did happen after i closed a second terminal.
claunia commented 2026-01-31 07:19:25 +00:00
Author
Owner
Copy Link

@wumo commented on GitHub (Nov 15, 2023):

Also have this issue:
image

@wumo commented on GitHub (Nov 15, 2023): Also have this issue: ![image](https://github.com/microsoft/terminal/assets/7351935/554a4cc6-cda0-4cbc-aaca-a2b4da6b72c2)
claunia commented 2026-01-31 07:19:25 +00:00
Author
Owner
Copy Link

@RKS-labs commented on GitHub (Nov 17, 2023):

I got around this by keep opening new WT instances until all buttons were gone, then exiting from the command line one by one.

@RKS-labs commented on GitHub (Nov 17, 2023): I got around this by *keep opening* new WT instances until all buttons were gone, then exiting from the command line one by one.
claunia commented 2026-01-31 07:19:25 +00:00
Author
Owner
Copy Link

@alesandroortiz commented on GitHub (Nov 17, 2023):

I've had this occur for a few weeks, multiple times per day. I've also seen it occur with a Maximize tooltip. I have not changed my config recently, so it's not related to that. Currently running Terminal version 1.18.2822.0 on Windows 10 Version 22H2 (Build 19045.3570). I'm also using PowerToys v0.75.1, in case that matters. (I did update PowerToys in the past few weeks.)

@alesandroortiz commented on GitHub (Nov 17, 2023): I've had this occur for a few weeks, multiple times per day. I've also seen it occur with a Maximize tooltip. I have not changed my config recently, so it's not related to that. Currently running Terminal version 1.18.2822.0 on Windows 10 Version 22H2 (Build 19045.3570). I'm also using PowerToys v0.75.1, in case that matters. (I did update PowerToys in the past few weeks.)
claunia commented 2026-01-31 07:19:25 +00:00
Author
Owner
Copy Link

@Kaexzr commented on GitHub (Nov 20, 2023):

I have the same issue.
Version 1.18.2822.0
It seems to happen more often when I unplug my 2 external monitors from work to go home.
But it could be pure coincidence.
If I terminate that process, all instances of Windows Terminal close, therefore some times I end up with the frozen pop up for days, while I don't cant to close all terminals I have open.

image

image

@Kaexzr commented on GitHub (Nov 20, 2023): I have the same issue. Version 1.18.2822.0 It seems to happen more often when I unplug my 2 external monitors from work to go home. But it could be pure coincidence. If I terminate that process, all instances of Windows Terminal close, therefore some times I end up with the frozen pop up for days, while I don't cant to close all terminals I have open. ![image](https://github.com/microsoft/terminal/assets/148399599/da8e9974-c944-4506-b314-14095dd9f0d7) ![image](https://github.com/microsoft/terminal/assets/148399599/b56f618b-b31a-455f-a736-c0741018413f)
claunia commented 2026-01-31 07:19:26 +00:00
Author
Owner
Copy Link

@PhilipMorrisJones commented on GitHub (Nov 22, 2023):

Same here. I can get to the close button but if I do so it kills all my open tabs and I have a dozen open ssh sessions so I just accumulate these over time.

image

image

image

@PhilipMorrisJones commented on GitHub (Nov 22, 2023): Same here. I can get to the close button but if I do so it kills all my open tabs and I have a dozen open ssh sessions so I just accumulate these over time. ![image](https://github.com/microsoft/terminal/assets/10975951/03f0c834-de06-489c-a864-90853b33ac6c) ![image](https://github.com/microsoft/terminal/assets/10975951/2f18834a-635d-4c1e-b4e5-533030f007b1) ![image](https://github.com/microsoft/terminal/assets/10975951/d631aa50-0765-45a3-9042-2fa24865928d)
claunia commented 2026-01-31 07:19:26 +00:00
Author
Owner
Copy Link

@xLiWHOI commented on GitHub (Jan 17, 2024):

Same issue here. Have to press "Ctrl+d" now to close tabs/windows.

@xLiWHOI commented on GitHub (Jan 17, 2024): Same issue here. Have to press "Ctrl+d" now to close tabs/windows.
claunia commented 2026-01-31 07:19:26 +00:00
Author
Owner
Copy Link

@gabbymouth commented on GitHub (Jan 25, 2024):

Same issue with both of my computers. This is a PITA because it makes it more difficult to minimize and un-minimize wt to the win 10 taskbar.

@gabbymouth commented on GitHub (Jan 25, 2024): Same issue with both of my computers. This is a PITA because it makes it more difficult to minimize and un-minimize wt to the win 10 taskbar.
claunia commented 2026-01-31 07:19:26 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 31, 2024):

Hey we think this was fixed in the latest release - can someone try out the newest 1.19 / 1.20 builds and double check?

@zadjii-msft commented on GitHub (Jan 31, 2024): Hey we think this was fixed in the latest release - can someone try out the newest 1.19 / 1.20 builds and double check?
claunia commented 2026-01-31 07:19:26 +00:00
Author
Owner
Copy Link

@Kaexzr commented on GitHub (Jan 31, 2024):

I just upgraded to 1.19.10302.0, I will test and report in a few days.

@Kaexzr commented on GitHub (Jan 31, 2024): I just upgraded to 1.19.10302.0, I will test and report in a few days.
claunia commented 2026-01-31 07:19:26 +00:00
Author
Owner
Copy Link

@PhilipMorrisJones commented on GitHub (Feb 1, 2024):

Hi @zadjii-msft, do you have a commit ID or issue where the fix was made?

@PhilipMorrisJones commented on GitHub (Feb 1, 2024): Hi @zadjii-msft, do you have a commit ID or issue where the fix was made?
claunia commented 2026-01-31 07:19:27 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 1, 2024):

I'm guessing it was one of

All of those improved the way window refrigeration was done, and I've got a hypothesis that together, they avoid the issue at the root of this thread.

@zadjii-msft commented on GitHub (Feb 1, 2024): I'm guessing it was one of * #16588 * #16587 * #16592 All of those improved the way window refrigeration was done, and I've got a hypothesis that together, they avoid the issue at the root of this thread.
claunia commented 2026-01-31 07:19:27 +00:00
Author
Owner
Copy Link

@Kaexzr commented on GitHub (Apr 4, 2024):

Just an update for anyone interested, 1.19.10302.0 did in fact solve the issue for me.

@Kaexzr commented on GitHub (Apr 4, 2024): Just an update for anyone interested, 1.19.10302.0 did in fact solve the issue for me.
claunia commented 2026-01-31 07:19:27 +00:00
Author
Owner
Copy Link

@j0eii commented on GitHub (Apr 4, 2024):

havent seen this a while i guess it is fixed

@j0eii commented on GitHub (Apr 4, 2024): havent seen this a while i guess it is fixed
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 Area-Windowing Issue-Bug Needs-Author-Feedback Priority-3 Product-Terminal
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#20623
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?