4

Run into a little bit of a snag with Windows 10, and it's a fairly well known one - the problem is that I'm struggling to find a Windows 10 compatible fix that actually works!

It's the old "regular users have to input their password to load task manager" chestnut again. How, exactly, do I work around this? Seeing as that inputting any valid credentials in gives you access to the task manager, I don't see why this is needed. I've mucked around with the UAC GPOs to try and get it to work, but that hasn't helped. I've also tried to start task manager with Windows, which in itself would be ideal as I can do that without elevation - but I can't see how to start it minimized, as everything I've seen simply doesn't take effect.

Any solutions would be much appreciated. As to why our users need task manager; well, Microsoft Office likes to tie itself in knots every now and again. It's much better for everyone's productivity to be able to actually kill the rogue tasks themselves!

13
  • Can you be more specific? I can log onto Windows 10 with a standard (non admin user) and Task Manager opens just fine (?). Commented Feb 27, 2017 at 21:31
  • I know, that's what it should be doing. But for whatever reason, probably an old GPO somewhere, we don't get that - it prompts for a password if you're not an admin! Commented Mar 1, 2017 at 8:38
  • What password does it prompt for? Is it a UAC prompt? (Please be more specific.) Commented Mar 3, 2017 at 19:36
  • It is a UAC prompt, yes. It asks for admin details, but in fact it is actually just fine with any user, as long as the details are correct. Interestingly enough, I've only observed this behaviour on our Windows 10 Anniversary edition computers - the one remaining on version 1511 (which has a broken taskbar... still) worked just fine, even with the same GPOs! Commented Mar 6, 2017 at 10:49
  • Build a brand new Windows 10 machine, do not join it to a domain, and update it fully. Do you see the behavior? If not, then you know the behavior is likely caused by one of the GPO settings. Commented Mar 6, 2017 at 17:44

3 Answers 3

2

Run this, and logoff/on

setx.exe __COMPAT_LAYER runAsInvoker 

If you have Admin rights and run this then some commands [e.g. gpedit.msc] will no longer auto-elevate and you will need to "Run as Administrator"

1
  • Didn't work on W10_1803 Commented Jul 30, 2018 at 14:58
1

Finally I have found the solution to this. Props go to a reddit post.

The issue is with the group policy "load and unload device drivers". Computer configuration -> Policies -> windows settings -> security settings -> local policies -> user rights assignment -> load and unload device drivers.

if this is set to a group the limited user is a member of (everyone, domain users, etc) then the prompt is displayed. if you set it instead to Administrators, the prompt is suppressed and everything works fine. I am not sure the ramifications of changing this value as it has been set for us since time immemorial. Seems to have to do with accepting unsigned device drivers. If everything suddenly stops working then i will have to set it back, but the setting goes all the way back to win2k so it may no longer be relevant (except to F up my shiz)...

0

I've had this problem for past 4 months. I used to be a domain admin and removed that from my daily account. It was driving me mad getting UAC prompted for basic tasks like you mentioned. I finally took a deeper look at my group memberships. The key for me was looking at indirect (nested) memberships (I used Adaxes to do so, not sure best way to do so using standard AD tools). My account was a member of Group Policy Creator Owners. After removing that, doing gpupdate and finally a reboot I was able to launch stuff like Event Viewer, Task Manager, etc without the UAC prompt!!

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.