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

Terminal displays as "DesktopWindowXaml..." when it's starting #15810

New Issue
Closed
opened 2026-01-31 04:49:05 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 04:49:05 +00:00
Owner
Copy Link

Originally created by @KotlinIsland on GitHub (Nov 7, 2021).

Windows Terminal version (or Windows build number)

Microsoft Windows [Version 10.0.19043.1288]

Other Software

No response

Steps to reproduce

Open wt

Expected Behavior

window displays as "Terminal" or something with the terminal icon.

Actual Behavior

"DesktopWindowXaml..." with a broken icon.

image

Once it loads it's back to normal.

Originally created by @KotlinIsland on GitHub (Nov 7, 2021). ### Windows Terminal version (or Windows build number) Microsoft Windows [Version 10.0.19043.1288] ### Other Software _No response_ ### Steps to reproduce Open wt ### Expected Behavior window displays as "Terminal" or something with the terminal icon. ### Actual Behavior "DesktopWindowXaml..." with a broken icon. ![image](https://user-images.githubusercontent.com/65446343/140664670-04d26def-8a43-4075-9234-11745b090b5e.png) Once it loads it's back to normal.
claunia commented 2026-01-31 04:49:07 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 8, 2021):

Which version of the Terminal is this? Do you have WSL installed?

My theory is that we're hitting the very slow path of the old WSL distro lookup, which is hanging during the creation of the window, so we don't actually update the window title to something sensible.

I suppose this is something we could fix regardless of if it's fixed already. Like, we could always we the title and icon of the window, even before we load the settings. Should be easy enough to repro, just slap a Sleep(10000) in the WslDistroGenerator

@zadjii-msft commented on GitHub (Nov 8, 2021): Which version of the Terminal is this? Do you have WSL installed? My theory is that we're hitting the very slow path of the old WSL distro lookup, which is hanging during the creation of the window, so we don't actually update the window title to something sensible. <hr> I suppose this is something we could fix _regardless_ of if it's fixed already. Like, we could always we the title and icon of the window, even before we load the settings. Should be easy enough to repro, just slap a `Sleep(10000)` in the `WslDistroGenerator`
claunia commented 2026-01-31 04:49:07 +00:00
Author
Owner
Copy Link

@KotlinIsland commented on GitHub (Nov 9, 2021):

I've seen this on every version of Terminal I've used, and yes WSL 2 with wsl as default shell.

@KotlinIsland commented on GitHub (Nov 9, 2021): I've seen this on every version of Terminal I've used, and yes WSL 2 with wsl as default shell.
claunia commented 2026-01-31 04:49:07 +00:00
Author
Owner
Copy Link

@Rosefield commented on GitHub (Nov 9, 2021):

I also noticed this when I was working on all of the saved layout / quit features. It can be fairly reliably reproduced by having window layout saying enabled and quitting/reloading half a dozen or so windows, resulting in a process list like this (dev/main not updated since the 1.12 release cut). This computer has WSL1 installed, but I only have powershell panes here.

image

@Rosefield commented on GitHub (Nov 9, 2021): I also noticed this when I was working on all of the saved layout / quit features. It can be fairly reliably reproduced by having window layout saying enabled and quitting/reloading half a dozen or so windows, resulting in a process list like this (dev/main not updated since the 1.12 release cut). This computer has WSL1 installed, but I only have powershell panes here. ![image](https://user-images.githubusercontent.com/6185249/140853664-a38d3538-be22-4762-9bb8-f1288a89fac8.png)
claunia commented 2026-01-31 04:49:08 +00:00
Author
Owner
Copy Link

@Link1J commented on GitHub (Jan 10, 2022):

The two DesktopWindowXamlSource is created by C:\Windows\System32\Windows.UI.dll. So I am going to guess they are what make XAML Islands work. My guess on why one of them appears (I don't know which) is that the window isn't configured to be hidden, but Windows makes it disappear when it has a parent. I have seen it appear when closing apps using XAML Islands, probably because it loses it parent window before it is closed.

Making it not appear may need an OS level fix, if it is even possible to fix.

@Link1J commented on GitHub (Jan 10, 2022): The two `DesktopWindowXamlSource` is created by `C:\Windows\System32\Windows.UI.dll`. So I am going to guess they are what make XAML Islands work. My guess on why one of them appears (I don't know which) is that the window isn't configured to be hidden, but Windows makes it disappear when it has a parent. I have seen it appear when closing apps using XAML Islands, probably because it loses it parent window before it is closed. Making it not appear may need an OS level fix, if it is even possible to fix.
claunia commented 2026-01-31 04:49:08 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 22, 2022):

You know what, I think the real root cause here is /dup #6507

@zadjii-msft commented on GitHub (Aug 22, 2022): You know what, I think the real root cause here is /dup #6507
claunia commented 2026-01-31 04:49:08 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 22, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Aug 22, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 Help Wanted Issue-Bug Priority-3 Product-Terminal Resolution-Duplicate
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#15810
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?