Database Search
TechHome
- 253 Unable to Attach to Window
- Application Compatiblity on Vista
- Check if UAC is Enabled
- Control Manager and 64 bit Controls
- Disable UAC Prompt for an Application
- Disable User Account Control
- DiskScan Issue
- Elevation Prompt
- File System Redirection
- How To Add a Friendly Name to a Certificate
- Manifests In WinBatch Explained
- Mapped Network Drive Issue with UAC On
- Minimized if UAC is Enabled
- Named Pipes on Vista
- Net Send Alternative
- PopMenu Run at StartUp Issue
- Problem Using IniWritePvt on Vista
- Programatically Turn UAC off
- Prompted When Running WBT
- Registry Redirection
- RegSetValue HKEY_LOCAL_MACHINE Error 1452 on Vista
- Requested Operation Requires Elevation
- Roboscripter Issues with 64 bit Window Controls
- Services on Vista
- Tray Applications not Launching Automatically
- UAC and OLE Drag-n-Drop
- UiAccess TRUE and Protected Locations
- Vista blocks PopMenu on startup
- Vista UAC Questions
- WinBatch and 64 Bit Windows
- WinBatch Benchmark on Vista
- WinBatch Studio and UAC
- WinBatch Studio Hints Problem
- WinBatch Studio Mapped Drives Issue
- WWWBATCH INI
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Tray Applications not Launching Automatically
Keywords: systray apps
Issues related to tray applications not launching automatically on Vista [due to UAC being enabled] can be resolved by properly constructing a manifest for the EXE file, as well as properly confuring Vista to allow that application to run unchallenged. The alternative is to disable UAC.
On Vista this issue occurs because a program or a service that has User Account Control (UAC) restrictions tries to start during the Windows Vista startup process or logon process. To simplify these processes, Software Explorer blocks programs or services that require UAC confirmation from running.
What uiAccess setting are you using? It is my understanding that requested execution level should be AsInvoker and uiAccess should be set to FALSE.
We had an issue with our popmenu utility causing this problem on Vista. The popMenu tool needs to be able to do things that could have User Account Control (UAC) restrictions. The way we resolved this issue was to create a simple startup script that called UacExePromptTest that checked if the EXE was going to cause a UAC prompt. If the EXE was going to cause a UAC prompt, we simply loaded the simple startup script into the system try awaiting a click. The first time the user clicked on the icon in the task bar we then launched the real exe using ShellExecute.
See also: http://vistasupport.mvps.org/run_blocked_startup_programs.htm
Article ID: W17492
File Created: 2008:04:10:15:11:32
Last Updated: 2008:04:10:15:11:32