T
Thomas Kluge
I dicovered a strange behavior of the CreateProcess() implementation under
Vista Beta 2. I tried to run a Process with
requestedExecutionLevel="requireAdministrator" from within a process with
level="asInvoker".
What I did expect is an Admin-Credential Box on standard users accounts
(thats the case) and a an admin confirmation box on admin accounts (thats
not the case). In the last case the execution fails with GetLastError()==740
which is: "The requested operation requires elevation". It's the same error
which would occur if the user would press a "No". So what is the initiator
of error 740? If I'm using the function ShellExecute() instead of
CreateProcess the call leads to the expected confirmation box.
Next one: If the parent process execution level is "asInvoker", a system
message states compatibility problems and taken settings. The next time, I
run the application, the error 740 is disappeared. If the parent process
execution level is not given per manifest <requestedPrivileges> the
described error 740 is permanent.
note: both applications are standard VS6.0 MFC-applications.
I did not change the standard lua settings :
User Account Control: Behavior of the elevation prompt for
administrators Prompt for consent
User Account Control: Behavior of the elevation prompt for standard
users Prompt for credentials
regards,
Thomas Kluge
T-Systems Enterprise Services GmbH
Vista Beta 2. I tried to run a Process with
requestedExecutionLevel="requireAdministrator" from within a process with
level="asInvoker".
What I did expect is an Admin-Credential Box on standard users accounts
(thats the case) and a an admin confirmation box on admin accounts (thats
not the case). In the last case the execution fails with GetLastError()==740
which is: "The requested operation requires elevation". It's the same error
which would occur if the user would press a "No". So what is the initiator
of error 740? If I'm using the function ShellExecute() instead of
CreateProcess the call leads to the expected confirmation box.
Next one: If the parent process execution level is "asInvoker", a system
message states compatibility problems and taken settings. The next time, I
run the application, the error 740 is disappeared. If the parent process
execution level is not given per manifest <requestedPrivileges> the
described error 740 is permanent.
note: both applications are standard VS6.0 MFC-applications.
I did not change the standard lua settings :
User Account Control: Behavior of the elevation prompt for
administrators Prompt for consent
User Account Control: Behavior of the elevation prompt for standard
users Prompt for credentials
regards,
Thomas Kluge
T-Systems Enterprise Services GmbH