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

When searching for "wt.exe" in Windows Search Box, it crashes and returns an error. #12306

New Issue
Closed
opened 2026-01-31 03:11:53 +00:00 by claunia · 16 comments
claunia commented 2026-01-31 03:11:53 +00:00
Owner
Copy Link

Originally created by @TrevCan on GitHub (Jan 29, 2021).

Originally assigned to: @DHowett on GitHub.

Environment

Microsoft Windows [Version 10.0.18363.1316]
Windows Terminal version (if applicable): 1.5.10271.0 (this is the one that appears on the Microsoft Store)

Any other software?
no

Steps to reproduce

Open the windows search box (or just use [Windows Key] + S
type "wt.exe"
press enter

Expected behavior

Should open the Windows Terminal

Actual behavior

As shown on the screenshot below, it returns an error and does not open the app. The last version that was installed used to work just fine doing the instructions presented above.

image

Other Information

Alternatively, if you try search for "wt.exe" on the Windows Powertoys search box it works. Apparently both searches point to different *.exes. The Powertoys search box points to C:\Users\{USER_NAME}\AppData\Local\Microsoft\WindowsApps and the default windows search box points to C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.5.10271.0_x64__8wekyb3d8bbwe.
Also, if I just search in the Windows Default Search Box for "Windows Terminal" and press enter it works.

Originally created by @TrevCan on GitHub (Jan 29, 2021). Originally assigned to: @DHowett on GitHub. # Environment ```none Microsoft Windows [Version 10.0.18363.1316] Windows Terminal version (if applicable): 1.5.10271.0 (this is the one that appears on the Microsoft Store) Any other software? no ``` # Steps to reproduce Open the windows search box (or just use [Windows Key] + S type "wt.exe" press enter <!-- A description of how to trigger this bug. --> # Expected behavior Should open the Windows Terminal <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior As shown on the screenshot below, it returns an error and does not open the app. The last version that was installed used to work just fine doing the instructions presented above. <!-- What's actually happening? --> ![image](https://user-images.githubusercontent.com/44383325/106337640-50ab1c00-6257-11eb-9329-7380967fbb69.png) # Other Information Alternatively, if you try search for "wt.exe" on the Windows Powertoys search box it works. Apparently both searches point to different *.exes. The Powertoys search box points to `C:\Users\{USER_NAME}\AppData\Local\Microsoft\WindowsApps` and the default windows search box points to `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.5.10271.0_x64__8wekyb3d8bbwe`. **Also, if I just search in the Windows Default Search Box for "Windows Terminal" and press enter it works.**
claunia added the Resolution-DuplicateCulprit-Centennial labels 2026-01-31 03:11:54 +00:00
claunia commented 2026-01-31 03:11:55 +00:00
Author
Owner
Copy Link

@srdjanjovcic commented on GitHub (Feb 1, 2021):

I do not get error, but wt.exe stopped working -- it just flashes a bit and disappears. It breaks my shortcuts which use wt.exe to open given profile.

@srdjanjovcic commented on GitHub (Feb 1, 2021): I do not get error, but wt.exe stopped working -- it just flashes a bit and disappears. It breaks my shortcuts which use wt.exe to open given profile.
claunia commented 2026-01-31 03:11:55 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 1, 2021):

@DHowett this one looks like it's also related to our recent deployment woes

@zadjii-msft commented on GitHub (Feb 1, 2021): @DHowett this one looks like it's also related to our recent deployment woes
claunia commented 2026-01-31 03:11:55 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 3, 2021):

This looks a lot like #9017. I'm worried that your install is somehow fragmented, and the alias is pointing at the wrong exe.

Could you share the output of the following two commands?

  • fsutil reparsepoint query C:\Users\{USER_NAME}\AppData\Local\Microsoft\WindowsApps\wt.exe
  • fsutil reparsepoint query C:\Users\{USER_NAME}\AppData\Local\Microsoft\WindowsApps\Microsoft.WindowsTerminal_8wekyb3d8bbwe\wt.exe
@zadjii-msft commented on GitHub (Feb 3, 2021): This looks a lot like #9017. I'm worried that your install is somehow fragmented, and the alias is pointing at the wrong exe. Could you share the output of the following two commands? * `fsutil reparsepoint query C:\Users\{USER_NAME}\AppData\Local\Microsoft\WindowsApps\wt.exe` * `fsutil reparsepoint query C:\Users\{USER_NAME}\AppData\Local\Microsoft\WindowsApps\Microsoft.WindowsTerminal_8wekyb3d8bbwe\wt.exe`
claunia commented 2026-01-31 03:11:55 +00:00
Author
Owner
Copy Link

@TrevCan commented on GitHub (Feb 3, 2021):

sure,

  • fsutil reparsepoint query C:\Users\{USER_NAME}\AppData\Local\Microsoft\WindowsApps\wt.exe

    Reparse Tag Value : 0x8000001b
Tag value: Microsoft

Reparse Data Length: 0x0000016a
Reparse Data:
0000:  03 00 00 00 4d 00 69 00  63 00 72 00 6f 00 73 00  ....M.i.c.r.o.s.
0010:  6f 00 66 00 74 00 2e 00  57 00 69 00 6e 00 64 00  o.f.t...W.i.n.d.
0020:  6f 00 77 00 73 00 54 00  65 00 72 00 6d 00 69 00  o.w.s.T.e.r.m.i.
0030:  6e 00 61 00 6c 00 5f 00  38 00 77 00 65 00 6b 00  n.a.l._.8.w.e.k.
0040:  79 00 62 00 33 00 64 00  38 00 62 00 62 00 77 00  y.b.3.d.8.b.b.w.
0050:  65 00 00 00 4d 00 69 00  63 00 72 00 6f 00 73 00  e...M.i.c.r.o.s.
0060:  6f 00 66 00 74 00 2e 00  57 00 69 00 6e 00 64 00  o.f.t...W.i.n.d.
0070:  6f 00 77 00 73 00 54 00  65 00 72 00 6d 00 69 00  o.w.s.T.e.r.m.i.
0080:  6e 00 61 00 6c 00 5f 00  38 00 77 00 65 00 6b 00  n.a.l._.8.w.e.k.
0090:  79 00 62 00 33 00 64 00  38 00 62 00 62 00 77 00  y.b.3.d.8.b.b.w.
00a0:  65 00 21 00 41 00 70 00  70 00 00 00 43 00 3a 00  e.!.A.p.p...C.:.
00b0:  5c 00 50 00 72 00 6f 00  67 00 72 00 61 00 6d 00  \.P.r.o.g.r.a.m.
00c0:  20 00 46 00 69 00 6c 00  65 00 73 00 5c 00 57 00   .F.i.l.e.s.\.W.
00d0:  69 00 6e 00 64 00 6f 00  77 00 73 00 41 00 70 00  i.n.d.o.w.s.A.p.
00e0:  70 00 73 00 5c 00 4d 00  69 00 63 00 72 00 6f 00  p.s.\.M.i.c.r.o.
00f0:  73 00 6f 00 66 00 74 00  2e 00 57 00 69 00 6e 00  s.o.f.t...W.i.n.
0100:  64 00 6f 00 77 00 73 00  54 00 65 00 72 00 6d 00  d.o.w.s.T.e.r.m.
0110:  69 00 6e 00 61 00 6c 00  5f 00 31 00 2e 00 35 00  i.n.a.l._.1...5.
0120:  2e 00 31 00 30 00 32 00  37 00 31 00 2e 00 30 00  ..1.0.2.7.1...0.
0130:  5f 00 78 00 36 00 34 00  5f 00 5f 00 38 00 77 00  _.x.6.4._._.8.w.
0140:  65 00 6b 00 79 00 62 00  33 00 64 00 38 00 62 00  e.k.y.b.3.d.8.b.
0150:  62 00 77 00 65 00 5c 00  77 00 74 00 2e 00 65 00  b.w.e.\.w.t...e.
0160:  78 00 65 00 00 00 30 00  00 00                    x.e...0...

  • fsutil reparsepoint query C:\Users\USER_NAME}\AppData\Local\Microsoft\WindowsApps\Microsoft.WindowsTerminal_8wekyb3d8bbwe\wt.exe

Reparse Tag Value : 0x8000001b
Tag value: Microsoft

Reparse Data Length: 0x0000016a
Reparse Data:
0000:  03 00 00 00 4d 00 69 00  63 00 72 00 6f 00 73 00  ....M.i.c.r.o.s.
0010:  6f 00 66 00 74 00 2e 00  57 00 69 00 6e 00 64 00  o.f.t...W.i.n.d.
0020:  6f 00 77 00 73 00 54 00  65 00 72 00 6d 00 69 00  o.w.s.T.e.r.m.i.
0030:  6e 00 61 00 6c 00 5f 00  38 00 77 00 65 00 6b 00  n.a.l._.8.w.e.k.
0040:  79 00 62 00 33 00 64 00  38 00 62 00 62 00 77 00  y.b.3.d.8.b.b.w.
0050:  65 00 00 00 4d 00 69 00  63 00 72 00 6f 00 73 00  e...M.i.c.r.o.s.
0060:  6f 00 66 00 74 00 2e 00  57 00 69 00 6e 00 64 00  o.f.t...W.i.n.d.
0070:  6f 00 77 00 73 00 54 00  65 00 72 00 6d 00 69 00  o.w.s.T.e.r.m.i.
0080:  6e 00 61 00 6c 00 5f 00  38 00 77 00 65 00 6b 00  n.a.l._.8.w.e.k.
0090:  79 00 62 00 33 00 64 00  38 00 62 00 62 00 77 00  y.b.3.d.8.b.b.w.
00a0:  65 00 21 00 41 00 70 00  70 00 00 00 43 00 3a 00  e.!.A.p.p...C.:.
00b0:  5c 00 50 00 72 00 6f 00  67 00 72 00 61 00 6d 00  \.P.r.o.g.r.a.m.
00c0:  20 00 46 00 69 00 6c 00  65 00 73 00 5c 00 57 00   .F.i.l.e.s.\.W.
00d0:  69 00 6e 00 64 00 6f 00  77 00 73 00 41 00 70 00  i.n.d.o.w.s.A.p.
00e0:  70 00 73 00 5c 00 4d 00  69 00 63 00 72 00 6f 00  p.s.\.M.i.c.r.o.
00f0:  73 00 6f 00 66 00 74 00  2e 00 57 00 69 00 6e 00  s.o.f.t...W.i.n.
0100:  64 00 6f 00 77 00 73 00  54 00 65 00 72 00 6d 00  d.o.w.s.T.e.r.m.
0110:  69 00 6e 00 61 00 6c 00  5f 00 31 00 2e 00 35 00  i.n.a.l._.1...5.
0120:  2e 00 31 00 30 00 32 00  37 00 31 00 2e 00 30 00  ..1.0.2.7.1...0.
0130:  5f 00 78 00 36 00 34 00  5f 00 5f 00 38 00 77 00  _.x.6.4._._.8.w.
0140:  65 00 6b 00 79 00 62 00  33 00 64 00 38 00 62 00  e.k.y.b.3.d.8.b.
0150:  62 00 77 00 65 00 5c 00  77 00 74 00 2e 00 65 00  b.w.e.\.w.t...e.
0160:  78 00 65 00 00 00 30 00  00 00                    x.e...0...
@TrevCan commented on GitHub (Feb 3, 2021): sure, - `fsutil reparsepoint query C:\Users\{USER_NAME}\AppData\Local\Microsoft\WindowsApps\wt.exe` ``` Reparse Tag Value : 0x8000001b Tag value: Microsoft Reparse Data Length: 0x0000016a Reparse Data: 0000: 03 00 00 00 4d 00 69 00 63 00 72 00 6f 00 73 00 ....M.i.c.r.o.s. 0010: 6f 00 66 00 74 00 2e 00 57 00 69 00 6e 00 64 00 o.f.t...W.i.n.d. 0020: 6f 00 77 00 73 00 54 00 65 00 72 00 6d 00 69 00 o.w.s.T.e.r.m.i. 0030: 6e 00 61 00 6c 00 5f 00 38 00 77 00 65 00 6b 00 n.a.l._.8.w.e.k. 0040: 79 00 62 00 33 00 64 00 38 00 62 00 62 00 77 00 y.b.3.d.8.b.b.w. 0050: 65 00 00 00 4d 00 69 00 63 00 72 00 6f 00 73 00 e...M.i.c.r.o.s. 0060: 6f 00 66 00 74 00 2e 00 57 00 69 00 6e 00 64 00 o.f.t...W.i.n.d. 0070: 6f 00 77 00 73 00 54 00 65 00 72 00 6d 00 69 00 o.w.s.T.e.r.m.i. 0080: 6e 00 61 00 6c 00 5f 00 38 00 77 00 65 00 6b 00 n.a.l._.8.w.e.k. 0090: 79 00 62 00 33 00 64 00 38 00 62 00 62 00 77 00 y.b.3.d.8.b.b.w. 00a0: 65 00 21 00 41 00 70 00 70 00 00 00 43 00 3a 00 e.!.A.p.p...C.:. 00b0: 5c 00 50 00 72 00 6f 00 67 00 72 00 61 00 6d 00 \.P.r.o.g.r.a.m. 00c0: 20 00 46 00 69 00 6c 00 65 00 73 00 5c 00 57 00 .F.i.l.e.s.\.W. 00d0: 69 00 6e 00 64 00 6f 00 77 00 73 00 41 00 70 00 i.n.d.o.w.s.A.p. 00e0: 70 00 73 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 p.s.\.M.i.c.r.o. 00f0: 73 00 6f 00 66 00 74 00 2e 00 57 00 69 00 6e 00 s.o.f.t...W.i.n. 0100: 64 00 6f 00 77 00 73 00 54 00 65 00 72 00 6d 00 d.o.w.s.T.e.r.m. 0110: 69 00 6e 00 61 00 6c 00 5f 00 31 00 2e 00 35 00 i.n.a.l._.1...5. 0120: 2e 00 31 00 30 00 32 00 37 00 31 00 2e 00 30 00 ..1.0.2.7.1...0. 0130: 5f 00 78 00 36 00 34 00 5f 00 5f 00 38 00 77 00 _.x.6.4._._.8.w. 0140: 65 00 6b 00 79 00 62 00 33 00 64 00 38 00 62 00 e.k.y.b.3.d.8.b. 0150: 62 00 77 00 65 00 5c 00 77 00 74 00 2e 00 65 00 b.w.e.\.w.t...e. 0160: 78 00 65 00 00 00 30 00 00 00 x.e...0... ``` - `fsutil reparsepoint query C:\Users\USER_NAME}\AppData\Local\Microsoft\WindowsApps\Microsoft.WindowsTerminal_8wekyb3d8bbwe\wt.exe` ``` Reparse Tag Value : 0x8000001b Tag value: Microsoft Reparse Data Length: 0x0000016a Reparse Data: 0000: 03 00 00 00 4d 00 69 00 63 00 72 00 6f 00 73 00 ....M.i.c.r.o.s. 0010: 6f 00 66 00 74 00 2e 00 57 00 69 00 6e 00 64 00 o.f.t...W.i.n.d. 0020: 6f 00 77 00 73 00 54 00 65 00 72 00 6d 00 69 00 o.w.s.T.e.r.m.i. 0030: 6e 00 61 00 6c 00 5f 00 38 00 77 00 65 00 6b 00 n.a.l._.8.w.e.k. 0040: 79 00 62 00 33 00 64 00 38 00 62 00 62 00 77 00 y.b.3.d.8.b.b.w. 0050: 65 00 00 00 4d 00 69 00 63 00 72 00 6f 00 73 00 e...M.i.c.r.o.s. 0060: 6f 00 66 00 74 00 2e 00 57 00 69 00 6e 00 64 00 o.f.t...W.i.n.d. 0070: 6f 00 77 00 73 00 54 00 65 00 72 00 6d 00 69 00 o.w.s.T.e.r.m.i. 0080: 6e 00 61 00 6c 00 5f 00 38 00 77 00 65 00 6b 00 n.a.l._.8.w.e.k. 0090: 79 00 62 00 33 00 64 00 38 00 62 00 62 00 77 00 y.b.3.d.8.b.b.w. 00a0: 65 00 21 00 41 00 70 00 70 00 00 00 43 00 3a 00 e.!.A.p.p...C.:. 00b0: 5c 00 50 00 72 00 6f 00 67 00 72 00 61 00 6d 00 \.P.r.o.g.r.a.m. 00c0: 20 00 46 00 69 00 6c 00 65 00 73 00 5c 00 57 00 .F.i.l.e.s.\.W. 00d0: 69 00 6e 00 64 00 6f 00 77 00 73 00 41 00 70 00 i.n.d.o.w.s.A.p. 00e0: 70 00 73 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 p.s.\.M.i.c.r.o. 00f0: 73 00 6f 00 66 00 74 00 2e 00 57 00 69 00 6e 00 s.o.f.t...W.i.n. 0100: 64 00 6f 00 77 00 73 00 54 00 65 00 72 00 6d 00 d.o.w.s.T.e.r.m. 0110: 69 00 6e 00 61 00 6c 00 5f 00 31 00 2e 00 35 00 i.n.a.l._.1...5. 0120: 2e 00 31 00 30 00 32 00 37 00 31 00 2e 00 30 00 ..1.0.2.7.1...0. 0130: 5f 00 78 00 36 00 34 00 5f 00 5f 00 38 00 77 00 _.x.6.4._._.8.w. 0140: 65 00 6b 00 79 00 62 00 33 00 64 00 38 00 62 00 e.k.y.b.3.d.8.b. 0150: 62 00 77 00 65 00 5c 00 77 00 74 00 2e 00 65 00 b.w.e.\.w.t...e. 0160: 78 00 65 00 00 00 30 00 00 00 x.e...0... ```
claunia commented 2026-01-31 03:11:56 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 3, 2021):

Curious. Those both point at the right version. So that's not the issue here...

When you search for wt.exe in the start menu, where does "Open file location" take you?
image

@zadjii-msft commented on GitHub (Feb 3, 2021): Curious. Those both point at the right version. So that's not the issue here... When you search for `wt.exe` in the start menu, where does "Open file location" take you? ![image](https://user-images.githubusercontent.com/18356694/106766454-80637680-65ff-11eb-913f-e02ce0d9f60f.png)
claunia commented 2026-01-31 03:11:56 +00:00
Author
Owner
Copy Link

@TrevCan commented on GitHub (Feb 3, 2021):

When you search for wt.exe in the start menu, where does "Open file location" take you?

C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.5.10271.0_x64__8wekyb3d8bbwe

@TrevCan commented on GitHub (Feb 3, 2021): > When you search for wt.exe in the start menu, where does "Open file location" take you? `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.5.10271.0_x64__8wekyb3d8bbwe`
claunia commented 2026-01-31 03:11:56 +00:00
Author
Owner
Copy Link

@TrevCan commented on GitHub (Feb 16, 2021):

Hello, it seems as if the issue is sort of worse now. I have updated to Microsoft Windows 10 Home Version [10.0.18363 Build 18363], previously Microsoft Windows [Version 10.0.18363.1316] and when executing wt.exe from the Windows Search bar, the Windows Terminal launches, but without the correct fonts and the .exe is pointing to a new version 1.5.x at the path C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.5.10411.0_x64__8wekyb3d8bbwe. It seems that Windows confused itself when updating and apparently reinstalled the 1.5.x version. When I open the json settings, it just appears very different from the one I have on the 'normal' Windows Terminal. If I search for Windows Terminal from the search bar it loads with the correct fonts and my configuration is still there. Below you can see screenshots when executing the wt.exe command from the Windows Search bar and when executing the Windows Terminal app.

wt.exe
image

Windows Terminal (normal)
image

(note: I blacked out my windows username and laptop name in case you see it any different).

@TrevCan commented on GitHub (Feb 16, 2021): Hello, it seems as if the issue is sort of worse now. I have updated to `Microsoft Windows 10 Home Version [10.0.18363 Build 18363]`, previously `Microsoft Windows [Version 10.0.18363.1316]` and when executing `wt.exe` from the Windows Search bar, the Windows Terminal launches, but without the correct fonts and the .exe is pointing to a new version 1.5.x at the path `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.5.10411.0_x64__8wekyb3d8bbwe`. It seems that Windows confused itself when updating and apparently reinstalled the 1.5.x version. When I open the json settings, it just appears very different from the one I have on the 'normal' Windows Terminal. If I search for `Windows Terminal` from the search bar it loads with the correct fonts and my configuration is still there. Below you can see screenshots when executing the `wt.exe` command from the Windows Search bar and when executing the `Windows Terminal` app. **`wt.exe`** ![image](https://user-images.githubusercontent.com/44383325/108110416-d6e99f80-7058-11eb-8d21-0bacbfdccf1f.png) **`Windows Terminal (normal)`** ![image](https://user-images.githubusercontent.com/44383325/108110520-fbde1280-7058-11eb-8220-39cd8abb68bd.png) (note: I blacked out my windows username and laptop name in case you see it any different).
claunia commented 2026-01-31 03:11:56 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 16, 2021):

Ugh, this is another shade of the same issue. Occasionally, running wt from the run dialog or shell search spawns Terminal without its package context (!) which naturally uses a different settings file and stuff. Gahhhh. I wasn't aware this issue was prevalent on 18362/3.

@DHowett commented on GitHub (Feb 16, 2021): Ugh, this is another shade of the same issue. Occasionally, running `wt` from the run dialog or shell search _spawns Terminal without its package context_ (!) which naturally uses a different settings file and stuff. Gahhhh. I wasn't aware this issue was prevalent on 18362/3.
claunia commented 2026-01-31 03:11:56 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 16, 2021):

FYI this also got reported on reddit, but I don't think OP ever ended up positing on GH

@zadjii-msft commented on GitHub (Feb 16, 2021): FYI this also got reported [on reddit](https://www.reddit.com/r/WindowsTerminal/comments/lkbzk4/start_windows_terminal_get_one_win_r_wt_get_other/), but I don't think OP ever ended up positing on GH
claunia commented 2026-01-31 03:11:56 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 26, 2021):

FWIW, some internal users have had success "repairing" the Terminal app in the settings app. Not sure if that'll work in this case too. The internal thread is still ongoing unfortunately.

@zadjii-msft commented on GitHub (Feb 26, 2021): FWIW, some internal users have had success "repairing" the Terminal app in the settings app. Not sure if that'll work in this case too. The internal thread is still ongoing unfortunately.
claunia commented 2026-01-31 03:11:57 +00:00
Author
Owner
Copy Link

@TrevCan commented on GitHub (Feb 26, 2021):

Thanks for the info, but what do you mean by entering the settings app? You mean uninstalling the app and installing it again ?

@TrevCan commented on GitHub (Feb 26, 2021): Thanks for the info, but what do you mean by entering the settings app? You mean uninstalling the app and installing it again ?
claunia commented 2026-01-31 03:11:57 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 26, 2021):

repair-app

@zadjii-msft commented on GitHub (Feb 26, 2021): ![repair-app](https://user-images.githubusercontent.com/18356694/109340026-191b9980-782e-11eb-9bca-9dabd92ba93c.gif)
claunia commented 2026-01-31 03:11:57 +00:00
Author
Owner
Copy Link

@TrevCan commented on GitHub (Feb 27, 2021):

Unfortunately, it didn't work. It did not change anything I believe. Correct fonts and configurations are not loading and it still points to a different .exe file.

@TrevCan commented on GitHub (Feb 27, 2021): Unfortunately, it didn't work. It did not change anything I believe. Correct fonts and configurations are not loading and it still points to a different `.exe` file.
claunia commented 2026-01-31 03:11:57 +00:00
Author
Owner
Copy Link

@fkalbe commented on GitHub (Mar 4, 2021):

Unfortunately, I'm facing the same issue as @TrevCan and repairing the Terminal app also didn't seem to change anything for me.

Microsoft Windows [Version 10.0.18363.0]

Windows Terminal Version: 1.6.10571.0

I think the issue just emerged today, possibly after an automatic update through the Microsoft Store?

EDIT: This workaround by letting the Windows Store install Windows Terminal on another drive seems to work for now . Additionally, I have disabled automatic updates in the Windows Store for now until this issue is fixed.

@fkalbe commented on GitHub (Mar 4, 2021): Unfortunately, I'm facing the same issue as @TrevCan and repairing the Terminal app also didn't seem to change anything for me. ``` Microsoft Windows [Version 10.0.18363.0] Windows Terminal Version: 1.6.10571.0 ``` I think the issue just emerged today, possibly after an automatic update through the Microsoft Store? **EDIT:** This [workaround](https://github.com/microsoft/terminal/issues/7081#issuecomment-790652941) by letting the Windows Store install Windows Terminal on another drive seems to work for now . Additionally, I have disabled automatic updates in the Windows Store for now until this issue is fixed.
claunia commented 2026-01-31 03:11:57 +00:00
Author
Owner
Copy Link

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

@fkalbe, @trevcan I'm gonna mark this as a /duplicate of #9452 -- I've got some instructions and a question in there, if you don't mind. 😄

@DHowett commented on GitHub (Mar 11, 2021): @fkalbe, @trevcan I'm gonna mark this as a /duplicate of #9452 -- I've got some instructions and a question in there, if you don't mind. :smile:
claunia commented 2026-01-31 03:11:57 +00:00
Author
Owner
Copy Link

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

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Mar 11, 2021): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 Resolution-Duplicate
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#12306
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?