The following possible errors occur when verifying a signed VBA project:
Error: "The publisher has not been authenticated and therefore could be imitated. Do not trust these credentials."
Error: "Windows does not have enough information to verify this certificate"
The Microsoft Office and the code signing certificate were picked up on one machine then exported and imported to a second machine and when the export was done, the Intermediate CA certificate was not included. The export function creates a .pfx file. If this .pfx file does not include the Thawte Code Signing CA chaining certificates, all files signed on the second machine will have a malformed digital signature that will not be able to be verified.
Using the proper export process will allow developers to correctly sign VBA projects from machines other than the one used to do the original enrollment and pick up of the Microsoft Office and VBA Code Signing certificate
Perform the following steps to export the Microsoft Office and VBA Code Signing certificate: