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

Windows Terminal crashes with Powershell 7 #1865

New Issue
Closed
opened 2026-01-30 22:40:26 +00:00 by claunia · 10 comments
claunia commented 2026-01-30 22:40:26 +00:00
Owner
Copy Link

Originally created by @teobugslayer on GitHub (Jun 22, 2019).

Windows Terminal crashes when it starts if only Windows Powershell 7 Preview 1 is installed on the machine.

Environment

Windows build number: [Version 10.0.18362.175]
Windows Terminal version (if applicable): the first preview version from Microsoft Store
Windows Powershell 7 Preview 1

Steps to reproduce

I have installed Powershell 7 preview 1 and uninstalled Powershell core 6.2.1

Expected behavior

I expect that Terminal would open with Powershell 7

Actual behavior

Windows Terminal crashes on startup. Only the border of the window is shown and then the process terminates. The following entry is recorded in Event Viewer:

Faulting application name: WindowsTerminal.exe, version: 1.0.1906.20005, time stamp: 0x5d0c1459
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000007ffdd79422
Faulting process id: 0x2fac
Faulting application start time: 0x01d528e182a35ce7
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.2.1715.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: unknown
Report Id: 85dd7eae-24e6-4dcf-bf38-6172a5dd7710
Faulting package full name: Microsoft.WindowsTerminal_0.2.1715.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Originally created by @teobugslayer on GitHub (Jun 22, 2019). Windows Terminal crashes when it starts if **only** Windows Powershell 7 Preview 1 is installed on the machine. # Environment ```none Windows build number: [Version 10.0.18362.175] Windows Terminal version (if applicable): the first preview version from Microsoft Store Windows Powershell 7 Preview 1 ``` # Steps to reproduce I have installed Powershell 7 preview 1 and uninstalled Powershell core 6.2.1 # Expected behavior I expect that Terminal would open with Powershell 7 # Actual behavior Windows Terminal crashes on startup. Only the border of the window is shown and then the process terminates. The following entry is recorded in Event Viewer: ``` Faulting application name: WindowsTerminal.exe, version: 1.0.1906.20005, time stamp: 0x5d0c1459 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0000007ffdd79422 Faulting process id: 0x2fac Faulting application start time: 0x01d528e182a35ce7 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.2.1715.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: unknown Report Id: 85dd7eae-24e6-4dcf-bf38-6172a5dd7710 Faulting package full name: Microsoft.WindowsTerminal_0.2.1715.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ```
claunia added the Resolution-DuplicateProduct-TerminalSeverity-Crash labels 2026-01-30 22:40:26 +00:00
claunia commented 2026-01-30 22:40:27 +00:00
Author
Owner
Copy Link

@magiblot commented on GitHub (Jun 23, 2019):

Shares similarities with #1364.
Here's my $PSVersionTable:

Name                           Value
----                           -----
PSVersion                      5.1.18362.145
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.18362.145
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
@magiblot commented on GitHub (Jun 23, 2019): Shares similarities with #1364. Here's my `$PSVersionTable`: ``` Name Value ---- ----- PSVersion 5.1.18362.145 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.18362.145 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1 ```
claunia commented 2026-01-30 22:40:28 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 27, 2019):

Are either of you able to use Visual Studio to deploy the developer build? We can't reproduce this on our end. :(

@DHowett-MSFT commented on GitHub (Jun 27, 2019): Are either of you able to use Visual Studio to deploy the developer build? We can't reproduce this on our end. :(
claunia commented 2026-01-30 22:40:28 +00:00
Author
Owner
Copy Link

@teobugslayer commented on GitHub (Jun 28, 2019):

The sequence to get the crash is:

  1. install PS Core 6
  2. install PS Core 7
  3. install WT
  4. launch WT. It should pick PS Core 6 as default shell
  5. uninstall PS Core 6
  6. launch WT. it should crash.
@teobugslayer commented on GitHub (Jun 28, 2019): The sequence to get the crash is: 1. install PS Core 6 1. install PS Core 7 1. install WT 1. launch WT. It should pick PS Core 6 as default shell 1. uninstall PS Core 6 1. launch WT. it should crash.
claunia commented 2026-01-30 22:40:28 +00:00
Author
Owner
Copy Link

@Forinil commented on GitHub (Jun 28, 2019):

You do not need to install and then uninstall Ps Core 6 at all. Windows Terminal will pick it up as a default shell, even if it was never installed. See #1673.

@Forinil commented on GitHub (Jun 28, 2019): You do not need to install and then uninstall Ps Core 6 at all. Windows Terminal will pick it up as a default shell, even if it was never installed. See #1673.
claunia commented 2026-01-30 22:40:28 +00:00
Author
Owner
Copy Link

@vivaladan commented on GitHub (Jul 3, 2019):

I've been having this error on an almost fresh install of Windows. No PS Core installed.
The terminal window opens and for a fraction of a second I see a flash of black which disappears showing the desktop behind and just the frame chrome.

I installed PS Core 7 and it didn't fix it.
I then installed PS Core 6 and it worked.

Does terminal require PS Core 6 to be installed?

Faulting application name: WindowsTerminal.exe, version: 1.0.1906.20005, time stamp: 0x5d0c1459
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process ID: 0x10fc
Faulting application start time: 0x01d531ccc606f71e
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.2.1715.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: unknown
Report ID: 1a066192-0dd5-4d78-80d9-3c4c1435e009
Faulting package full name: Microsoft.WindowsTerminal_0.2.1715.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
@vivaladan commented on GitHub (Jul 3, 2019): I've been having this error on an almost fresh install of Windows. No PS Core installed. The terminal window opens and for a fraction of a second I see a flash of black which disappears showing the desktop behind and just the frame chrome. I installed PS Core 7 and it didn't fix it. I then installed PS Core 6 and it worked. Does terminal require PS Core 6 to be installed? ``` Faulting application name: WindowsTerminal.exe, version: 1.0.1906.20005, time stamp: 0x5d0c1459 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0000000000000000 Faulting process ID: 0x10fc Faulting application start time: 0x01d531ccc606f71e Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.2.1715.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: unknown Report ID: 1a066192-0dd5-4d78-80d9-3c4c1435e009 Faulting package full name: Microsoft.WindowsTerminal_0.2.1715.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ```
claunia commented 2026-01-30 22:40:28 +00:00
Author
Owner
Copy Link

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

@vivaladan have you installed Windows Terminal on another computer, perhaps one where PSCore 6 is installed?

@DHowett-MSFT commented on GitHub (Jul 3, 2019): @vivaladan have you installed Windows Terminal on another computer, perhaps one where PSCore 6 _is_ installed?
claunia commented 2026-01-30 22:40:29 +00:00
Author
Owner
Copy Link

@vivaladan commented on GitHub (Jul 3, 2019):

@DHowett-MSFT Yea, previous install of Windows had PSCore 6 installed, and not 7. It was a clean format and install of Windows. I'm not on a domain, no roaming profile or such. I do use OneDrive so are you thinking something has synced through it?

@vivaladan commented on GitHub (Jul 3, 2019): @DHowett-MSFT Yea, previous install of Windows had PSCore 6 installed, and not 7. It was a clean format and install of Windows. I'm not on a domain, no roaming profile or such. I do use OneDrive so are you thinking something has synced through it?
claunia commented 2026-01-30 22:40:29 +00:00
Author
Owner
Copy Link

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

Yes, we've got an open issue about settings roaming breaking people's configurations. We chose to use the "Roaming" application data folder, which will apparently roam between computers with the same Store account. #1770

@DHowett-MSFT commented on GitHub (Jul 3, 2019): Yes, we've got an open issue about settings roaming breaking people's configurations. We chose to use the "Roaming" application data folder, which _will_ apparently roam between computers with the same Store account. #1770
claunia commented 2026-01-30 22:40:29 +00:00
Author
Owner
Copy Link

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

Also, the issue where removing powershell 6 crashes the terminal is #1458 😄

@DHowett-MSFT commented on GitHub (Jul 3, 2019): Also, the issue where removing powershell 6 crashes the terminal is #1458 :smile:
claunia commented 2026-01-30 22:40:30 +00:00
Author
Owner
Copy Link

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

When I said 1458, I meant #982.

@DHowett-MSFT commented on GitHub (Jul 3, 2019): When I said 1458, I meant #982.
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 Product-Terminal Resolution-Duplicate Severity-Crash
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#1865
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?