Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
8,239 questions
Latest build, same issue :(
Windows 11 terminal admin elevation does not work
Pavel yannara Mirochnitchenko
11,716
Reputation points MVP
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,836 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 MVP
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 MVP
2023-01-17T12:20:15.78+00:00 -
Pavel yannara Mirochnitchenko 11,716 Reputation points MVP
2023-01-28T09:12:55.3266667+00:00 If I sign in with local admin on full desktop first, then on user's desktop uac for terminal will work and open terminal fine. This is quite stupid, but some of workaround.
-
![](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(73.60000000000001, 98%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKG%3C/text%3E%3C/svg%3E)
Karas, Greg 0 Reputation points2023-02-10T15:39:10.5333333+00:00 It's useless for us. Our 1st line team often needs to be able to 'run as' when helping someone over QuickAssist, it makes no sense to switch user first as you'd lose your QuickAssist session!
-
Pavel yannara Mirochnitchenko 11,716 Reputation points MVP
2023-02-14T06:18:01.6066667+00:00 Exactly! Sure you can search cmd or powershell but it would be nice to have primary command console available as quick as possible.
-
pilgi3 21 Reputation points2023-04-03T09:08:12.58+00:00 I created a microsoft ticket two week ago and they confirmed that this is a bug.
They wrote this will be fixed in the next windows 11 version (2023?). It also can be tested in one of the next dev builds.
Currently it is not sure if they will backport the fix into 22H2.The support employee try his best to get this into the timeline and there are more tickets from companies with this issue.
So finger-crossed this get fixed maybe soon.
-
Pavel yannara Mirochnitchenko 11,716 Reputation points MVP
2023-04-03T11:47:48.8933333+00:00 This surprise me. I have few engineers working on this for few months, I have demonstrated this behavior 4-5 times for them, they are still testing it :D
Thanks @pilgi3 for letting us know.
Sign in to comment -
-
Pavel yannara Mirochnitchenko 11,716 Reputation points MVP
2023-04-20T11:56:54.19+00:00 Heh, finally got a answer from MS: "is a known issue and might get resolved with May or June monthly CU update"
-
pilgi3 21 Reputation points
2023-05-04T06:31:11.36+00:00 It is my status as well.
The microsoft technician was able to send me a private pre-CU for testing.With this CU installed, I can confirm the bug is gone!
His statement was, the update will be backported to 22H2 with an optional CU at end of June and will be implemented in the monthly CU of July.
Sign in to comment -