Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Terminal quits immediately if %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\ is not on PATH #3697

Closed
rossng opened this issue Nov 25, 2019 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@rossng
Copy link

rossng commented Nov 25, 2019

Environment

Windows build number: Win32NT             10.0.18362.0 Microsoft Windows NT 10.0.18362.0
Windows Terminal version (if applicable): 0.6.2951.0

Any other software?

Steps to reproduce

  1. Remove %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\ from your system PATH variable
  2. Start Windows Terminal

Expected behavior

Windows Terminal warns you that PowerShell cannot be found, or perhaps launches a fallback cmd session instead. I encountered this issue because some unruly installer erased my PATH 😒

Actual behavior

The Windows Terminal UI flashes briefly and immediately quits.

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Nov 25, 2019
@DHowett-MSFT
Copy link
Contributor

Hey, you're in luck! We just fixed this, but unfortunately it's not going out on the current release train. /dup #2563

@ghost
Copy link

ghost commented Nov 25, 2019

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!

@ghost ghost closed this as completed Nov 25, 2019
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Nov 25, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants