Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
8,164 questions
Contacted MS support, they find out this is known issue.
Windows 11 terminal admin elevation does not work
Pavel yannara Mirochnitchenko
11,716
Reputation points
I have Win10 and Win11 managed devices via Intune and for admin tasks, I use additional accounts which has AzureAD role assigned like Device Local Administrators. In Win10, elevating admin rights and executing run as admin works fine, in Win11 it doesn't. In Windows 11, after couple of tries entering admin credits via UAC, I get:
"The application cannot be started for the target user. Please login as the user and explicitly install this package."
So that terminal command line must be installed seperetly or something? Is this a bug?
{count} vote
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 81%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERA%3C/text%3E%3C/svg%3E)
Reza-Ameri 16,831 Reputation points2021-12-05T16:04:07.757+00:00 Are you using local account or Azure account?
Are you following the same procedure as the one for the Windows 10 in the Windows 11? -
Pavel yannara Mirochnitchenko 11,716 Reputation points
2021-12-06T21:35:18.367+00:00 - Azure account
- exact same process in Win10 and Win11 yes
It turns out, this problem is only about the Terminal Command line. Other UAC features work in Win11.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 72%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anthony 1 Reputation point2022-02-03T17:11:00.223+00:00 I am also unable to launch Windows Terminal (Admin) with a user account which is capable of elevating to perform other administrative actions on the device.
Sign in to comment
14 answers
Sort by: Most helpful
-
Pavel yannara Mirochnitchenko 11,716 Reputation points
2021-12-20T08:16:33.013+00:00 -
pilgi3 21 Reputation points2022-03-23T10:28:52.93+00:00 |Did you get an answer from microsoft support when this issue get fixed?
-
Pavel yannara Mirochnitchenko 11,716 Reputation points
2022-05-09T16:45:25.517+00:00 No :(
Sign in to comment -
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(182.40000000000003, 61%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMC%3C/text%3E%3C/svg%3E)
Mike Crawford 6 Reputation points2022-05-06T09:44:18.01+00:00 On an AAD joined machine, if you sign in as the elevated user account (admin) and run Terminal once, then sign out, then you should be able to now run Terminal elevated back in a standard user account.
I think there are others apps in Win11 where you also have to do this to be able to subsequently run elevated.
Regards
-
Pavel yannara Mirochnitchenko 11,716 Reputation points
2022-05-09T16:46:34.523+00:00 Still sounds like a bug for me
-
Humberto Jorquera 0 Reputation points2023-06-09T12:20:34.2566667+00:00 It works once I did this, but yeah the behaviour its buggy.
Sign in to comment -
-
Pavel yannara Mirochnitchenko 11,716 Reputation points
2022-10-24T16:47:40.163+00:00 New 22H2 build, same bug :D
(I have Windows Terminal sitting there, not Powershell like previously claimed)
-
Pavel yannara Mirochnitchenko 11,716 Reputation points
2023-07-17T11:30:14.53+00:00 I can see it works after this june patch, so CU 07-2023 does fix the issue!
-
Pavel yannara Mirochnitchenko 11,716 Reputation points
2021-12-10T11:59:27.377+00:00 It is only the Terminal which elevation does not work and it asks then for ""The application cannot be started for the target user. Please login as the user and explicitly install this package.""