cannot start Windows Terminal from Run diaglog #10188

Closed
opened 2026-01-31 02:14:45 +00:00 by claunia · 3 comments
Owner

Originally created by @long-nguyenxuan on GitHub (Aug 17, 2020).

Environment

Windows build number: [Version 10.0.19041.450]
Windows Terminal version (if applicable): 1.1.2233.0

Steps to reproduce

  1. Install Windows Terminal from msixbundle Microsoft.WindowsTerminalPreview_1.2.2234.0_8wekyb3d8bbwe.msixbundle
  2. Win+R to open Run diaglog
  3. wt -> enter

Expected behavior

Windows Terminal got executed and showed up

Actual behavior

Error message throw

[Window Title]
C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.2.2234.0_x64__8wekyb3d8bbwe\wt.exe

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

[OK]

Futher notice

In step 2, if I open it with Ctrl+Shift+Enter combo (open in Administrator mode), then Windows Terminal showed up successfully in Administrator mode, but on some system, I don't have Administrator role to run it.

Originally created by @long-nguyenxuan on GitHub (Aug 17, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [Version 10.0.19041.450] Windows Terminal version (if applicable): 1.1.2233.0 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1. Install Windows Terminal from msixbundle `Microsoft.WindowsTerminalPreview_1.2.2234.0_8wekyb3d8bbwe.msixbundle` 2. Win+R to open Run diaglog 3. `wt` -> `enter` # Expected behavior Windows Terminal got executed and showed up <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior Error message throw ``` [Window Title] C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.2.2234.0_x64__8wekyb3d8bbwe\wt.exe [Content] Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item. [OK] ``` # Futher notice In step 2, if I open it with `Ctrl+Shift+Enter` combo (open in Administrator mode), then Windows Terminal showed up successfully in Administrator mode, but on some system, I don't have Administrator role to run it. <!-- What's actually happening? -->
claunia added the Resolution-Duplicate label 2026-01-31 02:14:45 +00:00
Author
Owner

@KalleOlaviNiemitalo commented on GitHub (Aug 17, 2020):

This looks similar to https://github.com/microsoft/terminal/issues/7188. The workaround is to enable the wt.exe app execution alias of Windows Terminal Preview (not Windows Terminal).

@KalleOlaviNiemitalo commented on GitHub (Aug 17, 2020): This looks similar to <https://github.com/microsoft/terminal/issues/7188>. The workaround is to enable the `wt.exe` app execution alias of Windows Terminal Preview (not Windows Terminal).
Author
Owner

@DHowett commented on GitHub (Aug 18, 2020):

Yes, this is effectively a /duplicate of #7188

Once both package versions have the same alias structure, this bug should go away.

@DHowett commented on GitHub (Aug 18, 2020): Yes, this is effectively a /duplicate of #7188 Once both package versions have the same alias structure, this bug should go away.
Author
Owner

@ghost commented on GitHub (Aug 18, 2020):

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 (Aug 18, 2020): 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.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#10188