Skip to content
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

Windows PowerShell (Admin) on some computers with Windows 10 only Windows PowerShell work #15890

Closed
maisondasilva opened this issue Aug 28, 2023 · 9 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@maisondasilva
Copy link

maisondasilva commented Aug 28, 2023

Windows Terminal version

1.17.11461.0

Windows build number

10.0.19045.3393

Other Software

No response

Steps to reproduce

263811459-d7abbd6d-7f44-494b-9b7c-ef01d113ce8a.mp4

Expected Behavior

Windows PowerShell (Admin) open Terminal Admin

Actual Behavior

Windows PowerShell (Admin) open poweshell admin

@maisondasilva maisondasilva added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Aug 28, 2023
@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #10276 for more discussion.

/dup #10276

@microsoft-github-policy-service
Copy link
Contributor

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!

@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Aug 28, 2023
@maisondasilva
Copy link
Author

Thanks for the warning, I'd looked for it but couldn't find it!

@zadjii-msft
Copy link
Member

No worries - that's a wacky one that you'd have to know existed to be able to find it. Heck I knew it existed and still took me 10 minutes to find it 😛

@maisondasilva
Copy link
Author

maisondasilva commented Aug 28, 2023

No worries - that's a wacky one that you'd have to know existed to be able to find it. Heck I knew it existed and still took me 10 minutes to find it 😛

😂😂.
Are there any alternative solutions? The strange thing is that I have other computers just like it and it works as expected, same version all the same!

@zadjii-msft
Copy link
Member

The strange thing is that I have other computers just like it and it works as expected

excuse me what 👀

The "default terminal" functionality definitely has never worked for elevated commandline applications. On Windows 11 the Win+X menu has "Terminal (Admin)" in it, which doesn't use the default terminal feature. Maybe that's what you've seen?

@maisondasilva
Copy link
Author

maisondasilva commented Aug 28, 2023

The strange thing is that I have other computers just like it and it works as expected

excuse me what 👀

The "default terminal" functionality definitely has never worked for elevated commandline applications. On Windows 11 the Win+X menu has "Terminal (Admin)" in it, which doesn't use the default terminal feature. Maybe that's what you've seen?

See video

What I noticed in the video is that both options always open as administrator
I'm trying to understand what difference there is that could be generating this behavior

Win10 Pro same version 10.0.19045.3393

win10.work.mp4

@zadjii-msft
Copy link
Member

wat

Are you by any chance running with UAC entirely disabled?

reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLua should be able to tell us - 0 means UAC is disabled, anything else and it should be on.

@maisondasilva
Copy link
Author

That's right, it seems that whoever maintains the system used on this server has deactivated it, and activating it won't work again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants