Authenticode No longer working

[dunion]

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 files, same paths, same exact project, but now the authenticode signing always fails. I had to re-install IA to get merge modules working again; I've had this problem after MS updates sometimes as well but that is straight forward.

Can you think of anything I can do to try to get the authenticode working? Just in case I re-added these certificates locally to the trusted root certificate store (rather than any default path, but I've tried that also), that didn't make any difference.

And of course we need to get two installs out this week

My only backup plan would be to create some sort of virtual machine with an older OS and build it on that but it seems like others are not having this problem with Win7 x64?

Thanks.

[mills]

I see here that *running* Orca causes issues? That's particularly strange. You definitely hosed something!

You might want to try msizap to clear up the IA install...
http://msdn.microsoft.com/en-us/library ... 85%29.aspx

Here's the IA product code:
{1AFF3E5C-E67C-4D36-8478-8C36491440C2}

[dunion]

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 time I ran into this problem, so it's probably a version from at least the prior Visual Studio version install) it into a VM and only run it inside the Virtual Machine to modify merge modules that need to be modified.

[dunion]

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-around please let me know.

Note if it matters for COM component registrations (I don't think so) I have VS 2010 installed on this PC.

Thanks.

[dunion]

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 directory, dated 2004, with a 'newer one', if it would work any better?

[dunion]

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?

[dunion]

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

[mills]