-
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
WT command in Windows Explorer does not work anymore #7188
Comments
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 |
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):
When I install Windows Terminal Preview, AppXSvc creates the following Registry keys:
Those Registry keys stay there when I enable or disable the
If I disable the 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, thanks for the investigation. I'm gonna feed this straight into the app deployment team's hands 😄 |
Tracking MSFT:28217948 |
I only need to quickly start Windows Terminal, Can you show me how to "enable the |
I cannot reproduce in 1.1.2233.0, but Windows Terminal always opens in |
@PrOF-kk you'll need to use |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
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 The value is set to
|
^^ this was quite a helpful clue, @haydenmc I have both Windows Terminal Preview and Windows Terminal, both installed via the store.
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 I saw that Windows Terminal Preview was "hogging the spotlight" by having it configured under HKEY_CURRENT_USER. So, I renamed it from 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?
Caveat: Edit:
Maybe we should have three execution aliases: |
Received a store update for Windows Terminal today and things seem happy again for my situation. |
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 You might already know this, but to get the behavior you want, you can do one of:
These all mean exactly the same thing.
|
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 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
previously I fixed it by uninstalling from store and installing via choco. after installing the preview, the problem appeared again |
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. |
when I write |
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. |
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 |
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 |
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. |
Toggling "Windows Terminal" under Application Aliases as @zadjii-msft pointed out fixed my issue of not being able to launch wt.exe. |
Maybe you can try and check the steps on #7081 (comment). |
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) |
Anyone who was seeing this before on Windows 10, and has since updated to Windows 11 - are you still seeing this? |
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. |
Typing |
Environment
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.
The text was updated successfully, but these errors were encountered: