Per user update problems with 7.6.1 (XP and Win 7)

[docswab]

The 7.6.1 update did fix the per-user installation problems previously reported for the first time installation. Thanks!

Unfortunately there are still some issues when using Updater.exe to update per-user installations:

XP SP3 Per-User
(Installation, updates, and removal function as expected for Per-machine installation with the exception of AutoClose)
-The first installation puts the files in C:\Documents and Settings\[user]\Local Settings\Application Data\Programs.
-The update content is downloaded to C:\Documents and Settings\[user]\Application Data.
-The AutoCloseApplication argument does not work and you still have to manually quit the running application being updated before you can finish the update installation. (The same thing happens with per-machine installations as well.)
-The update installation then properly replaces all of the files and launches the updated application properly.
-BUT the updater still reports an error, "Some of the updates failed to install properly."
-AND Checking for Updates again tries to offer the same update, even though the registered version is the updated version.
-AND the updates folder in [user]\Application Data is not fully removed by either the updater or the uninstaller.

Windows 7 Per-User
- The first installation succeeds to C:\Users\[user]\AppData\Local\Programs
- The update installation begins properly and succeeds in removing all of the previous version files from the folder named above.
- The update installation begins to copy the new files into place. Some files and folders are properly copied.
- BUT then it fails, saying that there are not enough privileges for C:\Program Files.
- AND the updater reports, correctly, that Some of the updates failed to install properly.
- The installer then removes all of the copied files, leaving NO application in place.
- AND installing the update MSI manually on top of the original version creates the same failure as using updater.exe above.

- Installing the update MSI manually when the original version is not present works as expected.
- HOWEVER, checking for updates after manually installing the update MSI shows an update available instead of showing the software up to date as expected.
- Attempting to run the update shows the Modify/Repair/Remove dialog.
- Choosing "Repair" runs the installer again, but generates a Some updates were not installed error. Launching the software again still shows an available update.

[Cosmin]

Hi,

The AutoCloseApplication argument does not work and you still have to manually quit the running application being updated before you can finish the update installation.

Can you please give me more details about this? What argument are you using?

BUT the updater still reports an error, "Some of the updates failed to install properly."

Any update defined in the Updates Configuration file uses a detection criteria. This criteria is usually a file or a registry entry which contains the package version. If it's not met after the update is installed, the Updater will show this message. Therefore, you need to make sure that you specified a correct file or registry entry in the Installed Detection section of the Update Properties page.

AND the updates folder in [user]\Application Data is not fully removed by either the updater or the uninstaller.

The updates download folder should be removed during uninstall. If the problem persists, can you please send us the .AIP (project) file you are using to support at advancedinstaller dot com so we can investigate it?

BUT then it fails, saying that there are not enough privileges for C:\Program Files.

Installing the update MSI manually when the original version is not present works as expected.

Does the original version have files in the Program Files folder? If so, is the original version installed per-user or per-machine? Can you please send us the .AIP (project) files of the two versions so we can investigate them?

Regards,
Cosmin

[fingertapps]

I had this exact same problem. After going through what i'd changed, i figured out at some point I'd set the Update Version reg keys to be a 64-bit component.

Unchecking the 64-bit component box allowed the update to install successfully again. This may not be the same problem (although it has similar symptoms), as it would only have been a problem on 64-bit machines.

Maybe advanced updater should check both the 32 and 64-bit registries?

Regards,
Nick