Hi
I am seeing very odd behaviour when updating an installation on Windows 7. It is due to UAC being present and active on the system - and have witnessed it happening on more than 1 machine.
My installation consists of a small amount of files being installed to the Program Files folder in a default folder or folder selectable by the user. Part of the installation is to edit an application configuration file to add dynamic info using the "XML File functionality" of Advanced Installer. The installer works incrementally so each version can update the last using "uninstall old version first and then install new version" functionality.
The behaviour I am seeing is that a previous version of the config had a setting which switched off some functionality until it was ready for the user to try. The latest version changed this setting in the config file from 'off' to 'on'.
<add key="funcswitch" value="on" />
When I visually inspect the file in notepad it shows the value as being 'on' - but the application acts like it is 'off' and the WINGREP application detects the setting in the config as being 'off' too. Even if I uninstall the application from the machine, delete the files and reinstall I get the same effect and wingrep showing the setting as 'off'.
If I switch off UAC everything installs and works as expected.
My theory is that as the earlier install sets did not have "Run as administrator" set on the Install Parameters page so didnt get installed with elevated permissions.
Has anyone else seen these effects, and is there any way around them, other than to ask the user to switch off UAC (which they dont want to do) or install to a non-UAC protected directory? Is there any way to 'clear' the old config the system is appearing to hold on to.
Best Regards
Buzz