You are missing Impersonate="no" in your CustomAction element. On Vista, the
action runs impersonating the installing user, who (with UAC turned on) does
not have write permission under Program Files, since it is the user before the
elevation prompt.
If you set Impersonate="no", then the custom
Does it fail even if you run your setup elevated? If you’re able to run your
MSI non-elevated, it’s probably using the compatibility features to write to a
mirror program files directory under the user profile, not the real one. If
you run your msi, does Windows ask if you want to elevate? If
2 matches
Mail list logo
