Database Search
If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.
TechHome
UAC
- !! Understanding UAC !!
- A Referral was Returned From the Server
- Admin Privilege OK in WinBatch, but not Compiled
- Cmd Prompt Run As Administrator
- Determine if Application is Elevated
- Elevation Level and Environment Varibles
- FileCopy and UAC
- Installation Scripts
- Installing a program using Compatibility Mode
- Mapped Drives Issue with UAC
- Protected Directories
- Run As Admin WinBatch Script With UAC On
- RunWithLogon and UAC
- Scheduled Tasks
- SendKey and UAC
- Signing and Certificates
- StartUp No Prompt
- UAC Administrator Account
- UAC and WinBatch Studio
- UAC Help
- UAC Local System Account
- Unknown Publisher
- wntAccessAdd 64-bit Registry Key
- wntRunAsUser Issues
- wntShare UAC Problem
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
StartUp No Prompt
Keywords: Vista UAC No Prompt Consent Manifest Requested Execution Level AsInvoker As Invoker HighestAvailable Highest Available
Question:
With Vista UAC on,I created a simple wbt as Message("Hello","Hello") and compile as Requested Execution Level: highest available. When I execute the exe, I get "User account control" with Cancel or Allow. When I put to Startup, the exe shows on the Run Blocked Program. What can I do to let it run as UAC off. Thanks.Answer:
The problem is that you are using highest available which would cause the UAC prompt to appear.
If you are looking to have your compiled WinBatch exe run during the startup process, you should compile the script using
the 'Requested Execution Level' [ AsInvoker ] so that all users can run the software without the need for a UAC elevation.
A couple of exceptions:
- Setup applications that need to complete their setup after a reboot should be putting their application in the RunOnce key. This key gets consumed by the next Administrator account that logs on, and the setup will continue without the need for an elevation. (This key can only be set by a program running with elevated privileges.)
- Applications that require UAC elevation that gets pushed out via the POLICY\RUN keys will not get blocked at logon. They will run and will either result in the Secure Desktop prompt or appear in the taskbar as a blinking button that will require user input before the desktop switch occurs.
Article ID: W18323
Filename: StartUp No Prompt.txt
File Created: 2012:07:24:10:37:46
Last Updated: 2012:07:24:10:37:46