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

Windows Terminal works once, and then refuses to start afterwards #4818

New Issue
Closed
opened 2026-01-30 23:57:21 +00:00 by claunia · 11 comments
claunia commented 2026-01-30 23:57:21 +00:00
Owner
Copy Link

Originally created by @dalgibbard on GitHub (Nov 5, 2019).

Originally assigned to: @DHowett-MSFT on GitHub.

Feedback Hub ref: https://aka.ms/AA6h5a5

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.449]
Windows Terminal version (if applicable): 0.6.2951.0

Steps to reproduce

  • Install via Microsoft Store
  • Run once, change no settings, just exit the application
  • Try to run the application again. Refuses to start

Uninstalling and re-installing allows me to run it once before it stops working again.
The following shows in Event Viewer:

Faulting application name: WindowsTerminal.exe, version: 1.0.1910.22001, time stamp: 0x5daf7ab2
Faulting module name: ucrtbase.dll, version: 10.0.18362.387, time stamp: 0x4361b720
Exception code: 0xc0000409
Fault offset: 0x000000000006db8e
Faulting process ID: 0x648
Faulting application start time: 0x01d593d9ad986ce2
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report ID: 12631cc9-d497-4e43-b19a-b38d76e9dc8e
Faulting package full name: Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Expected behavior

  • Expect application to start repeatably

Actual behavior

  • Windows Terminal not starting after first run
Originally created by @dalgibbard on GitHub (Nov 5, 2019). Originally assigned to: @DHowett-MSFT on GitHub. Feedback Hub ref: https://aka.ms/AA6h5a5 # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18363.449] Windows Terminal version (if applicable): 0.6.2951.0 ``` # Steps to reproduce * Install via Microsoft Store * Run once, change no settings, just exit the application * Try to run the application again. Refuses to start Uninstalling and re-installing allows me to run it once before it stops working again. The following shows in Event Viewer: ```none Faulting application name: WindowsTerminal.exe, version: 1.0.1910.22001, time stamp: 0x5daf7ab2 Faulting module name: ucrtbase.dll, version: 10.0.18362.387, time stamp: 0x4361b720 Exception code: 0xc0000409 Fault offset: 0x000000000006db8e Faulting process ID: 0x648 Faulting application start time: 0x01d593d9ad986ce2 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Windows\System32\ucrtbase.dll Report ID: 12631cc9-d497-4e43-b19a-b38d76e9dc8e Faulting package full name: Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ``` # Expected behavior * Expect application to start repeatably # Actual behavior * Windows Terminal not starting after first run
claunia commented 2026-01-30 23:57:22 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 7, 2019):

Hey @dalgibbard! Thanks for the report.

Would you mind sharing your profiles.json? It's in %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\ (since you can't launch Terminal to get at it 😀)

@DHowett-MSFT commented on GitHub (Nov 7, 2019): Hey @dalgibbard! Thanks for the report. Would you mind sharing your `profiles.json`? It's in `%LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\` (since you can't launch Terminal to get at it 😀)
claunia commented 2026-01-30 23:57:22 +00:00
Author
Owner
Copy Link

@dalgibbard commented on GitHub (Nov 8, 2019):

Ah, i posted a reply to this with the code in it, but it's not here now? Must've had a sketchy network connection at the time.

Today I bit the bullet and installed the Fast Ring build (10.0.19018.1), and after reinstalling Windows Terminal it works correctly.
So; I no longer have access to the profile.json which had an issue, and after upgrading Windows to the fast ring (was: slow ring), I no longer have the issue.

@dalgibbard commented on GitHub (Nov 8, 2019): Ah, i posted a reply to this with the code in it, but it's not here now? Must've had a sketchy network connection at the time. Today I bit the bullet and installed the Fast Ring build (10.0.19018.1), and after reinstalling Windows Terminal it works correctly. So; I no longer have access to the profile.json which had an issue, and after upgrading Windows to the fast ring (was: slow ring), I no longer have the issue.
claunia commented 2026-01-30 23:57:22 +00:00
Author
Owner
Copy Link

@dalgibbard commented on GitHub (Nov 8, 2019):

Whoops I take that back; it's not opening again now; since it was working i've installed docker (with WSL2 integration), set that up for use with WSL2 and rebooted a bunch of times.

So issue still persists on latest windows fast ring build too :(

It looks like the same issue at face value at least; have grabbed another set of diag data to compare.
This is from Windows 10.0.19018.1: https://aka.ms/AA6isq0

Profiles json (with extension changed to allow it to be uploaded straight to github :) )
profiles.json.txt

@dalgibbard commented on GitHub (Nov 8, 2019): Whoops I take that back; it's not opening again now; since it was working i've installed docker (with WSL2 integration), set that up for use with WSL2 and rebooted a bunch of times. So issue still persists on latest windows fast ring build too :( It looks like the same issue at face value at least; have grabbed another set of diag data to compare. This is from Windows 10.0.19018.1: https://aka.ms/AA6isq0 Profiles json (with extension changed to allow it to be uploaded straight to github :) ) [profiles.json.txt](https://github.com/microsoft/terminal/files/3825554/profiles.json.txt)
claunia commented 2026-01-30 23:57:22 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 8, 2019):

And if you just run wsl -d Ubuntu directly, it works?

@DHowett-MSFT commented on GitHub (Nov 8, 2019): And if you just run `wsl -d Ubuntu` directly, it works?
claunia commented 2026-01-30 23:57:23 +00:00
Author
Owner
Copy Link

@dalgibbard commented on GitHub (Nov 9, 2019):

Yes indeed, running wsl -d Ubuntu from cmd.exe, works fine.

@dalgibbard commented on GitHub (Nov 9, 2019): Yes indeed, running ```wsl -d Ubuntu``` from cmd.exe, works fine.
claunia commented 2026-01-30 23:57:23 +00:00
Author
Owner
Copy Link

@nizmow commented on GitHub (Nov 15, 2019):

I'm getting what seems to be the exact same behaviour, but I'm building from source. Slightly different information is shown in the event log:

Faulting application name: WindowsTerminal.exe, version: 0.0.0.0, time stamp: 0x5dce6789
Faulting module name: InputHost.dll, version: 10.0.18362.387, time stamp: 0x1217c36e
Exception code: 0xc0000409
Fault offset: 0x0000000000041a73
Faulting process id: 0x3f68
Faulting application start time: 0x01d59bb49d507fdb
Faulting application path: C:\Code\third_party\Terminal\src\cascadia\CascadiaPackage\bin\x64\Release\AppX\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\InputHost.dll
Report Id: fd4f1b3a-c074-47ce-94c2-2c8fc0cce74d
Faulting package full name: WindowsTerminalDev_0.0.1.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

My profiles.json isn't anything special, the default tab is standard Powershell.

Built this morning from master branch:

commit ebdcfbd9400d505978675f0610275e72ebb70208 (HEAD -> master, tag: v0.6.3181.0, origin/master, origin/HEAD)

@nizmow commented on GitHub (Nov 15, 2019): I'm getting what seems to be the exact same behaviour, but I'm building from source. Slightly different information is shown in the event log: ``` Faulting application name: WindowsTerminal.exe, version: 0.0.0.0, time stamp: 0x5dce6789 Faulting module name: InputHost.dll, version: 10.0.18362.387, time stamp: 0x1217c36e Exception code: 0xc0000409 Fault offset: 0x0000000000041a73 Faulting process id: 0x3f68 Faulting application start time: 0x01d59bb49d507fdb Faulting application path: C:\Code\third_party\Terminal\src\cascadia\CascadiaPackage\bin\x64\Release\AppX\WindowsTerminal.exe Faulting module path: C:\Windows\System32\InputHost.dll Report Id: fd4f1b3a-c074-47ce-94c2-2c8fc0cce74d Faulting package full name: WindowsTerminalDev_0.0.1.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ``` My `profiles.json` isn't anything special, the default tab is standard Powershell. Built this morning from master branch: `commit ebdcfbd9400d505978675f0610275e72ebb70208 (HEAD -> master, tag: v0.6.3181.0, origin/master, origin/HEAD)`
claunia commented 2026-01-30 23:57:23 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 15, 2019):

Since you built it from source, can you run it inside Visual Studio and capture a stack trace? That’ll be really helpful :)

@DHowett-MSFT commented on GitHub (Nov 15, 2019): Since you built it from source, can you run it inside Visual Studio and capture a stack trace? That’ll be really helpful :)
claunia commented 2026-01-30 23:57:23 +00:00
Author
Owner
Copy Link

@dgibbard-cisco commented on GitHub (Nov 23, 2019):

OK i found something of interest; In Settings> Storage> "Change Where New Content Is Saved", I had this set to save new apps to drive "F:" (which is a Storage Spaces RAID1 across 2x 2TB HDDs) - I'd set this so that Xbox (Beta) games were saved to this drive; seems it affects all microsoft store apps.

After uninstalling Windows Terminal, setting this back to "C:" and re-installing, it now works correctly!

@dgibbard-cisco commented on GitHub (Nov 23, 2019): OK i found something of interest; In Settings> Storage> "Change Where New Content Is Saved", I had this set to save new apps to drive "F:" (which is a Storage Spaces RAID1 across 2x 2TB HDDs) - I'd set this so that Xbox (Beta) games were saved to this drive; seems it affects all microsoft store apps. After uninstalling Windows Terminal, setting this back to "C:" and re-installing, it now works correctly!
claunia commented 2026-01-30 23:57:23 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 23, 2019):

? ! ?

Well, that's not supposed to happen! Thanks for following up, that's really concerning.

@DHowett-MSFT commented on GitHub (Nov 23, 2019): ? ! ? Well, that's not supposed to happen! Thanks for following up, that's really concerning.
claunia commented 2026-01-30 23:57:23 +00:00
Author
Owner
Copy Link

@nizmow commented on GitHub (Nov 25, 2019):

Follow up from earlier: I'm a C# developer, not a C++ developer, and wrangling Visual Studio to get a stack trace was sadly beyond me (even in Debug mode, the exception wouldn't give me much but an opportunity disassemble to assembler, which didn't seem that useful).

However, to follow up on this last comment, I'm in an enterprise environment was using folder redirection (to a network share) for a lot of things. I've recently asked IT to switch this off, and surprise, Terminal now works fine all the time. So we may be onto something here.

@nizmow commented on GitHub (Nov 25, 2019): Follow up from earlier: I'm a C# developer, not a C++ developer, and wrangling Visual Studio to get a stack trace was sadly beyond me (even in Debug mode, the exception wouldn't give me much but an opportunity disassemble to assembler, which didn't seem that useful). However, to follow up on this last comment, I'm in an enterprise environment was using folder redirection (to a network share) for a lot of things. I've recently asked IT to switch this off, and surprise, Terminal now works fine all the time. So we may be onto something here.
claunia commented 2026-01-30 23:57:24 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 29, 2020):

It's been a while since we got a good repro for this, so I'm going to close it out. Let me know if it's still a problem!
Thanks
d

@DHowett-MSFT commented on GitHub (Jan 29, 2020): It's been a while since we got a good repro for this, so I'm going to close it out. Let me know if it's still a problem! Thanks d
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-Attention Needs-Tag-Fix Product-Terminal Resolution-No-Repro Severity-Crash
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#4818
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?