Opening wt.exe can no longer open as administrator (both WT and WT Preview)

[AriKrumbein]

Environment

Windows build number:  Microsoft Windows NT 10.0.21301.0 (aka 21301.1010 via WinVer)
Windows Terminal version (if applicable):
- WT Preview: 1.6.10412.0
- WT: 1.5.10411.0

Steps to reproduce

Scenario 1: directly Run as Administrator

• Navigate to install directory in Explorer (in my case, C:\Users[USERNAME]\AppData\Local\Microsoft\WindowsApps\Microsoft.WindowsTerminal_8wekyb3d8bbwe
• Right Click on wt.exe and click Run As Administrator

Scenario 2: Creating a shortcut to wt.exe

• Create a shortcut to the path above.
• Change the shortcut's properties to Run as Adminstrator

Expected behavior

Terminal shows a UAC prompt and launches elevated.

Actual behavior

A dialog box:

I can confirm the path is correct, and left click on the icon launches WT correctly.

Interestingly, clicking Run as Adminstrator when launching from Start does succeed.

[DHowett]

Was this working before either the WT or Windows update? You're using a dev build of Windows that has perhaps had some churn in app execution alias handling.

If you go to the "manage app execution aliases" page and disable/re-enable the wt.exe alias, is the issue resolved?

[AriKrumbein]

Yup! Resolved by turning on and off wt.exe alias.

Could be a dupe of #7188?

[zadjii-msft]

Very well might be. The Store has been working in mysterious ways as of late:

• Windows Terminal Preview crashes on startup from executing command-line wt. #9017
• Windows terminal installation from microsoft store is not working after being crashed by McAfee antivirus. #9159
• WT command in Windows Explorer does not work anymore #7188
• New install unable to Launch via Start Menu #9062

All these are similar, but I don't think we've got a single root cause narrowed down.

/dup #7188

[ghost]

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!