Cannot installed because not digitally signed trusted certificate

If you did not explicitly tap on the " No " option, another program or message window may have popped up on your device's screen while the Unsigned prompt was displayed. Windows Mobile will automatically cancel an installation in that case, to prevent software from using malicious means to choose "Yes" to install itself. To resolve the error, simply soft-reset your Windows Mobile PDA or phone and try the installation again.

This error message may also mean that your PDA requires software to be digitally signed in order to be installed. For the vast majority of Windows Mobile devices sold directly to consumers, software will not need to be digitally signed.

A few devices - most notably the Sprint Nextel i and i Windows Mobile Smartphones - do require digitally signed software and may not be able to run our currently unsigned applications. If you are trying to install our software on a Windows Mobile device provided by your employer, it is also possible that your employer has chosen to 'lock down' your Windows Mobile device to prevent unauthorized software installation.

Are there other possible settings perhaps Group Policy settings? In my opinion, if you have installed the certificate into Trusted Root Certification Authorities store and the Trusted Publishers store, permission grants and the add-in would be loaded. Do you try to sign the add-in with other certificates which have been installed in Trusted Root Certification Authorities store? Select Certification Path and check Certificate status. Is it "This certificate is OK"?

This can be beneficial to other community members reading this thread. The add-in then loaded correctly. I'm not sure why this would work for a self-signed certificate and not the certificate of my key card. The status of my key card certificate is OK. Comparing the properties of my self-signed certificate and my key card certificate, the properties are nearly identical:.

Enhanced Key Usage: Code Signing 1. My self-signed certificate notes that it is intended for "All issuance policies"; this language is not included on my key card certificate. Additionally, my key card certificate has data for the following properties, which are absent from the self-signed certificate:. Another difference is that the self-signed certificate is trusted directly; the key card certificate has an intermediate certificate before getting to a trusted root certificate authority.

This seems to be the case even if I add the key card certificate directly to the root certificate stores. In your original post, you said you get the same error when you sign the add-in using a test certificate created by VS.

I suggest you create a new cert and test again. The test certificate is intended for all issuance policies and all application policies.

I think it would work if you import the test certificate into trusted root and trusted publisher store. The certificate created through this process works correctly. How can we make this better? Please provide as much detail as possible. Contact our Support Team. Request Case Start Chat. Translation Feedback How can we make this translation better?

Get notified about latest updates to this technical article? Yes No. Do you want to Unsubscribe? Questions or issues with the site? Send Feedback. Please rate your online support experience with Esri's Support website. Below Satisfied.