Terminal crashes on launch - no error in Event Viewer #3550

@angelog0 commented on GitHub (Aug 26, 2019):

@dgweller, I would say that this is very similar to #1954. Just out of curiosity, have you tried to launch WT after launching some other applications? for example Event Viewer and the WT...

@angelog0 commented on GitHub (Aug 26, 2019): @dgweller, I would say that this is very similar to #1954. Just out of curiosity, have you tried to launch WT after launching some other applications? for example Event Viewer and the WT...

claunia commented

@dgweller commented on GitHub (Aug 27, 2019):

Looks similar, but not same.

@dgweller commented on GitHub (Aug 27, 2019): Looks similar, but not same.

claunia commented

@dgweller commented on GitHub (Aug 27, 2019):

Link to Feedback to Windows team (https://aka.ms/AA5wtl6 )

@dgweller commented on GitHub (Aug 27, 2019): Link to Feedback to Windows team (https://aka.ms/AA5wtl6 )

claunia commented

@madcpt commented on GitHub (Aug 27, 2019):

Maybe check if 'powershell.exe' is included in the environment variables. When PowerShell is set as the default profile while 'powershell.exe' is not found by the system, Terminal may just crash.

@madcpt commented on GitHub (Aug 27, 2019): Maybe check if 'powershell.exe' is included in the environment variables. When PowerShell is set as the default profile while 'powershell.exe' is not found by the system, Terminal may just crash.

claunia commented

@dgweller commented on GitHub (Aug 27, 2019):

I use Powershell almost exclusively (when not using bash, which reminds me I need to edit the additional data in my issue).

@dgweller commented on GitHub (Aug 27, 2019): I use Powershell almost exclusively (when not using bash, which reminds me I need to edit the additional data in my issue).

claunia commented

@madcpt commented on GitHub (Aug 27, 2019):

@dgweller, I used PowerShell a lot too, but still 'powershell.exe' was not included in my Environment Variables. You can try using 'powershell' in cmd.exe to check if it is correctly recognized. Anyway, it solved my problem (which is very similar to yours in your description), so maybe it's worth a shot.

@madcpt commented on GitHub (Aug 27, 2019): @dgweller, I used PowerShell a lot too, but still 'powershell.exe' was not included in my Environment Variables. You can try using 'powershell' in cmd.exe to check if it is correctly recognized. Anyway, it solved my problem (which is very similar to yours in your description), so maybe it's worth a shot.

claunia commented

@pfeurean commented on GitHub (Aug 27, 2019):

I was having the problem but the solution was the exact opposite as yours. My computer reset itself and the default shell was pwsh. Once I reinstalled PowershellCore terminal opened without issue.

@pfeurean commented on GitHub (Aug 27, 2019): I was having the problem but the solution was the exact opposite as yours. My computer reset itself and the default shell was pwsh. Once I reinstalled PowershellCore terminal opened without issue.

claunia commented

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

Would you mind sharing your profiles.json?

@DHowett-MSFT commented on GitHub (Sep 3, 2019): Would you mind sharing your `profiles.json`?

claunia commented

@dgweller commented on GitHub (Sep 3, 2019):

Sorry for not responding sooner. Can you tell me where profiles.json is located? It is not in C:\Users<username>\AppData\Local\Microsoft\WindowsApps

@dgweller commented on GitHub (Sep 3, 2019): Sorry for not responding sooner. Can you tell me where profiles.json is located? It is not in C:\Users\<username>\AppData\Local\Microsoft\WindowsApps

claunia commented

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

It'll be in %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState

@DHowett-MSFT commented on GitHub (Sep 4, 2019): It'll be in `%LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState`

claunia commented

@dgweller commented on GitHub (Sep 4, 2019):

It'll be in %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState

The only file there is wt.exe

@dgweller commented on GitHub (Sep 4, 2019): > It'll be in `%LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState` The only file there is wt.exe

claunia commented

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

That's the only file in %LOCALAPPDATA%\Microsoft\WindowsApps\Microsoft.WindowsTerminal_8wekyb3d8bbwe. I'm talking about %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState (Microsoft\WindowsApps -> Packages).

@DHowett-MSFT commented on GitHub (Sep 4, 2019): That's the only file in `%LOCALAPPDATA%\Microsoft\WindowsApps\Microsoft.WindowsTerminal_8wekyb3d8bbwe`. I'm talking about `%LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState` (`Microsoft\WindowsApps` -> `Packages`).

claunia commented

@dgweller commented on GitHub (Sep 4, 2019):

Doh! It would help to, you know, READ your instructions :)
File attached.
profiles.zip

@dgweller commented on GitHub (Sep 4, 2019): Doh! It would help to, you know, READ your instructions :) File attached. [profiles.zip](https://github.com/microsoft/terminal/files/3572775/profiles.zip)

claunia commented

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

Would you mind listing the contents of C:\Program Files\PowerShell?

@DHowett-MSFT commented on GitHub (Sep 5, 2019): Would you mind listing the contents of `C:\Program Files\PowerShell`?

claunia commented

@dgweller commented on GitHub (Sep 6, 2019):

here you go (short version: Only ps6 dir directly inside the ps dir - I included ./6 in this file)
ps_dir.zip

@dgweller commented on GitHub (Sep 6, 2019): here you go (short version: Only ps6 dir directly inside the ps dir - I included ./6 in this file) [ps_dir.zip](https://github.com/microsoft/terminal/files/3584100/ps_dir.zip)

claunia commented

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

Your default profile specifies 7-preview ;)

@DHowett-MSFT commented on GitHub (Sep 6, 2019): Your default profile specifies `7-preview` ;)

claunia commented

@alex-slover commented on GitHub (Sep 7, 2019):

Just wanted to chime in and say that this is also occurring for me on a totally fresh install of Windows (1903, 18362.329) and using the current Store release. Powershell is my default shell and %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\ is on my PATH. I have not installed PSCore yet and so I have no C:\Program Files\PowerShell directory, and my profiles.json file is the default one you get through a Store installation.

@alex-slover commented on GitHub (Sep 7, 2019): Just wanted to chime in and say that this is also occurring for me on a totally fresh install of Windows (1903, 18362.329) and using the current Store release. Powershell is my default shell and `%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\` is on my PATH. I have not installed PSCore yet and so I have no `C:\Program Files\PowerShell` directory, and my `profiles.json` file is the default one you get through a Store installation.

claunia commented