Sage 100

Error 1330. A file that is required cannot be installed because the cabinet file ..... has an invalid digital signature I have a client getting this error when trying to install Sage 100 Premium we have downloaded the files 4 times from sage's website and I sent them the installation files via FTP at first I thought it was a corrupted download but now I'm convinces that is not it Anyone have any thoughts on what this error could mean? I've never seen this error or anything like it.

https://www.evernote.com/shard/s270/sh/843b1d7c-f7cb-4179-bad2-e281cd36676c/4c738e5a91af1a00f2e834ca4597314d

Error 1330. A file that is required cannot be installed because the cabinet file C:\Program Files\Sage 100 ERP\...\Data1.cab has an invalid digital signature. This may indicate that the cabinet file is corrupt. Error 266 was returned by WinVerify Trust"" when trying to install 1. \ Solution The Root Certificates on the PC may not be the latest ones from Microsoft. Please download and run the Root Certificate Updater from Microsoft. It can be found at this link (check to see if there is a more recent version): http://www.microsoft.com/download/en/details.aspx?id=6149 Setup required internet access. Without internet access (or a restrictive firewall or proxy), setup may fail to verify the signature because it cannot access the online certificate revocation list (CRL). Some brief information on the root certificates: This item updates the list of root certificates on your computer to the list that is accepted by Microsoft as part of the Microsoft Root Certificate Program. If you want the details about Root Certificates, then try this link: http://technet.microsoft.com/en-us/library/cc751157.aspx

Thank you Wayne! - I'll let everyone know if that works

Thanks @WayneSchulz Apparently that worked! because they are now asking me what the message about ""you must use a valid UNC path to the source file"" means. this is a client that is doing their own upgrade (sigh).

Give them the Sage support line.....

Actually they spent 3 hours with Sage support Thursday night and the conversation ended with Sage telling them it was an operating system problem. Which technically is true.

Just wait until they get to the FRX upgrade