my program needs to start with Windows under all user accounts. however when the startup entry is added, User Account Control prevents the program from running. you can manually run the program by clicking the warning in the notification area, but is there no way to allow it to automatically run, without user interaction? A way to tell UAC not to block it? Of course my suggestion is just turn off that UAC junk, but some people may not want to.

Refactor the application not to unnecessarily require Administrator rights, manifest it with a requiredExecutionLevel of asInvoker and it will run fine at startup. Note that a program that runs at startup and requires Administrator rights will always fail, even on XP or Vistawith UAC disabled, if the logging in useris only a Standard User.

The software starts up OK on standard user accounts on XP. On Vista however it seems that you need Admin rights to do anything, even something like deleting a shortcut. Once I manually run the program on Vista, I don't encounter any prompts from UAC (although I haven't tested every area of the program yet). The program is a security-oriented app and I would assume that some things it does would require Admin rights, but as mentioned it runs OK on standard XP accounts as well as after being manually started on Vista. I should probably mention that the program is written in VB6. (not worth migrating it to .NET as VB6 has not limited me in any way, ever)

hmm, i know i did extensive testing before and had no problems under standard or even guest accounts (on xp) but now the program is unable to read or save files i'm not sure what could have changed, or what to do to fix it. i don't expect anyone to explain something basic like this but any links to info would be appreciated. thanks

The MSDN Vista forums are also a good place to ask development questions, regardless of how basic they may or may not be. This post in particular links to a number of really good resources that might help identify issues in your application. You'll also want to manifest your app to mark it Vista compatible as seen here. There are instructions for doing the same with VB6 here, though I haven't tried them so can't say how helpful they are.

i'm puttign this problem on the back burner but for anyone stumbling across this later, the reason it worked fine under XP before, but not now, is cause last time i was using FAT32.