Impossible to start Terminal #2905

Closed
opened 2026-01-30 23:08:30 +00:00 by claunia · 5 comments
Owner

Originally created by @toomanysecrets on GitHub (Jul 24, 2019).

Environment

Windows build number: [Versión 10.0.18362.239]
Windows Terminal version (if applicable): 0.2.1831.0

Any other software?
```none

# Steps to reproduce

Install Cmder with Chocolatey, and ConEmu also.
Open Microsoft Store, install Terminal Preview.
Uninstall ConEmu (in this order) and later Cmder.
Terminal refuse to start at this point. 

# Expected behavior

Open the Terminal app.

# Actual behavior

Impossible to run Terminal. If I try to execute through Powershell (using "wt" command) I can only obtain the message: "Last command exited with error status."

Originally created by @toomanysecrets on GitHub (Jul 24, 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. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [Versión 10.0.18362.239] Windows Terminal version (if applicable): 0.2.1831.0 Any other software? ```none # Steps to reproduce Install Cmder with Chocolatey, and ConEmu also. Open Microsoft Store, install Terminal Preview. Uninstall ConEmu (in this order) and later Cmder. Terminal refuse to start at this point. # Expected behavior Open the Terminal app. # Actual behavior Impossible to run Terminal. If I try to execute through Powershell (using "wt" command) I can only obtain the message: "Last command exited with error status."
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-30 23:08:30 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Jul 24, 2019):

Does the terminal launch normally through the start menu? Or is it only launching from the execution alias (wt.exe) that doesn't work?

Did the terminal work before installing/uninstalling conemu, cmder?

@zadjii-msft commented on GitHub (Jul 24, 2019): Does the terminal launch normally through the start menu? Or is it only launching from the execution alias (`wt.exe`) that doesn't work? Did the terminal work _before_ installing/uninstalling conemu, cmder?
Author
Owner

@toomanysecrets commented on GitHub (Jul 25, 2019):

I have to try directly with wt.exe because was impossible to start through the start menu.

Installed Cmder: just the same. Doesn't start from the menu or "wt.exe". When I try from a PowerShell terminal the message is the same: "Last command exited with error status".

Installed ConEmu (and uninstalling Cmder first): is like Cmder; doesn't run.

Installed ConEmu also with Cmder: the error persists. I cannot start the app.

Thank you so much for your work and help.

@toomanysecrets commented on GitHub (Jul 25, 2019): I have to try directly with wt.exe because was impossible to start through the start menu. Installed Cmder: just the same. Doesn't start from the menu or "wt.exe". When I try from a PowerShell terminal the message is the same: "Last command exited with error status". Installed ConEmu (and uninstalling Cmder first): is like Cmder; doesn't run. Installed ConEmu also with Cmder: the error persists. I cannot start the app. Thank you so much for your work and help.
Author
Owner

@zadjii-msft commented on GitHub (Jul 25, 2019):

So I'm going to go out on a limb and suggest that conemu and cmder have no correlation to this issue, since the terminal didn't work even with them.

Could you share your profiles.json file? It should be in %userprofile%\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState\

@zadjii-msft commented on GitHub (Jul 25, 2019): So I'm going to go out on a limb and suggest that conemu and cmder have no correlation to this issue, since the terminal didn't work even with them. Could you share your `profiles.json` file? It should be in `%userprofile%\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState\`
Author
Owner

@toomanysecrets commented on GitHub (Jul 26, 2019):

Looking the profiles.json file, I look that the first profile (powershell) has a fontFace that I don't have installed at this momment so, I just edited the profiles.json, put an existed font and all is running again like a farm ;-)

@toomanysecrets commented on GitHub (Jul 26, 2019): Looking the profiles.json file, I look that the first profile (powershell) has a fontFace that I don't have installed at this momment so, I just edited the profiles.json, put an existed font and all is running again like a farm ;-)
Author
Owner

@toomanysecrets commented on GitHub (Jul 26, 2019):

Looking the profiles.json file, I look that the first profile (powershell) has a fontFace that I don't have installed at this moment so, I just edited the profiles.json, put an existed font and all is running again like a farm ;-)
Maybe, it will be a great thing that if the app detects a wrong fontFace, it can communicate or use something like a "defaultfont".
I will apologize about my English because it isn't my mother tongue.

Thank you so much for your great help and attention.

@toomanysecrets commented on GitHub (Jul 26, 2019): Looking the profiles.json file, I look that the first profile (powershell) has a fontFace that I don't have installed at this moment so, I just edited the profiles.json, put an existed font and all is running again like a farm ;-) Maybe, it will be a great thing that if the app detects a wrong fontFace, it can communicate or use something like a "defaultfont". I will apologize about my English because it isn't my mother tongue. Thank you so much for your great help and attention.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#2905