Windows 10: Updated to 1511: "740: The requested operation requires elevation"

  1.    16 Nov 2015 #1

    Updated to 1511: "740: The requested operation requires elevation"


    In my normal user account (belonging to Users group) I maintain a folder with a bunch of convenient administrative shortcuts, which run certain applications under "Administrator" account through 'runas' utility. Each shortcut's command line looks as

    Code:
    C:\Windows\System32\runas.exe /user:Administrator /savecred "<command line>"
    Before update to version 1511 all my shortcuts were working fine. After the update most of them suddenly stopped working. Namely, running mmc shortcuts, like

    Code:
    C:\Windows\System32\runas.exe /user:Administrator /savecred "mmc compmgmt.msc"
    produces error "740: The requested operation requires elevation".

    Control panel shortcuts like

    Code:
    C:\Windows\System32\runas.exe /user:Administrator /savecred "control appwiz.cpl"
    generate a message box

    Code:
    ::{26EE0668-A00A-44D7-9371-BEB064C98683}\0\::{7B81BE6A-CE2B-4676-A29E-EB907A5126C5}
    Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.

    Some applications continue to work, some don't. SysInternal's Autoruns works fine. Far Manager doesn't suffer from it either. But CPU-Z shortcut

    Code:
    C:\Windows\System32\runas.exe /user:Administrator /savecred "C:\Utils\CPU-Z\cpuz_x64.exe"
    also fails with "740: The requested operation requires elevation".

    Is the something I can change (policy etc.) to restore the pre-1511 behavior?
    Last edited by AndreyT; 21 Nov 2015 at 18:13.
      My ComputerSystem Spec


  2. Posts : 3
    Windows 10 Pro
       17 Nov 2015 #2

    Hello AndreyT,

    I can confirm this strange behaviour!
    If I want to start an elevated commandbox with "runas" under the local administrator, a commandbox opens, but it
    definitely does not provide administrative rights. The behaviour is the same when I use the local administrator to log on: the account does not have "real administrative" rights anymore, although everything indicates that the account is the local administrator!

    The only way to start an elevated commandbox is to select the option from the start menu.
    The problem does not occur on a complete fresh installed Windows 10 1511, that's for sure.

    It cannot believe it, but Microsoft is able to destroy Windows with nearly every update!
    Why for the hell does "an update" a fresh Windows install?
    Nothing else is Windows 10 1511, a fresh Windows install that transfers some data! That's useless!
    I had to reinstall for example VirtualBox and all my certificates have disappeared.
    The Windows 10 1511 "update" is similar to an upgrade from Windows 8 to 10!!!

    It would be nice, if someone could offer a workaround for that strange "elevated commandline bug".

    Regards,
    Tupac
      My ComputerSystem Spec

  3.    18 Nov 2015 #3

    Tupac said: View Post
    The problem does not occur on a complete fresh installed Windows 10 1511, that's for sure.
    Can't confirm. I see the same "740" behavior on a clean install of 1511.
      My ComputerSystem Spec

  4.    18 Nov 2015 #4

    I don't know anything about this, but it appears to have something to do with trustlevels:

    C:\>runas /showtrustlevels
    The following trust levels are available on your system:
    0x20000 (Basic User)
      My ComputerSystem Spec


  5. Posts : 3
    Windows 10 Pro
       18 Nov 2015 #5

    NavyLCDR said: View Post
    I don't know anything about this, but it appears to have something to do with trustlevels:

    C:\>runas /showtrustlevels
    The following trust levels are available on your system:
    0x20000 (Basic User)
    On both systems the output is the same...so that should not be the problem.

    I've maybe found something: if I choose the option to start an elevated command promt from the start menu, I get (on the updated system) a link in the uac message box where I can get additional information concerning the certificate. I can imagine that this could cohere with the problem...but I cannot recognize any differences between the installed Microsoft certificates...

    Click image for larger version. 

Name:	tidwc5ix.jpg 
Views:	38 
Size:	99.4 KB 
ID:	49130
      My ComputerSystem Spec


  6. Posts : 3
    Windows 10 Pro
       21 Nov 2015 #6

    To your information: I think, that I have determined the problem.
    You have to set the key "FilterAdministratorToken" to "0" (to find in "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System").

    Regards,
    Tupac
      My ComputerSystem Spec

  7.    24 Nov 2015 #7

    Tupac said: View Post
    To your information: I think, that I have determined the problem.
    You have to set the key "FilterAdministratorToken" to "0" (to find in "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System").

    My machine did not have 'FilterAdministratorToken' value at that registry key. Adding it as a DWORD32 with value 0 (and rebooting) made no difference, unfortunately.
      My ComputerSystem Spec

  8.    24 Nov 2015 #8

    The funny part is that 'cmd.exe' does not suffer from this problem meaning that I can successfully run it as

    Code:
    runas.exe /user:Admin /savecred "cmd"
    which in turn means that I can use

    Code:
    runas /user:Admin /savecred "cmd /c compmgmt.msc"
    as a workaround to run Computer Management applet under 'Admin' account. Or, if I don't want to see console window hanging in the background, I can do

    Code:
    runas /user:Admin /savecred "cmd /c \"start compmgmt.msc\""
    In other words, if this new, more restrictive behavior was implemented as an additional security measure, this is a rather lousy security measure, since it is so easy to circumvent.
    Last edited by AndreyT; 24 Nov 2015 at 14:23.
      My ComputerSystem Spec

  9.    17 Dec 2015 #9

    AndreyT,

    experienced the same annoying 740 error after Win10 automatically updated itself to 1511, however on behalf of a pretty old Win7 related howto I was able to figure out what's going on: in this update they enabled by default Admin Approval Mode for built in Administrator. I was able to overcome it by disabling it in gpedit:

    windows settings / security settings / local policies / security options / User Account Control: Admin Approval Mode for built in Administrator account

    good luck!
      My ComputerSystem Spec


 

Related Threads
Hi, as with many I have upgraded to Windows 10 today and it is going well except for the fact I am unable to save any files or create new ones in the Documents and Pictures folders or any sub-folders within these folders, and I have no idea why it...
I have upgraded 5 machines and clean installed 3 machines. Experienced an issue with one machine with continuous corruption problems After the 3rd attempt I discovered that even with a Clean Install of Win 10 I get unrepairable errors - Sorry...
Backstory: I broke my windows 7 installation awhile ago and went to linux, without deleting the broken installation. Later when I discovered windows 10 I decided to go and use it but it broke, so I again installed windows 10. This is 3 windows...

Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 10:18.
Find Us