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

Ghost window (DesktopWindowXamlSource) still appears in the Taskbar (See #6507 - #6861 - #16183 - #15047 - #15165 - #15402) #23137

New Issue
Open
opened 2026-01-31 08:33:25 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 08:33:25 +00:00
Owner
Copy Link

Originally created by @robo187 on GitHub (Apr 11, 2025).

Windows Terminal version

1.24.250409001-llm (Canary) & 1.23.250314002-preview (Preview) & 1.22.250314001 (Stable)

Windows build number

Windows 10 - Version 10.0.19045.5608

Other Software

Microsoft PowerToys is not installed.

Steps to reproduce

  1. Open Windows Terminal
  2. Open Settings
  3. Click "Compatibility"
  4. Enable "Allow Windows Terminal to run in the background" option.
  5. Close Windows Terminal

Expected Behavior

After enabling WT to run in background and on clicking the "Close" icon, no Windows Terminal instance should be shown in the Taskbar.

Actual Behavior

After enabling WT to run in background and on clicking the "Close" icon, the WT closes but a ghost window of WT called "DesktopWindowXamlSource" still being shown in the taskbar. When the ghost window is closed, the actual window is also closed.

Other Tries
The same procedure have been tried in a clean-state VMware VM and Windows Sandbox and still the same issue occurs.

The issue is occuring whether the installation method was MSIX bundle or Installer or Portable.

The "%LocalAppData%\Microsoft\Windows Terminal" & "%ProgramFiles%\WindowsApps*WindowsTerminalFolder*" folders have been deleted before trying each method (MSIX bundle or Installer or Portable) to exclude any potential conflicts and ensure clean install.

EDIT: There was another combination of settings that revealed the "DesktopWindowXamlSource". That got pulled out and is being tracked in #18808. It's included as quoted below for convenience.

While enabling "Compatibility" option in the latest stable release [v1.22.10731.0], the ghost "DesktopWindowXamlSource" window does not appear in taskbar as long as "Startup --> (New Instance Behavior) is set to (Create new window)", otherwise if it set to any of the 2 other options, once WT closes, it can never be opened again until...

  1. Open "Task Manager"
  2. search for "Windows Terminal" in "Background Processes"
  3. End it.
  4. then open WT again.
    I think this can be opened as an another separate issue, but it is all-related to the ghost "DesktopWindowXamlSource" window.

The "Compatibility" option allows for quick launch of WT, say an average of 0.0800s with "Compatibility" option enabled vs cold launch of 0.3100s with "Compatibility" option disabled vs "%SystemRoot%\system32\cmd.exe" launch of 0.0460s. (Calculated using PassMark AppTimer).

The "Compatibility" option is crucial for smooth experience but unfortunately it is completely fucked up in Stable, Preview & Canary releases.

Please see this video for more clarification (The video demonstrate the "Compatibility" & "New Instance Behavior" options conflict on Portable mode only on all releases).

Originally created by @robo187 on GitHub (Apr 11, 2025). ### Windows Terminal version 1.24.250409001-llm (Canary) & 1.23.250314002-preview (Preview) & 1.22.250314001 (Stable) ### Windows build number Windows 10 - Version 10.0.19045.5608 ### Other Software Microsoft PowerToys is not installed. ### Steps to reproduce 1. Open Windows Terminal 2. Open Settings 3. Click "Compatibility" 4. Enable "Allow Windows Terminal to run in the background" option. 5. Close Windows Terminal ### Expected Behavior After enabling WT to run in background and on clicking the "Close" icon, no Windows Terminal instance should be shown in the Taskbar. ### Actual Behavior After enabling WT to run in background and on clicking the "Close" icon, the WT closes but a ghost window of WT called "DesktopWindowXamlSource" still being shown in the taskbar. When the ghost window is closed, the actual window is also closed. Other Tries The same procedure have been tried in a clean-state VMware VM and Windows Sandbox and still the same issue occurs. <!-- Failed to upload "explorer_VGoskUAkcL_cut.mp4" --> <!-- Failed to upload "explorer_VGoskUAkcL_cut.mp4" --> The issue is occuring whether the installation method was MSIX bundle or Installer or Portable. The "%LocalAppData%\Microsoft\Windows Terminal" & "%ProgramFiles%\WindowsApps\*WindowsTerminalFolder*" folders have been deleted before trying each method (MSIX bundle or Installer or Portable) to exclude any potential conflicts and ensure clean install. EDIT: There was another combination of settings that revealed the "DesktopWindowXamlSource". That got pulled out and is being tracked in #18808. It's included as quoted below for convenience. > While enabling "Compatibility" option in the latest stable release [v1.22.10731.0], the ghost "DesktopWindowXamlSource" window does not appear in taskbar as long as "Startup --> (New Instance Behavior) is set to (Create new window)", otherwise if it set to any of the 2 other options, once WT closes, it can never be opened again until... > 1. Open "Task Manager" > 2. search for "Windows Terminal" in "Background Processes" > 3. End it. > 4. then open WT again. > I think this can be opened as an another separate issue, but it is all-related to the ghost "DesktopWindowXamlSource" window. > > The "Compatibility" option allows for quick launch of WT, say an average of 0.0800s with "Compatibility" option enabled vs cold launch of 0.3100s with "Compatibility" option disabled vs "%SystemRoot%\system32\cmd.exe" launch of 0.0460s. (Calculated using PassMark AppTimer). > > The "Compatibility" option is crucial for smooth experience but unfortunately it is completely fucked up in Stable, Preview & Canary releases. > > Please see this [video](https://mega.nz/file/beJUBbZD#1Aqg5TjnPCDXSMnn6lLZyr-HM8Yp0LpjnbX9NwI2T24) for more clarification (The video demonstrate the "Compatibility" & "New Instance Behavior" options conflict on Portable mode only on all releases).
claunia added the Issue-BugPriority-3Product-TerminalArea-Performance labels 2026-01-31 08:33:26 +00:00
claunia commented 2026-01-31 08:33:26 +00:00
Author
Owner
Copy Link

@DejayRezme commented on GitHub (Apr 16, 2025):

Can confirm, #16183 still there. Always happens when I use powertoys fancyzones to organize my 4k desktop. Since Terminal is a shell and a basic interface to the windows operating system, bugs like this should be fixed (even though they are only annoying).

@DejayRezme commented on GitHub (Apr 16, 2025): ~~Can confirm, #16183 still there. Always happens when I use powertoys fancyzones to organize my 4k desktop. Since Terminal is a shell and a basic interface to the windows operating system, bugs like this should be fixed (even though they are only annoying).~~
claunia commented 2026-01-31 08:33:27 +00:00
Author
Owner
Copy Link

@DejayRezme commented on GitHub (Apr 17, 2025):

Sorry just tried the preview version 1.23.10732.0 the issue with the ghost window is already fixed. It flashes shortly but then disappears. So this issue seems to be unconnected with the other bug and fancyzones. My apologies.

@DejayRezme commented on GitHub (Apr 17, 2025): Sorry just tried the preview version 1.23.10732.0 the issue with the ghost window is already fixed. It flashes shortly but then disappears. So this issue seems to be unconnected with the other bug and fancyzones. My apologies.
claunia commented 2026-01-31 08:33:27 +00:00
Author
Owner
Copy Link

@ChristopherWalz commented on GitHub (Oct 1, 2025):

I still have this problem on Windows 10.

@ChristopherWalz commented on GitHub (Oct 1, 2025): I still have this problem on Windows 10.
claunia commented 2026-01-31 08:33:27 +00:00
Author
Owner
Copy Link

@RoachLin commented on GitHub (Oct 31, 2025):

I still have this problem on Windows 10.

try to disable the option "run in background"

@RoachLin commented on GitHub (Oct 31, 2025): > I still have this problem on Windows 10. try to disable the option "run in background"
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-Performance Issue-Bug 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#23137
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?