Troubleshooting Application Installation
During cab installation, the user might be prompted with a dialog box with the following message: You must restart the device to complete the installation. Click OK to restart, or Cancel to continue. This occurs if your installation application overwrites a DLL that is already running. The install proceeds because the MoveFile function works with running files, but deleting the backup fails because the DeleteFile function does not support deleting files without an exclusive lock. This same sort of installation interruption can also occur if your installation application uses shadowing during the install. For more information.
Application installation can fail due to the configuration of operating system security on Windows Mobile-based devices, as follows:
If the Unsigned Themes policy and Unsigned CABS policy settings require signed .cab files and the application .cab file is unsigned, the installation fails. You can sign the .cab file.
Use the SecurityPolicy Configuration Service Provider to determine the current setting for a security policy. You use Microsoft Authenticode tools to sign .cab files. For information about the Authenticode tools, see the Authenticode documentation under "Security" in the MSDN library.
If you've signed the application .cab file and either the file or the certificate used to sign the file is included in the revocation list, the application installation fails. The revocation list contains the hashes of revoked certificates and .cab files, as well as binary files. For more information on revocation lists, see Revoking Applications.
If you've signed the application .cab file and the Software Publisher Certificate (SPC) store does not contain a matching root certificate for the certificate chain used to sign the file, the application installation fails. You can add a matching root certificate to the SPC store to enable the application to install.
See Also
Deploying Windows Mobile Applications
Send Feedback on this topic to the authors