Windows Terminal crashing #22810

Closed
opened 2026-01-31 08:24:11 +00:00 by claunia · 4 comments
Owner

Originally created by @vm-workarea on GitHub (Jan 28, 2025).

Windows Terminal version

1.21.3231.0

Windows build number

10.0.22631 N/A Build 22631

Other Software

Powershell 7.4.7.0

Steps to reproduce

  • Update the Powershell to 7.5.0
    • I used winget to update ( winget upgrade --id Microsoft.PowerShell)
  • Try to launch the Windows terminal once the Powershell is updated

Expected Behavior

The Windows Terminal should work like previously

Actual Behavior

  • Getting some error and Terminal is crashing.
  • Unable to use the Windows Terminal
Originally created by @vm-workarea on GitHub (Jan 28, 2025). ### Windows Terminal version 1.21.3231.0 ### Windows build number 10.0.22631 N/A Build 22631 ### Other Software Powershell **7.4.7.0** ### Steps to reproduce - Update the Powershell to **7.5.0** - I used winget to update (` winget upgrade --id Microsoft.PowerShell`) - Try to launch the Windows terminal once the Powershell is updated ### Expected Behavior The Windows Terminal should work like previously ### Actual Behavior - Getting some error and Terminal is crashing. - Unable to use the Windows Terminal
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 08:24:11 +00:00
Author
Owner

@DHowett commented on GitHub (Jan 28, 2025):

Getting some error and Terminal is crashing.

Could you share the error with us?

@DHowett commented on GitHub (Jan 28, 2025): > Getting some error and Terminal is crashing. Could you share the error with us?
Author
Owner

@AdrianoCahete commented on GitHub (Jan 29, 2025):

The problem that I had (I'm not the OP) was the closed windows/panels tried to open the old PS version path (in my case, PS was installed via other way than winget, so I need to uninstall and then install with winget), therefore returning error. I really don't know if the old panels need to find the new version from environment variables path?

@AdrianoCahete commented on GitHub (Jan 29, 2025): The problem that I had (I'm not the OP) was the closed windows/panels tried to open the old PS version path (in my case, PS was installed via other way than winget, so I need to uninstall and then install with winget), therefore returning error. I really don't know if the old panels need to find the new version from environment variables path?
Author
Owner

@vm-workarea commented on GitHub (Mar 3, 2025):

Image

Please find the attached screenshot.

@vm-workarea commented on GitHub (Mar 3, 2025): ![Image](https://github.com/user-attachments/assets/47113449-6e50-46cf-bfbe-c1540f59a758) Please find the attached screenshot.
Author
Owner

@vm-workarea commented on GitHub (Mar 3, 2025):

I do use the below command to update the Powershell

winget upgrade --id Microsoft.Powershell

Experienced the same issue with 7.6.0-preview.3

Note: For time being I downgraded the Powershell to 7.4.7

@vm-workarea commented on GitHub (Mar 3, 2025): I do use the below command to update the `Powershell` `winget upgrade --id Microsoft.Powershell` Experienced the same issue with [7.6.0-preview.3](https://github.com/PowerShell/PowerShell/compare/v7.6.0-preview.2...v7.6.0-preview.3) **Note:** For time being I downgraded the `Powershell` to `7.4.7`
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22810