starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

WT command in Windows Explorer does not work anymore #10015

New Issue
Closed
opened 2026-01-31 02:10:08 +00:00 by claunia · 34 comments
claunia commented 2026-01-31 02:10:08 +00:00
Owner
Copy Link

Originally created by @TechWatching on GitHub (Aug 5, 2020).

Environment

Windows build number: Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0
Windows Terminal version (if applicable): 1.1.2021.0

Any other software?

Steps to reproduce

Open Windows Explorer in any directory. Enter wt in the "adress bar", and press "Enter".

Expected behavior

The Windows Terminal opens in the current directory.

Actual behavior

An error message appears "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item".
When looking in the Windows App directory, there is no path corresponding to the error title, instead ther is a folder Microsoft.WindowsTerminalPreview_2020.720.2337.0_neutral_~_8wekyb3d8bbwe.
Maybe there is an error in the directory name.

image

Originally created by @TechWatching on GitHub (Aug 5, 2020). # Environment ```none Windows build number: Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0 Windows Terminal version (if applicable): 1.1.2021.0 Any other software? ``` # Steps to reproduce Open Windows Explorer in any directory. Enter wt in the "adress bar", and press "Enter". # Expected behavior The Windows Terminal opens in the current directory. # Actual behavior An error message appears "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item". When looking in the Windows App directory, there is no path corresponding to the error title, instead ther is a folder `Microsoft.WindowsTerminalPreview_2020.720.2337.0_neutral_~_8wekyb3d8bbwe`. Maybe there is an error in the directory name. ![image](https://user-images.githubusercontent.com/15186176/89383428-bed5b280-d6fc-11ea-82e2-4476d8b9e9bd.png)
claunia commented 2026-01-31 02:10:10 +00:00
Author
Owner
Copy Link

@snalexp commented on GitHub (Aug 5, 2020):

I had the same issue using the Win-R run box.

It only occurred for me when both Windows Terminal and Windows Terminal Preview are installed.

Removing the Preview allows wt to work again.

@snalexp commented on GitHub (Aug 5, 2020): I had the same issue using the Win-R run box. It only occurred for me when _both_ Windows Terminal and Windows Terminal Preview are installed. Removing the Preview allows `wt` to work again.
claunia commented 2026-01-31 02:10:10 +00:00
Author
Owner
Copy Link

@KalleOlaviNiemitalo commented on GitHub (Aug 5, 2020):

I can reproduce with Windows Terminal 1.1.2021.0 and Windows Terminal Preview 1.2.2022.0 on Windows 10 version 2004 (OS Build 19041.388):

  • If I enable the wt.exe app execution alias of Windows Terminal Preview, then wt in File Explorer starts Windows Terminal Preview. ✔
  • If I enable the wt.exe app execution alias of Windows Terminal, then wt in File Explorer shows the access-denied dialog box. ❌
  • If I disable both wt.exe app execution aliases, then wt in File Explorer shows the access-denied dialog box. 🙄 In this case though, I shouldn't expect wt to work anyway.

When I install Windows Terminal Preview, AppXSvc creates the following Registry keys:

  • HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe

Those Registry keys stay there when I enable or disable the wt.exe app execution aliases. They seem related to https://github.com/microsoft/terminal/issues/6748 and https://github.com/microsoft/terminal/pull/6860. If I rename the Registry keys, then the results change:

  • If I enable the wt.exe app execution alias of Windows Terminal Preview, then wt in File Explorer runs Windows Terminal Preview. ✔
  • If I enable the wt.exe app execution alias of Windows Terminal, then wt in File Explorer runs Windows Terminal. ✔
  • If I disable both wt.exe app execution aliases, then wt in File Explorer opens http://wt/ in my Web browser. 🙄

If I disable the skype.exe app execution alias and type skype.exe in the Windows+R run box or in the File Explorer address bar, then I get a similar access-denied dialog box, so this is not specific to Windows Terminal.

If Windows needs a Registry key in App Paths, then perhaps it should keep the per-user key always synchronized with the app execution aliases, and not create the per-machine key.

@KalleOlaviNiemitalo commented on GitHub (Aug 5, 2020): I can reproduce with Windows Terminal 1.1.2021.0 and Windows Terminal Preview 1.2.2022.0 on Windows 10 version 2004 (OS Build 19041.388): * If I enable the `wt.exe` app execution alias of Windows Terminal Preview, then `wt` in File Explorer starts Windows Terminal Preview. ✔ * If I enable the `wt.exe` app execution alias of Windows Terminal, then `wt` in File Explorer shows the access-denied dialog box. ❌ * If I disable both `wt.exe` app execution aliases, then `wt` in File Explorer shows the access-denied dialog box. 🙄 In this case though, I shouldn't expect `wt` to work anyway. When I install Windows Terminal Preview, AppXSvc creates the following Registry keys: * HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe * HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe Those Registry keys stay there when I enable or disable the `wt.exe` app execution aliases. They seem related to <https://github.com/microsoft/terminal/issues/6748> and <https://github.com/microsoft/terminal/pull/6860>. If I rename the Registry keys, then the results change: * If I enable the `wt.exe` app execution alias of Windows Terminal Preview, then `wt` in File Explorer runs Windows Terminal Preview. ✔ * If I enable the `wt.exe` app execution alias of Windows Terminal, then `wt` in File Explorer runs Windows Terminal. ✔ * If I disable both `wt.exe` app execution aliases, then `wt` in File Explorer opens `http://wt/` in my Web browser. 🙄 If I disable the `skype.exe` app execution alias and type `skype.exe` in the Windows+R run box or in the File Explorer address bar, then I get a similar access-denied dialog box, so this is not specific to Windows Terminal. If Windows needs a Registry key in App Paths, then perhaps it should keep the per-user key always synchronized with the app execution aliases, and not create the per-machine key.
claunia commented 2026-01-31 02:10:10 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 6, 2020):

@KalleOlaviNiemitalo, thanks for the investigation. I'm gonna feed this straight into the app deployment team's hands 😄

@DHowett commented on GitHub (Aug 6, 2020): @KalleOlaviNiemitalo, thanks for the investigation. I'm gonna feed this straight into the app deployment team's hands :smile:
claunia commented 2026-01-31 02:10:10 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 6, 2020):

Tracking MSFT:28217948

@DHowett commented on GitHub (Aug 6, 2020): Tracking MSFT:28217948
claunia commented 2026-01-31 02:10:10 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Aug 12, 2020):

Same issue with Win+R when running "wt" ("wt" works when typing into cmd.exe) (i also have WT Preview installed):

image

@vadimkantorov commented on GitHub (Aug 12, 2020): Same issue with Win+R when running "wt" ("wt" works when typing into cmd.exe) (i also have WT Preview installed): ![image](https://user-images.githubusercontent.com/1041752/90002776-6588f880-dc93-11ea-9a9a-5cf95dc1f5af.png)
claunia commented 2026-01-31 02:10:10 +00:00
Author
Owner
Copy Link

@long-nguyenxuan commented on GitHub (Aug 20, 2020):

  • If I enable the wt.exe app execution alias of Windows Terminal Preview, then wt in File Explorer starts Windows Terminal Preview. ✔

I only need to quickly start Windows Terminal, Can you show me how to "enable the wt.exe app execution alias of Windows Terminal Preview"?

@long-nguyenxuan commented on GitHub (Aug 20, 2020): > * If I enable the `wt.exe` app execution alias of Windows Terminal Preview, then `wt` in File Explorer starts Windows Terminal Preview. ✔ I only need to quickly start Windows Terminal, Can you show me how to "enable the `wt.exe` app execution alias of Windows Terminal Preview"?
claunia commented 2026-01-31 02:10:10 +00:00
Author
Owner
Copy Link

@PrOF-kk commented on GitHub (Aug 20, 2020):

I cannot reproduce in 1.1.2233.0, but Windows Terminal always opens in C:\Users\%USERNAME% directory regardless of where explorer is opened
Note: cmd.exe set as default profile

@PrOF-kk commented on GitHub (Aug 20, 2020): I cannot reproduce in 1.1.2233.0, **but** Windows Terminal always opens in `C:\Users\%USERNAME%` directory regardless of where explorer is opened Note: cmd.exe set as default profile
claunia commented 2026-01-31 02:10:11 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 20, 2020):

@long-nguyenxuan
image
image

@PrOF-kk you'll need to use wt -d . to get wt to start in the current working directory.

@zadjii-msft commented on GitHub (Aug 20, 2020): @long-nguyenxuan ![image](https://user-images.githubusercontent.com/18356694/90784532-fcbf0300-e2c6-11ea-95c1-b538b480fe11.png) ![image](https://user-images.githubusercontent.com/18356694/90784644-1b24fe80-e2c7-11ea-8164-ec9442042f0e.png) <hr> @PrOF-kk you'll need to use `wt -d .` to get `wt` to start in the current working directory.
claunia commented 2026-01-31 02:10:11 +00:00
Author
Owner
Copy Link

@ntindle commented on GitHub (Aug 24, 2020):

@zadjii-msft that doesn't appear to be documented here:
image

Should I open an issue for that?

@ntindle commented on GitHub (Aug 24, 2020): @zadjii-msft that doesn't appear to be documented here: ![image](https://user-images.githubusercontent.com/8845353/91060065-1d9d9600-e5f0-11ea-86b3-617819518c85.png) Should I open an issue for that?
claunia commented 2026-01-31 02:10:11 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 24, 2020):

@ntindle Nope, no need. That flag is technically part of the new-tab command:
image

when no command is explicitly passed to wt, it assumes the command to be new-tab.

@zadjii-msft commented on GitHub (Aug 24, 2020): @ntindle Nope, no need. That flag is technically part of the `new-tab` command: ![image](https://user-images.githubusercontent.com/18356694/91060346-73723e00-e5f0-11ea-8000-6b40e0895fdb.png) when no command is explicitly passed to `wt`, it assumes the command to be `new-tab`.
claunia commented 2026-01-31 02:10:11 +00:00
Author
Owner
Copy Link

@haydenmc commented on GitHub (Aug 28, 2020):

I do not have Windows Terminal Preview installed, just Windows Terminal, and I started running into this.

FWIW I do not see a wt.exe key under HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths, but I do see one under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths.

The value is set to C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.2.2381.0_x64__8wekyb3d8bbwe\wt.exe which does exist, but I do not have permissions to execute it.

wt launch error

App execution aliases

PS C:\Users\Hayden> Get-AppPackage -Name "*terminal*"


Name              : Microsoft.WindowsTerminal
Publisher         : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Architecture      : X64
ResourceId        :
Version           : 1.1.2233.0
PackageFullName   : Microsoft.WindowsTerminal_1.1.2233.0_x64__8wekyb3d8bbwe
InstallLocation   : C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.1.2233.0_x64__8wekyb3d8bbwe
IsFramework       : False
PackageFamilyName : Microsoft.WindowsTerminal_8wekyb3d8bbwe
PublisherId       : 8wekyb3d8bbwe
IsResourcePackage : False
IsBundle          : False
IsDevelopmentMode : False
NonRemovable      : False
IsPartiallyStaged : False
SignatureKind     : Store
Status            : Ok
@haydenmc commented on GitHub (Aug 28, 2020): I do not have Windows Terminal Preview installed, just Windows Terminal, and I started running into this. FWIW I do not see a wt.exe key under `HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths`, but I do see one under `HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths`. The value is set to `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.2.2381.0_x64__8wekyb3d8bbwe\wt.exe` which does exist, but I do not have permissions to execute it. ![wt launch error](https://user-images.githubusercontent.com/5422053/91612061-71321b80-e931-11ea-892d-d2b1ea95025f.png) ![App execution aliases](https://user-images.githubusercontent.com/5422053/91612116-958df800-e931-11ea-8459-03dff307104d.png) ``` PS C:\Users\Hayden> Get-AppPackage -Name "*terminal*" Name : Microsoft.WindowsTerminal Publisher : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US Architecture : X64 ResourceId : Version : 1.1.2233.0 PackageFullName : Microsoft.WindowsTerminal_1.1.2233.0_x64__8wekyb3d8bbwe InstallLocation : C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.1.2233.0_x64__8wekyb3d8bbwe IsFramework : False PackageFamilyName : Microsoft.WindowsTerminal_8wekyb3d8bbwe PublisherId : 8wekyb3d8bbwe IsResourcePackage : False IsBundle : False IsDevelopmentMode : False NonRemovable : False IsPartiallyStaged : False SignatureKind : Store Status : Ok ```
claunia commented 2026-01-31 02:10:11 +00:00
Author
Owner
Copy Link

@AltitudeApps commented on GitHub (Aug 29, 2020):

FWIW I do not see a wt.exe key under HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths, but I do see one under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths.

^^ this was quite a helpful clue, @haydenmc

I have both Windows Terminal Preview and Windows Terminal, both installed via the store.

wt -d . from the address bar in Windows Explorer was broken completely, with the same error dialog from Windows Terminal Preview in the original post. I have the preview installed, but I'm not using it at the moment. I was trying to invoke vanilla Windows Terminal.

The settings in the "App Execution Aliases" panel looked right. The one for Windows Terminal was turned on, and the one for Windows Terminal Preview was turned off.

But when I checked under
HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths , and
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths,

I saw that Windows Terminal Preview was "hogging the spotlight" by having it configured under HKEY_CURRENT_USER. So, I renamed it from wt.exe to wtp.exe , just so that it wouldn't interfere with my use of wt -d . from the Windows Explorer address bar to invoke vanilla Windows Terminal. (Windows Terminal Preview is still broken in this regard, but I just wanted to be able to get working again).

The existing entry for Windows Terminal under HKEY_LOCAL_MACHINE was working fine, so I left it where it was. I guess these are supposed to be under HKCU now?

    Hive: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths
Name                           Property
----                           --------
wtp.exe                        (default) : C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.3.2382.0_x64__8wekyb3d8bbwe\wt.exe
^^ was wt.exe                  Path      : C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.3.2382.0_x64__8wekyb3d8bbwe

    Hive: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths
Name                           Property
----                           --------
wt.exe                         (default) : C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.2.2381.0_x64__8wekyb3d8bbwe\wt.exe
                               Path      : C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.2.2381.0_x64__8wekyb3d8bbwe

Caveat: wt new-tab -d . is broken for me; it simply launches a new copy of Windows Terminal instead of creating a new tab in an existing instance. (Perhaps it requires a single instance for the new-tab functionality to work? Or maybe that is only available in the Preview?)

Edit:
looks like @KalleOlaviNiemitalo had the analysis nailed, back at the beginning of the thread:

If Windows needs a Registry key in App Paths, then perhaps it should keep the per-user key always synchronized with the app execution aliases, and not create the per-machine key.

Maybe we should have three execution aliases: wt.exe, wtp.exe, and wtd.exe, to keep the release, preview, and dev versions from stepping on each other?

@AltitudeApps commented on GitHub (Aug 29, 2020): > FWIW I do not see a wt.exe key under `HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths`, but I do see one under `HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths`. ^^ this was quite a helpful clue, @haydenmc I have both Windows Terminal Preview and Windows Terminal, both installed via the store. `wt -d .` from the address bar in Windows Explorer was broken completely, with the same error dialog from Windows Terminal Preview in the original post. I have the preview installed, but I'm not using it at the moment. I was trying to invoke vanilla Windows Terminal. The settings in the "App Execution Aliases" panel looked right. The one for Windows Terminal was turned on, and the one for Windows Terminal Preview was turned off. But when I checked under `HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths` , and `HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths`, I saw that Windows Terminal Preview was "hogging the spotlight" by having it configured under HKEY_CURRENT_USER. So, I renamed it from `wt.exe` to `wtp.exe` , just so that it wouldn't interfere with my use of `wt -d .` from the Windows Explorer address bar to invoke vanilla Windows Terminal. (Windows Terminal Preview is still broken in this regard, but I just wanted to be able to get working again). The existing entry for Windows Terminal under HKEY_LOCAL_MACHINE was working fine, so I left it where it was. I guess these are supposed to be under HKCU now? ``` Hive: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths Name Property ---- -------- wtp.exe (default) : C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.3.2382.0_x64__8wekyb3d8bbwe\wt.exe ^^ was wt.exe Path : C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.3.2382.0_x64__8wekyb3d8bbwe Hive: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths Name Property ---- -------- wt.exe (default) : C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.2.2381.0_x64__8wekyb3d8bbwe\wt.exe Path : C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.2.2381.0_x64__8wekyb3d8bbwe ``` Caveat: `wt new-tab -d .` is broken for me; it simply launches a new copy of Windows Terminal instead of creating a new tab in an existing instance. (Perhaps it requires a single instance for the `new-tab` functionality to work? Or maybe that is only available in the Preview?) Edit: looks like @KalleOlaviNiemitalo had the analysis nailed, back at the beginning of the thread: > If Windows needs a Registry key in App Paths, then perhaps it should keep the per-user key always synchronized with the app execution aliases, and not create the per-machine key. Maybe we should have three execution aliases: `wt.exe`, `wtp.exe`, and `wtd.exe`, to keep the release, preview, and dev versions from stepping on each other?
claunia commented 2026-01-31 02:10:12 +00:00
Author
Owner
Copy Link

@haydenmc commented on GitHub (Aug 30, 2020):

Received a store update for Windows Terminal today and things seem happy again for my situation.

@haydenmc commented on GitHub (Aug 30, 2020): Received a store update for Windows Terminal today and things seem happy again for my situation.
claunia commented 2026-01-31 02:10:12 +00:00
Author
Owner
Copy Link

@stmax82 commented on GitHub (Sep 9, 2020):

When I enter wt in the address bar of Windows Explorer it opens wt, but in the wrong directory (C:\Users<username>). Expected behavior: The Windows Terminal opens in the current directory, like powershell and cmd do.

@stmax82 commented on GitHub (Sep 9, 2020): When I enter wt in the address bar of Windows Explorer it opens wt, but in the wrong directory (C:\Users\<username>). Expected behavior: The Windows Terminal opens in the current directory, like powershell and cmd do.
claunia commented 2026-01-31 02:10:12 +00:00
Author
Owner
Copy Link

@AltitudeApps commented on GitHub (Sep 9, 2020):

@stmax82 You might already know this, but to get the behavior you want, you can do one of:

  • wt -d .
  • wt --startingDirectory .
  • wt new-tab -d .
  • wt new-tab --startingDirectory .

These all mean exactly the same thing.

-d is an alias for -startingDirectory, and new-tab is the default argument to wt.exe, when the user does not provide an argument.

@AltitudeApps commented on GitHub (Sep 9, 2020): @stmax82 You might already know this, but to get the behavior you want, you can do one of: - `wt -d .` - `wt --startingDirectory .` - `wt new-tab -d .` - `wt new-tab --startingDirectory .` These all mean exactly the same thing. `-d` is an alias for `-startingDirectory`, and `new-tab` is the default argument to `wt.exe`, when the user does not provide an argument.
claunia commented 2026-01-31 02:10:12 +00:00
Author
Owner
Copy Link

@f2l2pe commented on GitHub (Oct 21, 2020):

Im having this problem but its a different error and nothing in this issue solved it. I don't have preview installed

image

Any ideas?

When i run from the start menu it works fine, its just when i try to run using wt.exe
It also ran fine before, it started doing that a few days ago

@f2l2pe commented on GitHub (Oct 21, 2020): Im having this problem but its a different error and nothing in this issue solved it. I don't have preview installed ![image](https://user-images.githubusercontent.com/6012227/96669824-65147a00-1334-11eb-8470-9eeb7efa9ab1.png) Any ideas? When i run from the start menu it works fine, its just when i try to run using `wt.exe` It also ran fine before, it started doing that a few days ago
claunia commented 2026-01-31 02:10:12 +00:00
Author
Owner
Copy Link

@KyleCrowley commented on GitHub (Nov 11, 2020):

EDIT: I was able to get Windows Terminal working again via a procedure I found here.

As I mentioned here, I'm also running into the same issue, and it seems many others are as well.

I installed Windows Terminal via chocolatey (I can't install via the Windows Store due to organization restrictions) a few months ago and it had been working fine until recently, as it fails to launch with the same error message that @chiniara received.

I've tried reinstalling and resetting permissions on C:\Program Files\WindowsApps, but nothing seems to be working.

@KyleCrowley commented on GitHub (Nov 11, 2020): **EDIT:** I was able to get Windows Terminal working again via a procedure I found [here](https://github.com/microsoft/terminal/issues/7081#issuecomment-726864131). --- As I mentioned [here](https://github.com/microsoft/terminal/issues/7081#issuecomment-724972410), I'm also running into the same issue, and it seems many others are as well. I installed Windows Terminal via chocolatey (I can't install via the Windows Store due to organization restrictions) a few months ago and it had been working fine until recently, as it fails to launch with the [same error message](https://github.com/microsoft/terminal/issues/7188#issuecomment-713273826) that @chiniara received. I've tried reinstalling and resetting permissions on `C:\Program Files\WindowsApps`, but nothing seems to be working.
claunia commented 2026-01-31 02:10:12 +00:00
Author
Owner
Copy Link

@xal1983 commented on GitHub (Jan 20, 2021):

I agree, being able to run "wt" and open in the current directory would be ideal. This works if you run cmd or powershell.

@xal1983 commented on GitHub (Jan 20, 2021): I agree, being able to run "wt" and open in the current directory would be ideal. This works if you run cmd or powershell.
claunia commented 2026-01-31 02:10:12 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 20, 2021):

@xal1983 You're looking for wt -d ., and #878. This issue is tracking a totally other issue where the OS seemingly invokes the wrong thing, and causes some other unexpected failures. Generally, wt -d . in the explorer address bar should work.

@zadjii-msft commented on GitHub (Jan 20, 2021): @xal1983 You're looking for `wt -d .`, and #878. This issue is tracking a totally other issue where the OS seemingly invokes the wrong thing, and causes some other unexpected failures. _Generally_, `wt -d .` in the explorer address bar _should_ work.
claunia commented 2026-01-31 02:10:13 +00:00
Author
Owner
Copy Link

@blackrek commented on GitHub (Mar 8, 2021):

previously I fixed it by uninstalling from store and installing via choco. after installing the preview, the problem appeared again

@blackrek commented on GitHub (Mar 8, 2021): previously I fixed it by uninstalling from store and installing via choco. after installing the preview, the problem appeared again
claunia commented 2026-01-31 02:10:13 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 11, 2021):

I believe that this is, in part, due to #9452. If any of you are still running into this issue, would you mind following the reporting steps over there?

@KalleOlaviNiemitalo - I reported your app paths findings to the app deployment team as mentioned above and have not heard back in some time. Discussions still unfolding I guess.

@DHowett commented on GitHub (Mar 11, 2021): I believe that this is, _in part_, due to #9452. If any of you are still running into this issue, would you mind following the reporting steps over there? @KalleOlaviNiemitalo - I reported your app paths findings to the app deployment team as mentioned above and have not heard back in some time. Discussions still unfolding I guess.
claunia commented 2026-01-31 02:10:13 +00:00
Author
Owner
Copy Link

@junksheng commented on GitHub (May 29, 2021):

when I write wt in win+r or directory, it warning me "the system can't find the wt.exe", but the wt.exe exist. and i can turn on in menu.

@junksheng commented on GitHub (May 29, 2021): when I write `wt` in win+r or directory, it warning me "the system can't find the wt.exe", but the wt.exe exist. and i can turn on in menu.
claunia commented 2026-01-31 02:10:13 +00:00
Author
Owner
Copy Link

@viceice commented on GitHub (May 30, 2021):

I need to disable and enable alias after latest terminal update, because it couldn't find when running wt from explorer path input 😕

@viceice commented on GitHub (May 30, 2021): I need to disable and enable alias after latest terminal update, because it couldn't find when running wt from explorer path input 😕
claunia commented 2026-01-31 02:10:14 +00:00
Author
Owner
Copy Link

@JorgenSmith commented on GitHub (May 31, 2021):

I need to disable and enable alias after latest terminal update, because it couldn't find when running wt from explorer path input 😕

Can confirm; that did the trick for me. (Thanks for posting about App Execution Aliases, Kalle).

I have a bat file running it linked up as Streamdeck shortcut (they're a brilliant macro launcher for dev!) and couldn't figure out why it stopped working; a reboot actually resolved it temporarily last week, then it stopped working again today.

@JorgenSmith commented on GitHub (May 31, 2021): > I need to disable and enable alias after latest terminal update, because it couldn't find when running wt from explorer path input 😕 Can confirm; that did the trick for me. (Thanks for posting about App Execution Aliases, Kalle). I have a bat file running it linked up as Streamdeck shortcut (they're a brilliant macro launcher for dev!) and couldn't figure out why it stopped working; a reboot actually resolved it temporarily last week, then it stopped working again today.
claunia commented 2026-01-31 02:10:14 +00:00
Author
Owner
Copy Link

@jogerj commented on GitHub (Jun 6, 2021):

I need to disable and enable alias after latest terminal update, because it couldn't find when running wt from explorer path input 😕

Also experienced this from a recent update and this solution worked for me.

As explained above by Kalle, the path is defined in the registry keys for "App Paths". There was a discrepancy where the path pointed to a previously installed version of wt C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe> when actually the app was updated so the correct path would be C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe>. Re-enabling wt.exe under 'App execution aliases' settings fixed it.

@jogerj commented on GitHub (Jun 6, 2021): > I need to disable and enable alias after latest terminal update, because it couldn't find when running wt from explorer path input 😕 Also experienced this from a recent update and this solution worked for me. [As explained above by Kalle](https://github.com/microsoft/terminal/issues/7188#issuecomment-669046854), the path is defined in the registry keys for "App Paths". There was a discrepancy where the path pointed to a previously installed version of wt `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe>` when actually the app was updated so the correct path would be `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe>`. Re-enabling wt.exe under 'App execution aliases' settings fixed it.
claunia commented 2026-01-31 02:10:14 +00:00
Author
Owner
Copy Link

@viceice commented on GitHub (Jun 7, 2021):

For me the store updated it in background while an older version was running. Then I found this issue and tried the re-enable which works.

@viceice commented on GitHub (Jun 7, 2021): For me the store updated it in background while an older version was running. Then I found this issue and tried the re-enable which works.
claunia commented 2026-01-31 02:10:14 +00:00
Author
Owner
Copy Link

@jogerj commented on GitHub (Jun 7, 2021):

For me the store updated it in background while an older version was running. Then I found this issue and tried the re-enable which works.

This might've been the cause for me. I've been running some scripts on wt non-stop for a couple of days until i closed wt and suddenly can't open it from run again

@jogerj commented on GitHub (Jun 7, 2021): > For me the store updated it in background while an older version was running. Then I found this issue and tried the re-enable which works. This might've been the cause for me. I've been running some scripts on wt non-stop for a couple of days until i closed wt and suddenly can't open it from run again
claunia commented 2026-01-31 02:10:14 +00:00
Author
Owner
Copy Link

@jaigak commented on GitHub (Jun 22, 2021):

wt works for me but it doesn't seem to launch in the current working directory but the Open in Windows Terminal option opens in the current working directory.

@jaigak commented on GitHub (Jun 22, 2021): wt works for me but it doesn't seem to launch in the current working directory but the Open in Windows Terminal option opens in the current working directory.
claunia commented 2026-01-31 02:10:15 +00:00
Author
Owner
Copy Link

@jnyanez commented on GitHub (Aug 9, 2021):

Toggling "Windows Terminal" under Application Aliases as @zadjii-msft pointed out fixed my issue of not being able to launch wt.exe.

@jnyanez commented on GitHub (Aug 9, 2021): Toggling "Windows Terminal" under Application Aliases as @zadjii-msft pointed out fixed my issue of not being able to launch wt.exe.
claunia commented 2026-01-31 02:10:15 +00:00
Author
Owner
Copy Link

@liudonghua123 commented on GitHub (Mar 12, 2022):

Maybe you can try and check the steps on https://github.com/microsoft/terminal/issues/7081#issuecomment-1065833836.

@liudonghua123 commented on GitHub (Mar 12, 2022): Maybe you can try and check the steps on https://github.com/microsoft/terminal/issues/7081#issuecomment-1065833836.
claunia commented 2026-01-31 02:10:15 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 28, 2022):

notes from internal bug: This should have been fixed in OS build 21307, which I think should have been released in Windows 11 RTM (alas, build numbers got confusing right around then)

@zadjii-msft commented on GitHub (Jul 28, 2022): notes from internal bug: This should have been fixed in OS build 21307, which I think should have been released in Windows 11 RTM (alas, build numbers got confusing right around then)
claunia commented 2026-01-31 02:10:15 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 28, 2022):

Anyone who was seeing this before on Windows 10, and has since updated to Windows 11 - are you still seeing this?

@zadjii-msft commented on GitHub (Jul 28, 2022): Anyone who was seeing this before on Windows 10, and has since updated to Windows 11 - are you still seeing this?
claunia commented 2026-01-31 02:10:15 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 1, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Aug 1, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 02:10:15 +00:00
Author
Owner
Copy Link

@Welding-Torch commented on GitHub (Oct 28, 2023):

Typing wt does not work for me in Run (Start+R) or Windows Explorer, but it does work when I type wt in cmd. Disabling and enabling the alias in alias settings had no effect.

@Welding-Torch commented on GitHub (Oct 28, 2023): Typing `wt` does not work for me in Run (Start+R) or Windows Explorer, but it does work when I type `wt` in cmd. Disabling and enabling the alias in alias settings had no effect.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Culprit-Centennial Needs-Author-Feedback Product-Terminal Tracking-External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#10015
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?