SST Setup Launcher Icon Setup Launcher Version 1.2
Help & User Guide
Warnings and Errors
This topic provides rudimentary support to users encountering warnings and/or errors while performing an installation or one of the other supported tasks (e.g. the download or extraction of a .msi file).


Error Codes
An error code is a numerical value assigned to a particular type of software error. They are returned by internal functions of the operating system (i.e. Windows) and (other) software applications to indicate that further execution of the computer program as originally intended by the software developer is no longer possible. This may require the program to fall back on alternative procedures, interact with the user on how to proceed, or terminate without having fulfilled its purpose.
Error codes displayed to users are commonly supplemented by a user friendly text, briefly explaining the nature of the error.

Security Warnings and Exit Codes
Although from a purely technical standpoint, both security warnings and exit codes are error codes, they (may) differ in significance from the user's perspective. Because errors that occur during the security check may have been directly or indirectly caused by concious user actions or third party software, such as the configuration of security settings, they cannot invariably be attributed to a security threat. Furthermore, they do not necessarily prevent a successful installation of the software. However, they are an indication for a potential threat to your system's security and therefore should not be ignored without due consideration.
Exit codes, on the other hand, are the result of an error in the overall installation process and give the reason for the failure. Which is why the SST Setup Launcher differentiates between the two.
As no confirmation of a successful installation is displayed by the SST Setup Launcher, it is highly recommended that the causes of both securtity warnings and exit codes be determined in the event that either is displayed. The tables below provide starting points for such a quest.

Security Related Technical Terms
Digital signature, digital certificate, message digest/hash, public and private key, certificate authority/trust center, are all linked, abstract, as well as implemented, concepts of computer security technology that cannot be explained within the limited scope of this overview of the SST Setup Launcher. Unfortunately, to keep the warning and error messages concise and meaningful to administrators, software developers, and experienced users, their use cannot be avoided.
Furthermore, as these terms touch vital aspects of system and data security, and are recurrent throughout the documentation on security related issues, we recommend to familiarize yourself with them prior to ignoring a security warning or repeating an installation that terminated with an error.
A brief explanation of the terms and an introduction to the subject matter is generally available in the offline documentation of operating systems, Internet browsers, and e-mail clients. For a more thorough discussion of the underlying concepts please refer to the documnets and Internet links listed under under Appendix B, Suggested Reading and Reference.

Finding Error Information
To quickly locate an error enter either the decimal or hexadecimal error code in the field below and click (on) the "Find Error" button. However, the error code should always be entered in ungrouped digits. That is without spaces as in "1 234 567", commas as in "1,234,567" (U.S. notation), or periods as in "1.234.567" (European notation);.
For example: To find the row treating the security warning "Warning ! The file ExampleFileName.msi does not bear a digital signature.", you should enter "-2146762496" instead of "-2,146,762,496" or "-2.146.762.496", or "0x800B0100" instead of "0x800B 0100". Of course, also without any quotation marks, parentheses, etc.. One method to achieve this is, is to select and copy the error code from the SST Setup Launcher dialog and pasting it in the "Error code" field on this page.
Error code:      Limit search to: All warnings and errors Security warnings Exit codes

Table 1: Security Warnings
Error Code
(Hexadecimal value in parentheses) 		Warning Text Possible Causes Possible Consequences
of Ignoring the Warning 		Possible Solution(s)
50
(0x0000 0032)
ERROR_NOT_SUPPORTED 		Warning ! Loading WinTrust.dll and/or Crypt32.dll failed. One or more software components required to verify the digital signature/certificate cannot be accessed by the SST Setup Launcher as a result of
1.  your system not meeting the requirements to execute the SST Setup Launcher
2.  inadequate access rights to one or both files,
3.  system corruption.
The digital signature/certificate on the installation package files cannot be verified. The SST Setup Launcher will be unable to determine the integrity of the files and the trustworthiness of the digital signature/certificate and display security warnings.
1.  Verify the existence of the two files on your system.
2.  Verify that the location of the two files is listed in the "PATH" environment variable.
3.  Verify that the SST Setup Launcher has the right to access the two files.
4.  Update your system if necessary and possible.
111
(0x0000 006F)
ERROR_BUFFER_OVERFLOW 		A string parameter that exceeds the max. permissible length was passed to a security function while verifying the signature of "File".
1.  Relevant parts of the installation package are located in a folder which results in the path, file name, and file extension exceeding 259 characters in length. Note that all blanks/spaces, hyphens, commas, and periods, etc. are also considered characters.
2.  Authoring error on the part of the publisher.
3.  Intentional or unintentional corruption of the SST Setup Launcher executable or the *.msi or *.msp Microsoft Installer file(s).
This is a fatal error that cannot be ignored.
1.  Move the entire installation package up in the folder hierarchy, so that all components of the installation package have a path (including the drive letter, file name, file extension, etc.) of not more than 259 characters in length.
2.  Shorten one or more folder names in the folder hierarchy to the root of the installation package, so that all components of the installation package have a path (including the drive letter, file name, file extension, etc.) of not more than 259 characters length.
3.  Inform the publisher.
120
(0x0000 0078)
ERROR_CALL_NOT_IMPLEMENTED 		Warning ! A function necessary to verify the existence or validity of a digital signature cannot be accessed.
1.  Not all functions necessary to verify the digital signature/certificate are implemented in the versions of Wintrust.dll and/or Crypt32.dll that are installed on your system.
2.  The files Wintrust.dll and/or Crypt32.dll have been corrupted.
Verification of the digital signature/certificate and/or the integrity of the installation package may not be possible or return erroneous results. Update, repair, or reinstall Microsoft Internet Explorer and/or the entire operating system.
-2,146,885,594
(0x8009 2026)
CRYPT_E_SECURITY_SETTINGS 		Warning ! Although the digital signature is valid, the cryptographic hash that represents the subject or the publisher is not trusted by the administrator and the present security policy does not permit explicit trust by users.
The digital signature/certificate is not trusted as part of your system's security policy and users are explicitly denied the privileges necessary to alter the list of trusted signatures/certificates.
1.  The installation will probably fail.
2.  Executing the installed software may fail.
1.  Perform the installation with elevated (i.e. administrator) privileges.
2.  Ask the administrator of your system to verify the installation package's files' digital signature/certificate and add the certificate to the list of trusted certificates. The installation should subsequently also be possible with user privileges.
3.  Permit users to explicitly trust and install the certificate(s) on the installation package's file(s).
-2,146,869,232
(0x8009 6010)
TRUST_E_BAD_DIGEST 		Warning ! The verification hash is not identical to the hash stored in the signature of file "File". This indicates that the file has been corrupted during download or storage, intentionally modified, or in some other manner tampered with. We recommend to immediately abort the installation and notify the publisher of this occurrence.
1.  The file was intentionally modified after having been digitally signed.
2.  The file was corrupted during download or during transfer from one storage medium to another.
1.  If the installation package was intentionally modified, a virus or other malicious software may be installed on your system.
2.  If the file was unintentionally corrupted during download or transfer, the installation may fail or the installed software may be faulty.
Abort the installation immediately and inform the signer and/or publisher of the error and quarantine or remove all files belonging to the installation package from your system.
-2,146,762,751)
(0x800B 0001)
TRUST_E_PROVIDER_UNKNOWN 		Warning ! The verification of the digital signature on file "File" requires a trust provider that is not recognized or installed on your system. In the interest of your system security we recommend resolving the problem prior to continuing with the installation.
1.  The necessary security software is not installed or activated (e.g. a service is not running or other configuration settings are preventing the execution of the necessary security software).
2.  Your system does not fulfill the requirements to run the SST Setup Launcher.
1.  Verification of the digital signature/certificate and/or the integrity of the installation package will not be possible.
2.  The installation may fail.
Verify the correct installation and configuration of the security software on your system and repair/reinstall or update the security software if necessary.
-2,146,762,748
(0x800B 0004)
TRUST_E_SUBJECT_NOT_TRUSTED 		Warning ! The digital signature on the file "File" is currently not considered trustworthy by the trust provider. In the interest of your system security we recommend clarifying the issue prior to continuing with the installation. The trust provider installed on the system under which the verification of the digital signature/certificate was executed does not discern more distinctly between the causes for the failure. The consequences of ignoring this warning are unpredictable. They can range from having to no effect at all to damaging, and even rendering the system inoperable.  
-2,146,762,496
(0x800B 0100)
TRUST_E_NOSIGNATURE 		Warning ! The file "File" does not bear a digital signature.
1.  The file was not signed by the publisher.
2.  The file was unintentionally corrupted during download or during transfer from one storage medium to another.
3.  The digital signature was intentionally removed.
1.  The origin of the installation package or the software to be installed cannot be determined with certainty.
2.  The SST Setup Launcher will not be able to verify the integrity of the installation package.
3.  If the installation package was intentionally modified, a virus or other malicious software may be installed on your system.
1.  Contact the publisher and get a signed version of the installation package.
2.  If you are certain that you can trust the source of the installation package, you can ignore the warning.
-2,146,762,487
(0x800B 0109)
CERT_E_UNTRUSTEDROOT 		Warning ! The certificate chain of the digital signature on the file "File" was successfully processed, but terminated in a root certificate that is not trusted by the trust provider.
1.  The issuer of the root certificate has not been certified by Microsoft.
2.  The digital certificate on the file is a self signed certificate (that is a certificate issued by the publisher/signer of the file).
1.  The installation may fail.
2.  Executing the installed software may fail.
Decide whether you want to trust the publisher and/or the source of the file or not. If you decide to trust the signer and/or issuer of the root certificate, install the certificate by adding it to the list of trusted root certificates or simply ignore the warning.
-2,146,762,479
(0x800B 0111)
TRUST_E_EXPLICIT_DISTRUST 		Warning ! The file "File" bears a valid digital signature that has been explicitly designated as not trustworthy. In the interest of your system's security we recommend to abort the installation and determine the reason for the explicit distrust.
1.  The digital certificate was added to the list of certificates that should not be trusted.
2.  The root certificate or another certificate in the certificate chain/hierarchy is listed in the list of certificates that should not be trusted.
1.  The installation may fail.
2.  Executing the installed software may fail.
Determine the reason for the explicit distrust and decide whether you want to trust the source of the file or not. If you decide to trust the signer/publisher you can
1.  remove the digital certificate from the list of explicitly distrusted certificates and add it to the list of trusted certificates.
2.  consider revising your system's certificate management configuration/policy.
3.  simply ignore the warning.




Table 2: Exit Codes
Error Code
(Hexadecimal value in parentheses) 		Error Text Possible Causes Possible Solution(s)
2
(0x0000 0002)
ERROR_FILE_NOT_FOUND 		Setup was unable to find the file to be verified as entered on the command line. You requested the SST Setup Launcher to verify the digital signature on a file that could not be found as the result of
1.  entering the incorrect path to the file and/or name of the file on the command line (i.e. a simple typing error).
2.  an unexpected network or media error, such as the inadvertent removal of a disk.
Ascertain whether the network drive/resource or storage medium (e.g. hard disk, CD, DVD) the file to verify is located on is available and check your spelling.
6
(0x0000 0006)
ERROR_INVALID_HANDLE 		A system function returned an invalid handle. Verify that your system meets the requirements to run this installation, update your system if necessary, and check your security settings.
1.  A self-extracting installation package is being run from a storage device/medium to which it does not have read and write access (e.g. a CD or DVD).
2.  Security policy or third party security software may be preventing read/write access to the disk the installation is being run from or a system file.
3.  Incomplete or corrupted installation package.
4.  The operating system does not fulfill the requirements to execute the SST Setup Launcher.
5.  The operating system has been corrupted.
1.  Copy or move the installation package to a hard disk to which the SST Setup Launcher has read and write access.
2.  Verify that system security policy and/or third party security software is not preventing read and write access to the drive and folders in which the setup package's files are located, and that the SST Setup Launcher has at least read access to the Windows and other system folders.
3.  Contact the publisher and get a signed, intact installation package.
4.  Update, repair or reinstall your operating system.
14
(0x0000 000E)
ERROR_OUTOFMEMORY 		The operating system was unable to provide this program with the memory necessary to complete an operation. Reduce the system's memory load by closing all other applications or rebooting the system and try running this program again.
1.  Too many other processes are currently being executed on your system.
2.  Terminated processes have not freed the memory they were allocated by the operating system.
3.  Your system is not equipped with adequate physical memory for your requirements.
Reduce memory usage by closing other applications and/or restart your system.
87
(0x0000 0057)
ERROR_INVALID_PARAMETER 		An invalid parameter was passed to an internal or system function. This can be the result of an internal or an authoring error. Please inform the publisher.
1.  Authoring error on the part of the publisher.
2.  Intentional or unintentional corruption of the SST Setup Launcher executable.
Inform the publisher of the error and get a signed, intact installation package.
120
(0x0000 0078)
ERROR_CALL_NOT_IMPLEMENTED 		A function necessary to execute this program is not supported by the system or cannot be accessed. Verify that your system meets the requirements to run this installation, update your system if necessary, and check your security settings.
1.  The operating system does not fulfill the requirements to execute the SST Setup Launcher
2.  Corrupted or compromised operating system.
1.  Verify that your operating system fulfills the criteria to execute the SST Setup Launcher and update your system if necessary.
2.  Try using an alternative method to install the software.
3.  Reinstall your operating system.
122
(0x0000 007A)
ERROR_INSUFFICIENT_BUFFER 		An internal function did not provide the necessary memory to another internal or system function to complete the operation. This can be the result of an internal or an authoring error. Please inform the publisher.
1.  Authoring error on the part of the publisher.
2.  Intentional or unintentional corruption of the SST Setup Launcher executable.
Inform the publisher of the error and get a signed, intact installation package.
160
0x0000 00A0)
ERROR_BAD_ARGUMENTS 		This package does not support the specified command line switch. A command line parameter requesting an action that is not supported by the particular installation package was passed to the SST Setup Launcher. For example: This error is returned if you specify the command line switch to download the Microsoft Installer package ("/d") on the command line of a self-extracting installation package. Omit the offending command line switch. In version 1.0.0.0 of the SST Setup Launcher this can only be "/d" or "/e".
161
(0x0000 00A1)
ERROR_BAD_PATHNAME 		An internal or system function either specified or returned an invalid path, or formed a path that execeeds tha max. permissible length.
1.  Relevant parts of the installation package are located in a folder which results in the path, file name, and file extension exceeding 259 characters in length. Note that all blanks/spaces, hyphens, commas, and periods, etc. are also considered characters.
2.  Authoring error on the part of the publisher.
3.  Intentional or unintentional corruption of the SST Setup Launcher executable.
1.  Move the entire installation package up in the folder hierarchy, so that all components of the installation package have a path (including the drive letter, file name, file extension, etc.) of not more than 259 characters in length.
2.  Shorten one or more folder names in the folder hierarchy to the root of the installation package, so that all components of the installation package have a path (including the drive letter, file name, file extension, etc.) of not more than 259 characters length.
3.  Inform the publisher of the error and get a signed, intact installation package.
1620
(0x0000 0654)
ERROR_INSTALL_PACKAGE_INVALID 		Either an internal or external component of the installation\npackage cannot be found or accessed. This error is normally the result of an incomplete or corrupted package. Please inform the publisher.
1.  Missing or inaccessible installation component. For example; a missing .msi or .msp file.
2.  Authoring error on the part of the publisher.
3.  Intentional or unintentional corruption of the SST Setup Launcher executable.
Contact the publisher and get a signed, intact installation package.
1639
(0x0000 0667)
ERROR_INVALID_COMMAND_LINE 		An invalid installation properties command line was authored into the package. Please inform the publisher.
1.  Authoring error on the part of the publisher.
2.  Intentional or unintentional corruption of the SST Setup Launcher executable.
Inform the publisher of the error and get a signed, intact installation package.
1813
(0x0000 0715)
ERROR_RESOURCE_TYPE_NOT_FOUND 		An internal resource of the specified type cannot be found in the SST Setup Launcher executable. This error may have been caused by a corrupted or compromised executable. Please inform the publisher.
1.  Authoring error on the part of the publisher.
2.  Intentional or unintentional corruption of the SST Setup Launcher executable.
Inform the publisher of the error and get a signed, intact installation package.
1814
(0x0000 0716)
ERROR_RESOURCE_NAME_NOT_FOUND 		An internal resource with the specified name cannot be found in the SST Setup Launcher executable. This error may have been caused by a corrupted or compromised executable. Please inform the publisher.
1.  Authoring error on the part of the publisher.
2.  Intentional or unintentional corruption of the SST Setup Launcher executable.
Inform the publisher of the error and get a signed, intact installation package.
1815
(0x0000 0717)
ERROR_RESOURCE_LANG_NOT_FOUND 		An internal resource with the specified language ID cannot be found in the SST Setup Launcher executable. This error may have been caused by a corrupted or compromised executable. Please inform the publisher.
1.  Authoring error on the part of the publisher.
2.  Intentional or unintentional corruption of the SST Setup Launcher executable.
Inform the publisher of the error and get a signed, intact installation package.
-2,146,697,211
(0x800C 0005)
INET_E_RESOURCE_NOT_FOUND 		The system cannot locate the resource specified.
1.  A connection to the Internet does not exist and/or could not be established.
2.  System or third party security software is blocking access to the Internet or the installation site/address.
3.  Error on the installation website. For example: The URL may not exist.
4.  Authoring error on the part of the publisher.
5.  Intentional or unintentional corruption of the SST Setup Launcher executable.
1.  Verify that a connection to the Internet can be established or exists prior to running the installation.
2.  Verify that access by the SST Setup Launcher to the Internet, (setup component(s),) download address (see Appendix C) is not blocked by security policy or third party, security software.
3.  Consider using an alternative installation method and package to install the software (See the respective software's online documentation for further details).
4.  Inform the publisher of the error and get a signed, intact installation package.


Topic Hierarchy: Setup Launcher  •  Help & User Guide  •  Table of Contents  •  Warnings and Errors
 
See Also: The Setup Launcher User Interface, The Information Dialog, The Warning Dialog, The Error Dialog, Setup Package Types, Setup Launcher Command Line Switches and Parameters,  

Document/Contents version 1.01
Page/URI last updated on 30.03.2023 		 
Copyright © Stoelzel Software Technologie (SST) 2018 - 2023 		Suggestions and comments mail to:
webmaster@stoelzelsoftwaretech.com