-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Can't run Windows Terminal without Administrator #13197
Comments
I reset UAC and reboot, and it works for me. |
"reset" means I didn't change the level. Mine is "Never notify", I click it, and then click "OK", and then it said I need to reboot. It works after reboot. Btw, I change the level to default, and reboot again, it works too. |
That's a weird way to use the words, but OK.
Well, I don't want to nullify all security on my computer. There's a reason UAC exists. |
I'm using the default level, and it works. I think you can set it to any level, just set it again. Click it to make it saying you need to restart the computer. |
|
I'm actually not for some reason? I can change the level all I want without restarting. Even completely disable it and re-enable it again and the changes apply instantly (i.e. it's not asking me to reboot). Should I just reboot anyway after messing with it? |
It must be a bug. |
Rebooted my computer again, still can't open Windows Terminal without administrator. :/ |
Sorry for not helping. |
<meta discussion> We need a better way of reporting these issues to the appx team - We simply don't have the debugging knowhow to investigate these properly. |
Make sure in |
There is no |
woah, I have no idea how that got clicked, I used ctrl+enter to comment |
Same issue here when I run Terminal (Admin) with a non-admin account and input my admin creds. Is this being looked into? This a fresh build of Windows 11 22H2. |
@LoganDark Nope, those are App Execution Aliases, which are reparse points, which the OS does a really bad job of telling you what they mean. |
Is there any way to figure out why non-administrators cannot execute them? |
I mean, the reparse point isn't an executable itself. It's just like, a symlink, that points at the actual exe. Trick is, that AEA's for Store apps point at an exe on the filesystem that has super restricted permissions, such that even admins can't execute it normally. However, there's a magic handoff in CreateProcess that knows how to delegate the creation of a packaged process to the right set of ACLs. It's a process I don't fully understand, to be totally honest. That magic lets apps run with special store-granted permissions only, but from the user context it seems like nothing weird happened It's definitely weird, though, that you can't run the Terminal without admin permissions. That's unexpected. Does that repro for any other Store apps? Like, maybe |
Yeah, I understand what you mean. You still execute them in order to do the reparse magic, though.
The However, since the in-place reinstall, built-in apps like Alarms & Clock or Calendar work just fine. |
Okay yea this is definitely a Centennial issue then. Alarms&Clock, Calendar, Calculator - these are all apps that run in an app container. That's fundamentally different than Terminal, Python, WSL distros, etc, which do not have an app container. We need to connect you up with someone on the appx/msix/deployment team to help investigate this, cause this is definitely not something we (the Terminal team) are equipped to debug. |
So far I haven't had any issues with accessing WSL, either through Windows Terminal (as admin),
I would definitely appreciate that very much, thank you! My email can be found on my GitHub profile. You're welcome to have someone contact me, and if we can find a solution I'll make sure to post it here. |
there are two |
I have the same issue - I cannot start Windows Terminal outside of Administrator Mode, whether it's |
This solves my problem, thanks a lot. |
Windows Terminal version
1.13.11431.0
Windows build number
10.0.19041.572
Yes, this has actually downgraded since my last bug report. Blame the fact that I had limited download options.
Other Software
No response
Steps to reproduce
See #13099 (comment) and the comments leading up to it.
Expected Behavior
No response
Actual Behavior
Windows Terminal, through any amount of reinstalls, now cannot run without Administrator. I also cannot double-click the msixbundle to install (I get some permission error), but
Add-AppxPackage
works.The
wt
command is not found in a non-Administrator Command Prompt, but it is found in an Administrator Command Prompt.No Start Menu entries work for any part of Windows Terminal, not even the shortcuts, unless run as Administrator.
The text was updated successfully, but these errors were encountered: