>>A better idea would be to put a Setup Wizard runtime install out on the network and use the same approach (a runonce key) to actually run the Setup Wizard installation; this ensures that files are copiued into place properly and registry entries are updated, etc.
>
>Ed,
>
>Unfortunately our client's only have power user login authorization. If the update of runtimes require any registration then I'm sunk. Using the Setup Wizard approach would require admin login.

Well, then you've got major problems IAC, because any new or revised OLE-enabled component is going to really require registration (many updates to controls will actually use the same VersionIndependent ProgID, but will put a new ProgID in place, may have a new identity if the interface changes, and obviously any new component will need to register, too.

You can hack the SETUP.STF to remove the check for admin privileges under NT, and use a command line switch (/G filename) to have a detailed log file created, which your app or launcher could read to deterine if things ran OK.