Five reasons for using AutoUpdate+:
1) Admin account not required!
It is difficult to ensure that Windows XP computers get updated. Not all users run with
an administrator account. It's even more difficult to update Vista PCs, as users
by default run with low permissions.
How can we help? AutoUpdate+ runs a background service that will securely update application
files without the requirement that your users have administrator privileges.
2) Complete flexibility and control
All update behaviors are defined remotely. We offer features such as silent updates, messages that are defined per update, ability to update the registry and execute supporting files and a script that is human readable and easy to integrate with your backend server logic.
3) Flexible delivery mechanism
You can use either an http, https, ftp or file server for your updates. Backup servers are also supported.
4) No expertise needed
AutoUpdate+ does not require any user scripting, unusual installation steps or bundling with large framework packages (such as .NET). The product works right out of the box.
5) Excellent support services
We are looking forward to deploying AutoUpdate+ with your product. To assist, we offer a support capability which is second-to-none.
Updates on Vista
Below is a list of 5 common Vista problems that update packages encounter. Each problem will either generate security warnings or force your app to launch only with admin credentials:
Access permissions:
The Program Files directory and HKLM are strictly off-limits and require privilege elevation to modify.
Detection heuristics:
Various heuristics, such the import table of your executable, are used by Vista to know if to launch your app under admin credentials. This can cause problems if the update check is built into your app.
Keywords in use:
Files with the words setup, install or update will require admin credentials to run. Be careful not to use the word update anywhere in the file name or properties, or your app will trigger Vista security warnings.
File APIs:
Programmers can still use the standard file manipulation APIs, but be careful... permission failures may not be detected due to File Virtualization automatically redirecting you to a per-user copy of the file.
Service interaction:
The 'allow service to interact with desktop' option is no longer acceptable. If you have written an Update Service, it must not have any user interaction that requires a GUI.

Home
Download
Purchase