microsoft / terminal

The new Windows Terminal and the original Windows console host, all in the same place!
MIT License
95.23k stars 8.27k forks source link

Startup Crash Frequently #9831

Closed mingsxs closed 3 years ago

mingsxs commented 3 years ago

Windows Terminal version (or Windows build number)

Windows build number: 18363.1440 Windows Terminal version: 1.7.1033.0

Other Software

Nothing

Steps to reproduce

Just double click it will crash and exit, very little chance it can start up successfully.

Expected Behavior

No response

Actual Behavior

double click to open and then it crashes and exits.

mingsxs commented 3 years ago

Sorry that I closed it accidentally.

mingsxs commented 3 years ago

Screenshot 2021-04-15 140840

mingsxs commented 3 years ago

You can see clearly from the screenshot, after opening the terminal, the window leaves blank and soon it will exit with No Response.

igitur commented 3 years ago

@mingsxs Same here. I installed Terminal using scoop package manager. I'm just wondering how you installed it. Maybe that's relevant here.

igitur commented 3 years ago

If I uninstall my current instance (that I originally installed through scoop package manager) and I download the .msixbundle file from https://github.com/microsoft/terminal/releases/tag/v1.7.1033.0 and install it manually using Add-AppPackage in PowerShell, then Windows Terminal opens successfully.

If I remove it again using Remove-AppPackage and reinstall it via scoop package manager, it fails again. So I'm guessing something is wrong with the scoop install script.

justinkb commented 3 years ago

If I uninstall my current instance (that I originally installed through scoop package manager) and I download the .msixbundle file from https://github.com/microsoft/terminal/releases/tag/v1.7.1033.0 and install it manually using Add-AppPackage in PowerShell, then Windows Terminal opens successfully.

If I remove it again using Remove-AppPackage and reinstall it via scoop package manager, it fails again. So I'm guessing something is wrong with the scoop install script.

https://github.com/lukesampson/scoop-extras/blob/master/bucket/windows-terminal.json

doubtful anything is wrong with the script, most likely it's just intermittent failures and it happened to work a few times when you installed it manually

zadjii-msft commented 3 years ago

/dup #9821

Scoop installs terminal in an unsupported way. We're working on fixing it, but we have never supported the way that they installed us.

ghost commented 3 years ago

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!

mingsxs commented 3 years ago

@igitur Hey there, yeah, I do install with scoop, didn't realize that it could be relevant to it. Thanks for this information