This project has moved. For the latest updates, please go here.

Invalid code signing certificate

Feb 2, 2011 at 2:11 AM

The Beta 2 had this problem, and it looks like v1.0 still has it: it is signed by a self-signed certificate which is untrusted.

I am running 64-bits Word 2010 on Windows 7, and am unable to use it (B2 and v1.0) because the add-in is signed by "CN=EUROPE\i-thaug" (expires on 04/21/2010).

Anyway to have this signed by a public CA so that we can use it out-of-the-box (e.g. without mocking around with the Windows Certificate Stores)?


Feb 2, 2011 at 5:11 PM


We are looking into your issue. We will keep you posted on the updates.

Support Team 

Mar 1, 2011 at 1:33 PM


Thanks for your patience. We are on this with our development team on the highest priority. We will get back to you with more updates on this.

In the meanwhile, please let us know if you have any other concern/issue.

Support Team

Mar 2, 2011 at 4:00 AM

If this helps: it would appear that the 64-bits Word 2010 is invalidating the x509 digital certificate signature present in the "chem4word.addin.vsto" file under the <PublisherIdentity> tag.