Closed ninbura closed 7 months ago
Hi I'm an AI powered bot that finds similar issues based off the issue title.
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
From what I can tell, this started to occur after updating Windows Terminal to version 1.19.10292.0
. The issue is replicable on 3 systems that I own, all on different chipsets, but running the same Windows Edition, Version, & OS Build.
Windows 11 Pro N for Workstations
23H2
22631.3085
There is another issue on the PowerShell repository (https://github.com/PowerShell/PowerShell/issues/20595) that mentions this same error, but it has been closed as it was mentioned to be an issue with Windows terminal; linking to this https://github.com/microsoft/terminal/issues/16051. Which has been locked due to participant's "spicy" behavior. However, I'm not sure I have the same issue as running the Get-EnvsWithEmbeddedNull script mentioned in https://github.com/microsoft/terminal/issues/16051 does not list any corrupt registry entries on any of my 3 systems.
I guess this is a bug in the v1.19 Release and will be probably fixed in v1.20. See: https://github.com/microsoft/terminal/releases/tag/v1.20.10303.0
Yea pretty sure this is /dup #16623, which is already fixed in v1.19.10302.0
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!
Windows Terminal version
1.19.10292.0
Windows build number
10.0.22631.0
Other Software
PowerShell 7 - v7.4.1 PowerShell - v5.1.22621.2506
Steps to reproduce
via run
wt pwsh
via shell
wt pwsh
orwt PowerShell
nuance
For whatever reason I've found that it is sometimes necessary to run
wt [shell]
more than once before Windows Terminal will even launch to print the error message. Almost as if Terminal itself is hard crashing before it can display.Expected Behavior
wt pwsh
launches Windows Terminal with the PowerShell 7 profile without error.wt PowerShell
launches Windows Terminal with the PowerShell profile without error.Actual Behavior
wt pwsh
launches Windows Terminal with the PowerShell 7 profile and displays the following error & exit code:wt PowerShell
launches Windows Terminal with the PowerShell profile and displays the following error & exit code: