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 fails to launch when installed from the store #3581

New Issue
Closed
opened 2026-01-30 23:24:52 +00:00 by claunia · 6 comments
claunia commented 2026-01-30 23:24:52 +00:00
Owner
Copy Link

Originally created by @mukaschultze on GitHub (Aug 27, 2019).

Environment

Microsoft Windows [Version 10.0.18362.295]
Any other software? No

Steps to reproduce

Install the application from Windows Store (or from binaries released on this repo) and launch it, it results in the following error:

image

Builds made on my machine launches just fine, so I don't know how I can get more info to debug this issue (they crash after using it for a while, but I don't think this is related to the same bug).

Expected behavior

The application installed from the store should launch just like the ones built on my machine.

Actual behavior

It crashes, with the error File system error (12029).

Originally created by @mukaschultze on GitHub (Aug 27, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Microsoft Windows [Version 10.0.18362.295] Any other software? No ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Install the application from Windows Store (or from binaries released on this repo) and launch it, it results in the following error: ![image](https://user-images.githubusercontent.com/13923364/63764494-526ff380-c89d-11e9-8679-dfb8ffc2d608.png) Builds made on my machine launches just fine, so I don't know how I can get more info to debug this issue (they crash after using it for a while, but I don't think this is related to the same bug). # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> The application installed from the store should launch just like the ones built on my machine. # Actual behavior <!-- What's actually happening? --> It crashes, with the error `File system error (12029).`
claunia added the Resolution-ExternalNeeds-Tag-Fix labels 2026-01-30 23:24:53 +00:00
claunia commented 2026-01-30 23:24:53 +00:00
Author
Owner
Copy Link

@sergio-nsk commented on GitHub (Aug 27, 2019):

Very similar, but another error code.

[Window Title]
C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe

[Content]
C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe

	File system error (12007).

[OK]
@sergio-nsk commented on GitHub (Aug 27, 2019): Very similar, but another error code. ``` [Window Title] C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe [Content] C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe File system error (12007). [OK] ```
claunia commented 2026-01-30 23:24:54 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Aug 29, 2019):

Do you have a third-party AV or firewall solution installed?

@DHowett-MSFT commented on GitHub (Aug 29, 2019): Do you have a third-party AV or firewall solution installed?
claunia commented 2026-01-30 23:24:54 +00:00
Author
Owner
Copy Link

@mukaschultze commented on GitHub (Aug 30, 2019):

I'm not running any third-party AV and firewalls.

I tried running it with Windows firewall disabled just in case, and... it launched...
So I reenabled the firewall and tested it again, now it is working all the times, even after uninstalling and reinstalling it.

I think it's worth mentioning that the app was allowed through the firewall in the settings while it was crashing.

Solution

In case anyone runs into the same issue in the future: Disable Windows firewall, start the terminal application and then reenable the firewall.

@mukaschultze commented on GitHub (Aug 30, 2019): I'm not running any third-party AV and firewalls. I tried running it with Windows firewall disabled just in case, and... it launched... So I reenabled the firewall and tested it again, now it is working all the times, even after uninstalling and reinstalling it. I think it's worth mentioning that the app was allowed through the firewall in the settings while it was crashing. ### Solution In case anyone runs into the same issue in the future: Disable Windows firewall, start the terminal application and then reenable the firewall.
claunia commented 2026-01-30 23:24:54 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 5, 2019):

Thanks for confirming. We've seen something like this before, but we have no idea what causes it. It's definitely external to our project. ☹️

@DHowett-MSFT commented on GitHub (Sep 5, 2019): Thanks for confirming. We've seen something like this before, but we have no idea what causes it. It's definitely external to our project. ☹️
claunia commented 2026-01-30 23:24:54 +00:00
Author
Owner
Copy Link

@xairoo commented on GitHub (Feb 16, 2020):

In case anyone runs into the same issue in the future: Disable Windows firewall, start the terminal application and then reenable the firewall.

Same for NetLimiter.

@xairoo commented on GitHub (Feb 16, 2020): > In case anyone runs into the same issue in the future: Disable Windows firewall, start the terminal application and then reenable the firewall. Same for NetLimiter.
claunia commented 2026-01-30 23:24:55 +00:00
Author
Owner
Copy Link

@ericgl commented on GitHub (Aug 10, 2021):

I installed the latest version of Terminal (v1.10.1933.0), and upon launch - it gave me this error (12029).
It seems to be caused by my firewall app. After disabling it, Terminal launched normally. I then re-enabled my firewall app.
Strange behavior...

@ericgl commented on GitHub (Aug 10, 2021): I installed the latest version of Terminal (v1.10.1933.0), and upon launch - it gave me this error (**12029**). It seems to be caused by my firewall app. After disabling it, Terminal launched normally. I then re-enabled my firewall app. Strange behavior...
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 Needs-Tag-Fix Resolution-External
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#3581
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?