|This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.|
Application execution may fail due to the configuration of operating system security on Windows Mobile devices. If your application is not properly executing, consult the following solutions to resolve the issue.
If the application security configuration requires signed binary files and the application binary files are unsigned, the application does not run. To resolve this issue, you can sign the files .
If you have signed the application binary files, and either the files or the certificate used to sign the files is included in the revocation list, the application does not run. The revocation list contains the hashes of revoked certificates and binary files, as well as .cab files. For more information on application revocation, see Revoking Applications.
The application might not run if you have signed the application binary files, and the certificate chain used to sign the file does not map to a root certificate in one of the following certificate stores, depending on the Unsigned Applications policy setting. You can add a matching root certificate to one of the stores to enable the application to run:
- Privileged Execution Trust Authorities
- Unprivileged Execution Trust Authorities