Vista custom action

INFO: Resolving reference for culture en. INFO: Did not find manifest for culture en. End Activation Context Generation. Fortunately, I was able to resolve this after discussing with a friend and searching for required run times. Did you ever get to the bottom of that, or was it not really a problem for you? Ask a question. Quick access. Search related threads. While the error is up I am able to access the EXE in the expected location and can run it manually, though it also gets the same UAC prompt as above.

The EXE has an embedded application manifest that specifies the requested execution level as requireAdministrator.

Any help resolving these issues would be greatly appreciated. Tags: None. Make sure that the Impersonate option is turned off in the custom action and that it is being run deferred.

Comment Post Cancel. Impersonate option is turned off and the Scheduling option is set to Deferred. I have an install that includes a custom action that calls "an executable from installed files". All custom action must use the "asInvoker" option, not "requireAdministrator" or "highestAvailable" Broadcom Employee. Migration User. Posted Mar 05, AM. Reply Reply Privately Options Dropdown. This executable creates a scheduled task on Windows Vista.

If I run the executable from the command line, the task is created like it should be. However, when the executable runs from the installer, it fails with a return code of LogonType which means that the executable did not run with sufficient privileges to create the task. I've tried adding a manifest it's a. I have made sure that the custom action is after all the files have been installed insuring that both the executable and manifest are in place and I have made sure that the "Enable User Account Control" checkbox is checked in the Installation Expert.

When the installation starts, it prompts for the UAC approval, and I can tell that my custom action fires and the executable runs, but if run under the installer, it fails with an Exception LogonType.

It works if I run it form the command line after the install. You could also put a manifest file in the same location as the executable, with the same name as the executable with.

For example, a manifest for setup. Either way, example content of that manifest follows:. Of course, in Vista setup. A transform could also be used to change the Attributes for a custom action when installing the product.