Vista Home Premium "User Account Control" blocks SpywareBlaster AutoUpdate from running at startup. My Vista user name is running in "Administrator" mode. It is the only item in my startup folder (in msconfig) that shows "Unknown" in the "Manufacturer" column. Also, in Windows Defender, in the Software Explorer, it is the only item that shows "Publisher Not Available". During each boot, I get an icon in the system tray by the clock that states "Blocked startup programs" when I point my mouse pointer at it. When right clicking on the icon, it allows me to select "Run blocked program". However, I need to selectively do this after each and every boot or reboot or else the startup item won't run (as shown in the following Vista help file, it states I need to repeat these certain steps each time I want to run the program after starting Windows): Run or remove blocked startup programs User Account Control prevents programs that require permission or an administrator password from running automatically when Windows starts. If a program is blocked, you'll see a message in the notification area that says some startup programs need permission to run. You can run a blocked program, remove blocked programs from startup, or ignore the notification. To run a blocked program Right-click the Blocked startup programs icon in the notification area. Click Run blocked program, and then click the name of the program you want to run. If you are prompted for an administrator password or confirmation, type the password or provide confirmation. Note You'll need to repeat these steps each time you want to run the program after starting Windows. I have been spending a better part of the last 5 hours doing internet searches, help file searches, etc, trying to find a fix (to no avail). It seems this new User Account Control (UAC) does not have an "approved list" or such to override the fact that it is blocking SpywareBlaster AutoUpdate from running at startup. I am a regular user of this AutoUpdate feature for a number of years now for various Windows XP computers that are under my control... However, I am stumped regarding this issue on my lone Vista machine. 1) Is Javacool aware of this issue? 2) Will there be a fix in the upcoming version? Thank you.