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

"DesktopWindowXamlSource" appears in taskbar if ("Compatibility") headless and "Startup" > "New Instance Behavior" set to ANYTHING OTHER THAN "Create new window" #23168

New Issue
Open
opened 2026-01-31 08:34:18 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 08:34:18 +00:00
Owner
Copy Link

Originally created by @carlos-zamora on GitHub (Apr 16, 2025).

Windows Terminal version

v1.22.10731.0 (Stable)

Windows build number

Windows 10 - Version 10.0.19045.5608

Other Software

Microsoft PowerToys is not installed.

Steps to reproduce

Originally a part of #18784

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.
  3. then open WT again.

Related to the ghost "DesktopWindowXamlSource" window mentioned in #18784

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

Expected Behavior

"DesktopWindowXamlSource" should never be exposed.

Actual Behavior

"DesktopWindowXamlSource" is exposed

Originally created by @carlos-zamora on GitHub (Apr 16, 2025). ### Windows Terminal version v1.22.10731.0 (Stable) ### Windows build number Windows 10 - Version 10.0.19045.5608 ### Other Software Microsoft PowerToys is not installed. ### Steps to reproduce Originally a part of #18784 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. Related to the ghost "DesktopWindowXamlSource" window mentioned in #18784 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). ### Expected Behavior "DesktopWindowXamlSource" should never be exposed. ### Actual Behavior "DesktopWindowXamlSource" is exposed
claunia commented 2026-01-31 08:34:19 +00:00
Author
Owner
Copy Link

@similar-issues-ai[bot] commented on GitHub (Apr 16, 2025):

We've found some similar issues:

  • #18784 , similarity score: 90%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@similar-issues-ai[bot] commented on GitHub (Apr 16, 2025): We've found some similar issues: - #18784 , similarity score: 90% If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue. > Note: You can give me feedback by 👍 or 👎 this comment.
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-UserInterface Issue-Bug Needs-Tag-Fix 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#23168
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?