
How can I find out what file already exists and is causing this error? If the user manually launches the new installer, then it works, so it must be something that happens when updater.exe is running.

We are unable to replicate the behaviour on our end. Can you please tell us if you can replicate the behaviour on multiple machines? If not, most likely is something specific for the related machine.I am trying to troubleshoot an upgrade problem on one computer.
We are only seeing this behavior on one machine and I still need help identifying which file or files on that machine are causing the problem. Can a debug build of updater.exe be provided that would provide more information?Dan wrote: We are unable to replicate the behaviour on our end. Can you please tell us if you can replicate the behaviour on multiple machines? If not, most likely is something specific for the related machine.
Dan
FOLLOW US
Get the latest news in Application Packaging