terminal: Running wt from "Run" dialog box doesn't work

Windows Terminal version (or Windows build number)

10.0.19042.0 1.7.1091.0

Other Software

Windows run dialog

Steps to reproduce

  • Press Windows+R to open the run dialog
  • Type “wt” or “wt.exe”
  • Press enter or ctrl+shift+enter, it doesn’t launch with either

Expected Behavior

The application would launch normally when launched from a run dialog.

Actual Behavior

Open dialog closes, cursor goes to “loading” state, then everything turns back silent. Running Get-Command wt | Select-Object -ExpandProperty Definition, it echoes back %USERPROFILE%\AppData\Local\Microsoft\WindowsApps\wt.exe, and pasting this string into the run dialog actually opens the terminal. That path is already in the system AND user paths.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 20 (8 by maintainers)

Most upvoted comments

@zadjii-msft I’ve been having the same issue and have too much important data to merit doing a clean install, so I’m working with a faulty wt.exe alias if you need some more diagnostics. Just so we’re caught up, I tried toggling the App Execution Alias and performing an app repair via Settings, but neither worked for me. Symptoms for me are identical as the original video posted in this issue. I can’t remember, but I might’ve messed with the permissions a while back, so I wouldn’t be surprised if that was the cause. Looking back through the thread a bit, I saw you posted the correct permission for the WindowsApps folder; could you please elaborate on (or send a link that explains) the :(OI)(CI)(IO)(F)(c,S,E)... bit? I take it (F) means Full Control, then (R|W|X) mean Read|Write|Execute respectively, but I’m not familiar with the others.

Edit: I ran icacls "C:\Program Files\WindowsApps", here’s my output:

C:\Program Files\WindowsApps NT SERVICE\TrustedInstaller:(OI)(CI)(F)
                             S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204:(OI)(CI)(RX)
                             NT AUTHORITY\SYSTEM:(OI)(CI)(F)
                             BUILTIN\Administrators:(CI)(RX,W)
                             NT AUTHORITY\LOCAL SERVICE:(OI)(CI)(RX)
                             NT AUTHORITY\NETWORK SERVICE:(OI)(CI)(RX)
                             NT AUTHORITY\RESTRICTED:(OI)(CI)(RX)
                             LAPTOP\Nick:(OI)(CI)(F)
                             BUILTIN\Users:(Rc,S,RD,REA,X,RA)

Successfully processed 1 files; Failed processing 0 files

@sungvzer Could you try toggling the “App Execution Alias” for the Terminal, in the Settings App? That might just fix it for you. Otherwise, there’s an option in the Settings app to “Repair” an app (Settings > Apps and Features > Terminal > Advanced Options > Repair) which might work.