-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot start wt through "Run" #17486
Comments
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:
|
Works perfectly fine for me on windows 11 home 23H2. |
I got the same issue on Windows 10 22H2 (
|
While running "wt" fails, running by specifying the full path works, i.e. running I doubled checked that |
Curious. What's the whole value of your |
This comment was marked as off-topic.
This comment was marked as off-topic.
Can you try running this /? We'd like to know the contents of that to debug this further. |
Running this command returns I think it's because I have 4 Although, I don't have an issue running |
Thanks. We were more hoping for ThomasETN and Anans2 to help out with that. You seem to be having a different issue. For you: can you turn off your app execution alias in the "Manage App Execution Aliases" settings page, and then turn it back on? |
(CyberChef) |
This comment was marked as resolved.
This comment was marked as resolved.
I think you should run |
Ok, then I get the same output. |
Hmm... Ok, could you use feedback hub to get a trace for us /? Thanks Can you also go into your Windows settings and switch the app execution alias? You mentioned 1.20 in the bug report, but the log you posted says 1.21, so we're a bit suspicious of that. /feedback |
other notes:
|
I doubt if it has anything to do with the preview versions, because unlike Anans2 I'm on 1.20.11381.0 all along, I don't even have the preview version installed... yet we seem to be facing the same issue 🤔 |
Oh, I got it wrong. I have tried switching to the preview version to repair it but got the same result. Now I am certainly using the stable one.
I found that starting through the path "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.20.11781.0_x64__8wekyb3d8bbwe\wt.exe" will make it crash. However, using the softlink "%LOCALAPPDATA%\Microsoft\WindowsApps\wt.exe" works will, even though the softlink points to former one🤔 |
Huh well yep that would do it! Can you run the following in an admin command prompt window:
we think the permissions on |
As requested in #17593 above cacls "C:\Program Files\WindowsApps" /S
C:\Program Files\WindowsApps "D:PAI(A;OICI;0x1200a9;;;RC)(A;;FA;;;SY)(A;OICIIO;GA;;;SY)(A;OICI;0x1200a9;;;LS)(A;OICI;0x1200a9;;;NS)(A;CI;0x1200a9;;;BA)(A;OICI;FA;;;BA)(A;OICIIO;0x1200a9;;;BU)(XA;;0x1200a9;;;BU;(Exists WIN://SYSAPPID))(A;OICIIO;GA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;OICI;0x1200a9;;;AC)(A;;0x1200a9;;;S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204)(A;OICIIO;GXGR;;;S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204)"
|
|
|
As requested in #17593 & above
Prettified:
|
Facing the same issue as #17593 from last two days. cacls command output:
Formatted:
When execute Event Viewer entry:
Tried repair-reset-reinstall many times but not working. |
Thank you. I can run |
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.
However, with any other ways to start, like start menu, right-click menu or run "wt" in another terminal, it works well.
The text was updated successfully, but these errors were encountered: