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

App won't open when launched from windows #23778

New Issue
Closed
opened 2026-01-31 08:52:14 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 08:52:14 +00:00
Owner
Copy Link

Originally created by @SamKook on GitHub (Nov 2, 2025).

Windows Terminal version

1.19.10302.0 and 1.23.251008001(1.23.12811.0)

Windows build number

10.0.19045.4046

Other Software

No response

Steps to reproduce

Launch windows terminal from an app controlled by windows(start menu, desktop, file explorer).

Expected Behavior

For the app to stay open.

Actual Behavior

When I'm executing the app from a windows controlled source as mentioned above, there's a window called "DesktopWindow..."(or close to that, hard to tell) that opens and closes right away and then nothing more happens. But, if I start it from a 3rd party file explorer software like FreeCommanderXE, then the app actually opens once the DesktopWindow one closes.

I updated neither windows nor the app between when this was working fine and it started happening in the last couple months so I'm really confused on how this can even happen. I tried to update to 1.23 just now and same behavior. Both version were installed from the zip file from github.

Edit: After manually looking at the latest issues, I stumbled on https://github.com/microsoft/terminal/issues/19482 and changing the powertoys path from the PATH env var does fix the issue so that seems to be the source of the problem.
After a bit of reading, I'm guessing Windows Terminal is loading something from the powertoys folder instead of where it should actually load it, onedrive apparently has a similar issue.

Originally created by @SamKook on GitHub (Nov 2, 2025). ### Windows Terminal version 1.19.10302.0 and 1.23.251008001(1.23.12811.0) ### Windows build number 10.0.19045.4046 ### Other Software _No response_ ### Steps to reproduce Launch windows terminal from an app controlled by windows(start menu, desktop, file explorer). ### Expected Behavior For the app to stay open. ### Actual Behavior When I'm executing the app from a windows controlled source as mentioned above, there's a window called "DesktopWindow..."(or close to that, hard to tell) that opens and closes right away and then nothing more happens. But, if I start it from a 3rd party file explorer software like FreeCommanderXE, then the app actually opens once the DesktopWindow one closes. I updated neither windows nor the app between when this was working fine and it started happening in the last couple months so I'm really confused on how this can even happen. I tried to update to 1.23 just now and same behavior. Both version were installed from the zip file from github. Edit: After manually looking at the latest issues, I stumbled on https://github.com/microsoft/terminal/issues/19482 and changing the powertoys path from the PATH env var does fix the issue so that seems to be the source of the problem. After a bit of reading, I'm guessing Windows Terminal is loading something from the powertoys folder instead of where it should actually load it, onedrive apparently has a similar issue.
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:52:14 +00:00
claunia commented 2026-01-31 08:52:16 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 2, 2025):

Is there a chance you have PowerToys 0.95 or above?

@DHowett commented on GitHub (Nov 2, 2025): Is there a chance you have PowerToys 0.95 or above?
claunia commented 2026-01-31 08:52:16 +00:00
Author
Owner
Copy Link

@SamKook commented on GitHub (Nov 3, 2025):

Yeah, I have powertoys 0.95.1 installed. Like I said in my edit, disabling the PATH env var for it does fix the issue.

@SamKook commented on GitHub (Nov 3, 2025): Yeah, I have powertoys 0.95.1 installed. Like I said in my edit, disabling the PATH env var for it does fix the issue.
claunia commented 2026-01-31 08:52:16 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 3, 2025):

I indeed missed your edit. Thanks!

@DHowett commented on GitHub (Nov 3, 2025): I indeed missed your edit. Thanks!
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 Issue-Bug Needs-Triage
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#23778
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?