File Share Encryption

Windows 7 x64 PGP 10.2.1 MP5

University of Florida managed but none of my help channels have seen this issue.

After about two months of using this product, after a reboot I see a progress bar and get this error:
 

Progress Bar Text:

   Please wait while Windows configures Symantec Encryption Desktop

Error:

   The feature you are trying to use is on a network resource that is unavailable. Click OK to try again, or enter an alternate path to a folder containing the installation package 'PGP7A7E.msi' in the box below

   Use Source: C:\Users\username\AppData\Roaming\PGP Corporation\PGP

When I browse to that directory, there are no .msi files.

Thanks for the help,

try this link,

https://www-secure.symantec.com/connect/forums/missing-pgp-desktop-msi-file

I have also seen an issue reported (internally) where certain versions of Symantec Endpoint Protection could be quarantining the file. I would suggest possibly whitelisting the pgp desktop msi filename and/or disabling SEP if you have it installed to see if that helps (as a workaround obviously).

Please do post your results as we are always interested in hearing feedback on how we can improve our products to fit our customers needs.

oh, i just re-read your original post again and this also sounds like an issue I have seen from time to time related to how the MSI was originally deployed. I would recommend redownloading the customized MSI installer that you are deploying within your company and store it on the local C drive in a place where the user will have access and it won't be deleted easily though (like c:\ or else maybe in the users profile somewhere) but not in a temporary directory.

Then when that dialog box pops up, click the browse button and point it to the correct MSI file.

Of course you would need to provide the same MSI file for the version of  PGP that the product was originally installed with.

The other option is to uninstall PGP and then reinstall with the customized installer package (MSI). Since this dialog box typically occurs on a reboot when there is a component missing or it needs reinstalled on the machine.