Hi Cosmin,
Thanks for the reply.
I tried "Deferred with no impersonation" but it didn't help.
However when I created a simple test installation, the execution of the exe custom action succeeded.
After reducing and converting my original installation step by step to the simple test installation, I found out that I have to change the location of the temporary exe file that is executed in the custom action. In my original non-working installation the file was located in the application directory (under program files). After moving the file to windows temporary folder the execution of the custom action worked in "no impersonation" mode worked.
Unfortunatly, after all the work I've done I discovered that I can't run the custom action without impersonation, since the executable that runs in the action should sometimes read and write files located on protected network folders for which the user running the installation has permissions, but the SYSTEM user doesn't.
So I'm back to my original question.
I am trying to run a 'console application' exe file in a commit custom action. Everything works OK when UAC is disabled, and fails with error code 1720 when UAC is enabled.
I tried to rebuild the application that is performed in the custom action.
At some time it turned out that removing the resources file (*.rc) from the custom application project, makes a different, and the test installation that was created in that stage ran OK. Unfortunately, for my original and full application it didn't help.
I there anything else I can do to make the custom action work?
Are there any special guidelines for creating the custom application so it can run under VISTA with UAC?
Thanks in advance,
I really need the help.
Israel Sadeh
FOLLOW US
Get the latest news in Application Packaging