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

Windows Terminal 1.8.1521.0 Breaks wt.exe #14134

New Issue
Closed
opened 2026-01-31 04:01:51 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 04:01:51 +00:00
Owner
Copy Link

Originally created by @richardcox13 on GitHub (Jun 5, 2021).

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.

Originally created by @richardcox13 on GitHub (Jun 5, 2021). ### Windows Terminal version (or Windows build number) 1.8.1521.0 ### Other Software _No response_ ### Steps to reproduce Start | Run | wt <enter> 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.
claunia commented 2026-01-31 04:01:53 +00:00
Author
Owner
Copy Link

@richardcox13 commented on GitHub (Jun 5, 2021):

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.

@richardcox13 commented on GitHub (Jun 5, 2021): 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`.
claunia commented 2026-01-31 04:01:54 +00:00
Author
Owner
Copy Link

@smaug9 commented on GitHub (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

@smaug9 commented on GitHub (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
claunia commented 2026-01-31 04:01:54 +00:00
Author
Owner
Copy Link

@bikeoid commented on GitHub (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

@bikeoid commented on GitHub (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
claunia commented 2026-01-31 04:01:54 +00:00
Author
Owner
Copy Link

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

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.

@richardcox13 commented on GitHub (Jun 6, 2021): 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.
claunia commented 2026-01-31 04:01:55 +00:00
Author
Owner
Copy Link

@EdSF commented on GitHub (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!

@EdSF commented on GitHub (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!
claunia commented 2026-01-31 04:01:55 +00:00
Author
Owner
Copy Link

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

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.

@sairaghavak commented on GitHub (Jun 7, 2021): 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.
claunia commented 2026-01-31 04:01:55 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 6, 2021):

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 commented on GitHub (Jul 6, 2021): 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!
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 Issue-Question Needs-Tag-Fix Needs-Triage Resolution-Answered
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#14134
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?