Bug Report: Initial settings - Power Shell 6 detected even if not present #2324

Closed
opened 2026-01-30 22:52:27 +00:00 by claunia · 2 comments
Owner

Originally created by @Forinil on GitHub (Jun 27, 2019).

Environment

Windows build number: 10.0.18362.175
Windows Terminal version (if applicable): from Windows Store

Any other software?
PowerShell Core 7 preview

Steps to reproduce

Install Windows Terminal on Windows without PowerShell Core 6, but with PowerShell Core 7 installed.
Run Windows Terminal.

Expected behavior

Windows Terminal opens with either PowerShell Core 7 or Windows PowerShell or cmd as the default console.

Actual behavior

Windows Terminal crashes.

Reason for the crash

The profile.json file contains entry for PowerShell 6 Core set as default console.

Originally created by @Forinil on GitHub (Jun 27, 2019). <!-- 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: 10.0.18362.175 Windows Terminal version (if applicable): from Windows Store Any other software? PowerShell Core 7 preview ``` # Steps to reproduce Install Windows Terminal on Windows without PowerShell Core 6, but with PowerShell Core 7 installed. Run Windows Terminal. # Expected behavior Windows Terminal opens with either PowerShell Core 7 or Windows PowerShell or cmd as the default console. # Actual behavior Windows Terminal crashes. # Reason for the crash The `profile.json` file contains entry for PowerShell 6 Core set as default console.
claunia added the Needs-Tag-FixResolution-Duplicate labels 2026-01-30 22:52:27 +00:00
Author
Owner

@WSLUser commented on GitHub (Jun 27, 2019):

PS6Core is supposed to replace Windows Powershell as the Powershell that ships with Windows since there's a compatibility module to ensure Windows specific modules can be accessed (though still alittle buggy at this time in my experience). CMD would probably be the best default for now since you can quickly switch to Powershell or other shells/terminals. Current workaround is to manually update profile.json to specify CMD (or Windows PS technically).

@WSLUser commented on GitHub (Jun 27, 2019): PS6Core is supposed to replace Windows Powershell as the Powershell that ships with Windows since there's a compatibility module to ensure Windows specific modules can be accessed (though still alittle buggy at this time in my experience). CMD would probably be the best default for now since you can quickly switch to Powershell or other shells/terminals. Current workaround is to manually update `profile.json` to specify CMD (or Windows PS technically).
Author
Owner

@miniksa commented on GitHub (Jun 27, 2019):

Dupe of #1399.

@miniksa commented on GitHub (Jun 27, 2019): Dupe of #1399.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#2324