Windows Terminal doesn't start from folder right-click menu #18863

Open
opened 2026-01-31 06:26:37 +00:00 by claunia · 10 comments
Owner

Originally created by @gyorokpeter on GitHub (Nov 10, 2022).

Windows Terminal version

1.15.2875.0

Windows build number

10.0.22621.819

Other Software

N/A

Steps to reproduce

After installing Windows Terminal, right click in any folder in Windows Explorer and choose "Open in Terminal".

Expected Behavior

Terminal should start up.

Actual Behavior

Nothing happens.
However Terminal works if started by other means, such as by running it from the start menu, so the problem must be in the context menu launch method.

Originally created by @gyorokpeter on GitHub (Nov 10, 2022). ### Windows Terminal version 1.15.2875.0 ### Windows build number 10.0.22621.819 ### Other Software N/A ### Steps to reproduce After installing Windows Terminal, right click in any folder in Windows Explorer and choose "Open in Terminal". ### Expected Behavior Terminal should start up. ### Actual Behavior Nothing happens. However Terminal works if started by other means, such as by running it from the start menu, so the problem must be in the context menu launch method.
claunia added the Issue-BugProduct-TerminalArea-ShellExtension labels 2026-01-31 06:26:37 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Nov 11, 2022):

We might need a feedback hub trace on this, so we can get the context menu folks to take a look. I don't recall off the top of my head what the area path for the shell context menu is. The bot will tell you to file this under the "Terminal" path, but you should look for a context menu path instead. (alas, feedback hub is busted on my machine ATM, so I can't figure that out for you).

/feedback

@zadjii-msft commented on GitHub (Nov 11, 2022): We might need a feedback hub trace on this, so we can get the context menu folks to take a look. I don't recall off the top of my head what the area path for the shell context menu is. The bot will tell you to file this under the "Terminal" path, but you should look for a context menu path instead. (alas, feedback hub is busted on my machine ATM, so I can't figure that out for you). /feedback
Author
Owner

@ghost commented on GitHub (Nov 11, 2022):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?

Thanks!

image

image

image

@ghost commented on GitHub (Nov 11, 2022): Hi there!<br><br>Can you please send us feedback with the [Feedback Hub](https://support.microsoft.com/en-us/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332) with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18356694/140811502-a068f78b-89d2-4587-925a-73e19652b830.png)<br><br>![image](https://user-images.githubusercontent.com/18356694/140811557-cdc22a0f-fa6a-4f6a-953e-73b51f5548a3.png)<br><br>![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
Author
Owner

@gyorokpeter commented on GitHub (Nov 12, 2022):

https://aka.ms/AAippyc

@gyorokpeter commented on GitHub (Nov 12, 2022): https://aka.ms/AAippyc
Author
Owner

@carlos-zamora commented on GitHub (Dec 7, 2022):

Hmm. Could you try doing this?

  1. Open Windows Terminal
  2. Open the drop down menu
  3. shift+click a profile

Does a terminal launch in a new window? This may help us diagnose what specifically is failing.

@carlos-zamora commented on GitHub (Dec 7, 2022): Hmm. Could you try doing this? 1. Open Windows Terminal 2. Open the drop down menu 3. shift+click a profile Does a terminal launch in a new window? This may help us diagnose what specifically is failing.
Author
Owner

@gyorokpeter commented on GitHub (Dec 7, 2022):

That opens a folder in Windows Explorer with the name %LOCALAPPDATA%\Microsoft\WindowsApps\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\wt.exe . It's a folder but it's named like an executable file.

@gyorokpeter commented on GitHub (Dec 7, 2022): That opens a folder in Windows Explorer with the name `%LOCALAPPDATA%\Microsoft\WindowsApps\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\wt.exe` . It's a folder but it's named like an executable file.
Author
Owner

@carlos-zamora commented on GitHub (Dec 7, 2022):

Awesome. Could you run this command:
fsutil reparsepoint query %LOCALAPPDATA%\Microsoft\WindowsApps\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\wt.exe

It looks like your app execution alias might be broken (as you've probably guessed).

@carlos-zamora commented on GitHub (Dec 7, 2022): Awesome. Could you run this command: `fsutil reparsepoint query %LOCALAPPDATA%\Microsoft\WindowsApps\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\wt.exe` It looks like your app execution alias might be broken (as you've probably guessed).
Author
Owner

@gyorokpeter commented on GitHub (Dec 8, 2022):

It says "Error: The file or directory is not a reparse point" (in Hungarian).

@gyorokpeter commented on GitHub (Dec 8, 2022): It says "Error: The file or directory is not a reparse point" (in Hungarian).
Author
Owner

@zadjii-msft commented on GitHub (Dec 8, 2022):

Well that's entirely unexpected! I honestly have no idea how that would happen. You might want to back up your settings.json file file (and possibly state.json in that folder too), delete the bad "wt.exe" folder, and reinstall the Terminal. I have no idea how that would get created as a folder instead of as the app execution alias / reparse point...

@zadjii-msft commented on GitHub (Dec 8, 2022): Well that's entirely unexpected! I honestly have no idea how that would happen. You might want to back up your [settings.json file](https://github.com/microsoft/terminal/wiki/Frequently-Asked-Questions-(FAQ)#where-can-i-find-the-settings-file) file (and possibly `state.json` in that folder too), delete the bad "`wt.exe`" folder, and reinstall the Terminal. I have no idea how that would get created as a folder instead of as the app execution alias / reparse point...
Author
Owner

@gyorokpeter commented on GitHub (Dec 8, 2022):

I managed to recreate the symlinks. Now the shift-click method works in a terminal window, but the right-click menu in a folder still doesn't.

@gyorokpeter commented on GitHub (Dec 8, 2022): I managed to recreate the symlinks. Now the shift-click method works in a terminal window, but the right-click menu in a folder still doesn't.
Author
Owner

@carlos-zamora commented on GitHub (Jan 25, 2023):

Sorry for the delay, finally coming back to this. It looks like #14637 has presented a potential solution. We would just need some time to implement a similar thing for the shell extension.

@carlos-zamora commented on GitHub (Jan 25, 2023): Sorry for the delay, finally coming back to this. It looks like #14637 has presented a potential solution. We would just need some time to implement a similar thing for the shell extension.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18863