Contacted MS support, they find out this is known issue.
Windows 11 terminal admin elevation does not work
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?
14 answers
Sort by: Most helpful
-
Pavel yannara Mirochnitchenko 12,471 Reputation points MVP
2021-12-20T08:16:33.013+00:00 -
Mike Crawford 6 Reputation points
2022-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 12,471 Reputation points MVP
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 12,471 Reputation points MVP
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 12,471 Reputation points MVP
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.""