Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
robo187 opened this issue Apr 11, 2025 · 2 comments
Labels
Area-Performance Performance-related issue Issue-Bug It either shouldn't be doing this or needs an investigation. Priority-3 A description (P3) Product-Terminal The new Windows Terminal.
Milestone

Comments

@robo187
Copy link

robo187 commented 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).

@robo187 robo187 added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Apr 11, 2025
@DejayRezme
Copy link

DejayRezme commented 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).

@DHowett DHowett added Area-Performance Performance-related issue Product-Terminal The new Windows Terminal. Priority-3 A description (P3) and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Apr 16, 2025
@carlos-zamora carlos-zamora removed their assignment Apr 16, 2025
@carlos-zamora carlos-zamora added this to the Backlog milestone Apr 16, 2025
@DejayRezme
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Performance Performance-related issue Issue-Bug It either shouldn't be doing this or needs an investigation. Priority-3 A description (P3) Product-Terminal The new Windows Terminal.
Projects
None yet
Development

No branches or pull requests

4 participants