I had that same trouble and it caused me lots of head scratching. Then I found out that our certificate had expired and been renewed to a new certificate instead of renewing the 'same one' by Verisign, so I just needed the new certificate. Make sure your certificate is still valid (check date).

acess violation at address 72c15a60 in module uxtheme.dll read of address 00000002.

while opening the 'define interactive characteristics' dialong on the finished form of my project.

V10.

I think if you build against the newer COM dll all will suddenly get fixed

UI seems unstable, though at least all is working. Various bar colors sometimes change for no reason, scrollbars seem mis-aligned, bounding boxes disappear, etc. This is all over the app, I've attached some screen captures. Normally if the UI gets too confused I have to close/reopen. This is 9R2, UI...

Found it, I think it's it's a certificate problem. Our certificate coincidentally just expired!

Is it possible to get the list of commands and order you use for signcode maybe you or I could write a very small wrapper around those specific commands into a dummy signcode.exe file that will call signtool and see if that will work better?

I have attached a "process monitor" log file for doing a fairly simple install with an authenticode signing, this doesn't have any merge modules so it's pretty straight forward and shows the error. Keys files are on correct/current paths. I wonder if we replaced signcode.exe from the IA di...

Uninstall IA, ran the msizap, reinstalled IA, same problem. When I run it all works unless I try to install via authenticode. I have the same files I was using on Vista x64 (same PC) to do this, this is a Verisign code-signing certificate. This is time sensitive so if you have any ideas for a work-a...

Should I try to uninstall IA, then run msizap then re-install? The msizap says products you use it on may fail to work after that... ORCA install is what messes up IA, not 'use' but I can't use it if it's not installed, so I don't want to install it on my Dev Machine. What I did was to install (last...

Thanks but if I run ORCA it will break InstallAware, causing me to have to uninstall and reinstall to get it even somewhat working again, I've verified that twice now, and I don't have that kind of extra time today or the rest of this week. I would like to resolve the Authenticode issue first then m...

If you go above the directories you want to copy and do a *.* you can set it to get all subdirectories and it will recurse.
I've been using a single uncompressed folder mostly but the path variable you are looking for for the CD's root is I believe
$SFXPATH$

FYI my question on version came from reading one of the support responses "Re: Build problems with IA9 on Windows 7 64bit by MichaelNesmith » Fri Jun 11, 2010 10:32 am Make sure you are on 9.08 or 9.09.Michael Nesmith InstallAware Home of The Next Generation MSI Installer Get your free copy tod...

FYI my solution to this, whose root cause I don't know but maybe is a result of some sort of update of an MS component that causes some 'over-registration' is that if I fully uninstall and reinstall IA, the problem is fixed for 'a while'. Installing Orca definitely breaks it, uninstalling Orca somet...

I'm creating a new thread for this. I have existing projects that were working fine with authenticode. I updated my development machine (in place) from Vista x64 to Win7 x64, nothing else has changed, though I did also update the HDD (imaged the drive onto a larger HDD). All the same certificate fil...

Reinstalled, got past the merge module issue but having problems with the authenticode signing now. I believe the updating to Win7 is the key to all the issues I'm seeing in some way. I have installed the certificate on my local machine again. I also see some graphics/ui problems with the bar on the...