Cannot start wt through "Run"

[Anans2]

Windows Terminal version

1.20.11781.0

Windows build number

10.0.26120.670

Other Software

No response

Steps to reproduce

win+R then type "wt" in Run

Expected Behavior

Start the terminal

Actual Behavior

wt crashed immediately, with the same logs just like #13193.

AppName WindowsTerminal.exe
AppVersion 1.21.2406.25002
AppTimeStamp 667b71e3
ModuleName ucrtbase.dll
ModuleVersion 10.0.26100.751
ModuleTimeStamp cdc60ec5
ExceptionCode c0000409
FaultingOffset 00000000000a514e
ProcessId 0x918
ProcessCreationTime 0x1dac9cdc051aa8e
AppPath C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.21.1772.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
ModulePath C:\WINDOWS\System32\ucrtbase.dll
IntegratorReportId 53217967-c8f2-46a6-9b33-7883da184a4d
PackageFullName
PackageRelativeAppId

However, with any other ways to start, like start menu, right-click menu or run "wt" in another terminal, it works well.

[github-actions]

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!

Closed similar issues:

• Windows Terminal's wt.exe throws exception 0xc0000409 when trying to start it from the Run box/Start menu (#14219), similarity score: 0.84
• Windows Terminal crash with wt.exe (#12139), similarity score: 0.84
• wt command crash in "Windows + R" input popup (#11480), similarity score: 0.81

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[vinzmoke-zoro]

Works perfectly fine for me on windows 11 home 23H2.

[ThomasETN]

I got the same issue on Windows 10 22H2 (Microsoft Windows NT 10.0.19045.0).
Executing wt through "Run" fails immediately, an event viewer entry shows:

Faulting application name: WindowsTerminal.exe, version: 1.20.2405.17001, time stamp: 0x66479c60
Faulting module name: ucrtbase.dll, version: 10.0.19041.3636, time stamp: 0x81cf5d89
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process ID: 0x974
Faulting application start time: 0x01dacc28cccbb3c4
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.20.11381.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report ID: 894c8028-b6a7-4a1a-904d-2c89e0bb1e77
Faulting package full name: 
Faulting package-relative application ID: 

[ThomasETN]

While running "wt" fails, running by specifying the full path works, i.e. running %LOCALAPPDATA%\Microsoft\WindowsApps\wt.exe worked perfectly. This serves as my current workaround.

I doubled checked that %LOCALAPPDATA%\Microsoft\WindowsApps\wt.exe is already in my PATH

[zadjii-msft]

Curious. What's the whole value of your PATH? Or more specifically, from CMD, what does where wt output/?

[ThomasETN]

C:\Users\<USERNAME>\AppData\Local\Microsoft\WindowsApps\wt.exe

[Anans2]

By the way, I found that running with explorer path box

will get the same crash, too🤔

[AvogatoWizardWhisker]

For some reason, PowerToys run doesn't recognize wt at all on my machine.

[carlos-zamora]

Can you try running this /?
fsutil reparsepoint query %LOCALAPPDATA%\Microsoft\WindowsApps\wt.exe

We'd like to know the contents of that to debug this further.