Intel® Studio products and Intel® XDK Installation failure 'Package signature verification failed.'

Installation of Intel® Parallel Studio XE, Intel® System Studio, Intel® INDE, or  Intel® XDK may fail with a message from the installer 'Package signature verification failed.'  There are two specific causes of this failure.  The most likely cause is that valid trusted root certificates cannot be found on the system.  These are needed by the installer to verify the package is good.  A secondary cause is that the installation package is corrupted, or that the package has an invalid signature or timestamp.

If valid trusted root certificates cannot be found on the system, the reasons may include:

  • The system either does not have access to the Internet, or if it does, Windows Update cannot acquire the needed certificates.  In either case, the needed certificates will need to be downloaded and installed separately.  Two certificates are needed; one to verify the digital signature, and another to verify the timestamp. 
    • The 'AddTrust External CA Root' certificate is needed to verify the digital signature and may be obtained here.
    • The 'QuoVadis Root Certification Authority' certificate is needed to verify the timestamp and may be obtained here.
  • The operating system is not a supported version.  For example, Microsoft* Windows 7* is the oldest version supported for installation of  Intel® Parallel Studio XE 2016; older versions of the OS may not have valid certificates, or the OS may not support valid certificates.  For a complete listing of supported operating systems, see the Intel® C++ Compiler 16.0 Update 1 for Windows* Release Notes (all components of Intel® Parallel Studio XE 2016 have the same OS requirements).
  • For the operating system requirements of  Intel® System Studio, Intel® INDE, or  Intel® XDK, see the Release Notes for those products.

If the installation package is corrupted, or the package has an invalid signature or timestamp, then it may have been corrupted during a download, or perhaps been tampered with or corrupted by a virus.  The solution is to obtain a fresh copy of the package and attempt the install again.

 

For more complete information about compiler optimizations, see our Optimization Notice.