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

Error starting up after installing PowerShell 7 #6751

New Issue
Closed
opened 2026-01-31 00:46:28 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 00:46:28 +00:00
Owner
Copy Link

Originally created by @fr3dd on GitHub (Mar 5, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.0]
Windows Terminal version: v0.9.433.0

Steps to reproduce

Install PowerShell 7 on a system with a working copy of Windows Terminal (Preview) and open a PowerShell Core session.

Expected behavior

Successfully start a new PowerShell Core session in Windows Terminal (Preview).

Actual behavior

When starting a new PowerShell Core session, you receive the following error message:

[error 0x80070002 when launching 'C:\Program Files\PowerShell\6\pwsh.exe']

This appears to be failing because the installation of PowerShell 7 removes the old directory (C:\Program Files\PowerShell\6) and creates a new one (C:\Program Files\PowerShell\7). In the default profiles.json, the following value called commandline needs to be changed from "C:\\Program Files\\PowerShell\\6\\pwsh.exe" to "C:\\Program Files\\PowerShell\\7\\pwsh.exe".
The issue can be addressed by updating the value, but many people are not going to be able to figure that out on their own.

Originally created by @fr3dd on GitHub (Mar 5, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 Windows build number: Microsoft Windows [Version 10.0.18362.0] Windows Terminal version: v0.9.433.0 # Steps to reproduce Install PowerShell 7 on a system with a working copy of Windows Terminal (Preview) and open a PowerShell Core session. # Expected behavior Successfully start a new PowerShell Core session in Windows Terminal (Preview). # Actual behavior When starting a new PowerShell Core session, you receive the following error message: `[error 0x80070002 when launching 'C:\Program Files\PowerShell\6\pwsh.exe']` This appears to be failing because the installation of PowerShell 7 removes the old directory (C:\Program Files\PowerShell\6) and creates a new one (C:\Program Files\PowerShell\7). In the default profiles.json, the following value called **commandline** needs to be changed from `"C:\\Program Files\\PowerShell\\6\\pwsh.exe"` to `"C:\\Program Files\\PowerShell\\7\\pwsh.exe"`. The issue can be addressed by updating the value, but many people are not going to be able to figure that out on their own.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 00:46:28 +00:00
claunia commented 2026-01-31 00:46:29 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 5, 2020):

This is only true if you are using a version of the powershell profile generated before 0.5 (October 2019). Terminal now detects the existence of pwsh.exe in a bunch of locations and automatically chooses one.

If you have an old profile with hundreds of keybindings and full profile blocks, it’s probably a great time to refresh it by deleting it.

@DHowett-MSFT commented on GitHub (Mar 5, 2020): This is only true if you are using a version of the powershell profile generated before 0.5 (October 2019). Terminal now detects the existence of `pwsh.exe` in a bunch of locations and automatically chooses one. If you have an old profile with hundreds of keybindings and full profile blocks, it’s probably a great time to [refresh it](https://www.hanselman.com/blog/NowIsTheTimeToMakeAFreshNewWindowsTerminalProfilesjson.aspx) by deleting it.
claunia commented 2026-01-31 00:46:29 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 5, 2020):

Thanks for the report! Given that our settings architecture is still evolving, and that this was fixed by circumstance, I’m gonna close it out for now.

@DHowett-MSFT commented on GitHub (Mar 5, 2020): Thanks for the report! Given that our settings architecture is still evolving, and that this was fixed by circumstance, I’m gonna close it out for now.
claunia commented 2026-01-31 00:46:29 +00:00
Author
Owner
Copy Link

@g0t4 commented on GitHub (Sep 19, 2021):

This is happening in 1.11. I modified my commandline setting for powershell (not preview) ... setting it to "pwsh.exe -nologo" to hide the banner. If I launch Windows Terminal Preview directly it opens just fine. If however, I use the "app execution alias" which I have mapped to Windows Terminal Preview and then I open preview via "wt" it breaks:

[error 0x80070002 when launching `pwsh -nologo']

And, setting the "commandline" to just "pwsh" also breaks it.

@g0t4 commented on GitHub (Sep 19, 2021): This is happening in 1.11. I modified my commandline setting for powershell (not preview) ... setting it to "pwsh.exe -nologo" to hide the banner. If I launch Windows Terminal Preview directly it opens just fine. If however, I use the "app execution alias" which I have mapped to Windows Terminal Preview and then I open preview via "wt" it breaks: [error 0x80070002 when launching `pwsh -nologo'] And, setting the "commandline" to just "pwsh" also breaks it.
claunia commented 2026-01-31 00:46:30 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 20, 2021):

This is happening in 1.11. I modified my commandline setting for powershell (not preview) ... setting it to "pwsh.exe -nologo" to hide the banner. If I launch Windows Terminal Preview directly it opens just fine. If however, I use the "app execution alias" which I have mapped to Windows Terminal Preview and then I open preview via "wt" it breaks:

[error 0x80070002 when launching `pwsh -nologo']

And, setting the "commandline" to just "pwsh" also breaks it.

This suggests that the PowerShell installation location is not on your system PATH.

@DHowett commented on GitHub (Sep 20, 2021): > This is happening in 1.11. I modified my commandline setting for powershell (not preview) ... setting it to "pwsh.exe -nologo" to hide the banner. If I launch Windows Terminal Preview directly it opens just fine. If however, I use the "app execution alias" which I have mapped to Windows Terminal Preview and then I open preview via "wt" it breaks: > > > > [error 0x80070002 when launching `pwsh -nologo'] > > > > And, setting the "commandline" to just "pwsh" also breaks it. > > This suggests that the PowerShell installation location is not on your system `PATH`.
claunia commented 2026-01-31 00:46:30 +00:00
Author
Owner
Copy Link

@g0t4 commented on GitHub (Sep 20, 2021):

Yeah I saw some other red flags, haven't had time to investigate yet. It's
odd that it only happens under some circumstances and not others. I'll do
some more digging and see if maybe it's just a Win 11 Insiders build issue
or otherwise a bug in a Preview build of something (terminal or ps).

@g0t4 commented on GitHub (Sep 20, 2021): Yeah I saw some other red flags, haven't had time to investigate yet. It's odd that it only happens under some circumstances and not others. I'll do some more digging and see if maybe it's just a Win 11 Insiders build issue or otherwise a bug in a Preview build of something (terminal or ps).
claunia commented 2026-01-31 00:46:30 +00:00
Author
Owner
Copy Link

@ebicoglu commented on GitHub (Jan 4, 2022):

Solved like this:

image

@ebicoglu commented on GitHub (Jan 4, 2022): Solved like this: ![image](https://user-images.githubusercontent.com/9526587/148068556-5d14f586-1183-4060-8712-adf7e6afe005.png)
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 Needs-Triage
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#6751
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?