Troubleshooting Application Execution
Application execution may fail due to the configuration of operating system security on Windows Mobile-based devices, as follows:
If the application security configuration requires signed binary files and the application binary files are unsigned, the application does not run. You can sign the files. .
You use the SecurityPolicy Configuration Service Provider to determine the current setting for a security policy. For information about the security configurations, see Windows Mobile-based Device Security Model.
If you've 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.
If you've 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, the application might not run, 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
See Also
Deploying Windows Mobile Applications
Send Feedback on this topic to the authors