Skip to content
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

Windows Terminal 1.8.1521.0 Breaks wt.exe #10346

Closed
richardcox13 opened this issue Jun 5, 2021 · 7 comments
Closed

Windows Terminal 1.8.1521.0 Breaks wt.exe #10346

richardcox13 opened this issue Jun 5, 2021 · 7 comments
Labels
Culprit-Centennial Issue-Question For questions or discussion Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Answered Related to questions that have been answered

Comments

@richardcox13
Copy link

Windows Terminal version (or Windows build number)

1.8.1521.0

Other Software

No response

Steps to reproduce

Start | Run | wt

and get popup with

[Window Title] C:\Users\richard\AppData\Local\Microsoft\WindowsApps\wt.exe

[Content]
Windows cannot find 'C:\Users\richard\AppData\Local\Microsoft\WindowsApps\wt.exe'. Make sure >you've typed the name correctly, then try again.

Running from an open Windows Terminal tag with PowserShell 7.1.3 reports

ResourceUnavailable: Program 'wt.exe' failed to run: The system cannot find the file specified.At line:1 char:1
+ wt
+ ~~.

This is immediately after the Windows Store pushed a new build (previously was running 1.8 as released 2021-05-21.

(Opening from the shortcut pinned to my task bar works correctly.)

Expected Behavior

A new Windows Terminal window is opened with my default profile loaded.

Actual Behavior

See steps to reproduce.

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 5, 2021
@richardcox13
Copy link
Author

The problem appears to be the link %USERPROFILE%\AppData\Local\Microsoft\WindowsApps\wt.exe has not been updated, it exists but links to C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\wt.exe rather than C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe\wt.exe.

@smaug9
Copy link

smaug9 commented Jun 5, 2021

I'm getting a similar error.

  1. It looks like the wt.exe link in my user directory points to the wrong wt.exe in the c:\program files\windowsapps.
  2. Additionally, it seems that my user doesnt have permissions to read/execute wt.exe in the c:\program files\windowsapps.
> dir C:\users\jeff\appdata\local\microsoft\WindowsApps\wt.exe

    Directory: C:\users\jeff\appdata\local\microsoft\WindowsApps

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
la---          2021-04-17    11:46              0 wt.exe -> C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.7.1033.0_x64__8wekyb3d8bbwe\wt.exe
C:\>"c:\program files\windowsapps\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe\wt.exe"
Access is denied.

Currently I can only start wt.exe from the icon in the start menu.

Furthermore.... looks like wt.exe in hklm registry apppaths is pointing to the correct wt.exe, but hkcu is pointing to the old path.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe]
@="C:\\Program Files\\WindowsApps\\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe\\wt.exe"
"Path"="C:\\Program Files\\WindowsApps\\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe"

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe]
@="C:\\Program Files\\WindowsApps\\Microsoft.WindowsTerminal_1.7.1033.0_x64__8wekyb3d8bbwe\\wt.exe"
"Path"="C:\\Program Files\\WindowsApps\\Microsoft.WindowsTerminal_1.7.1033.0_x64__8wekyb3d8bbwe"

I've deleted the hkcu key, and now im getting a different error when running win+r>wt:

Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.

Lastly... I seem to have resolved it (poorly) by browsing to c:\program files\windowsapps, which popped a dialog box asking me to permanently grant access to open the item, which I did, and now win+r>wt works

@bikeoid
Copy link

bikeoid commented Jun 5, 2021

I was able to resolve this by turning the App Execution Alias for WT off then on following the screen at https://stackoverflow.com/a/66539884/1743

@richardcox13
Copy link
Author

In the end I tried a repair: and that worked (after a logoff/on and then a reboot had not).

It is annoying when Windows Terminal is restarted on me (all the state, history, and output lost) especially when I cannot quickly restore things.

@EdSF
Copy link

EdSF commented Jun 7, 2021

I was able to resolve this by turning the App Execution Alias for WT off then on following the screen at https://stackoverflow.com/a/66539884/1743

@bikeoid Confirmed. Thank you!

@sairaghavak
Copy link

I know op is talking about version

Windows Terminal version 1.8.x

But, just in case if anyone has trouble with Preview version

1.9.1523.0

Initially after windows update
Couldn't open windows terminal from

start -> run -> wt

In my case, after checking the Manage app execution aliases, Windows Terminal app is already turned on
After turning it off and on, and a round of restart worked for me.

@zadjii-msft
Copy link
Member

FYI, this is something that can break basically any time the Terminal is updated. We're working with the platform team to try and get that fixed. see also: https://github.com/microsoft/terminal/issues?q=is%3Aissue+label%3ACulprit-Centennial, #9452

Thanks all!

@zadjii-msft zadjii-msft added Culprit-Centennial Issue-Question For questions or discussion Resolution-Answered Related to questions that have been answered labels Jul 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Culprit-Centennial Issue-Question For questions or discussion Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Answered Related to questions that have been answered
Projects
None yet
Development

No branches or pull requests

6 participants