After rebooting your computer, you receive the following error:
PGP is unable to open your keyring files at the specified locations. The files may be missing...
You may also see either missing keys, only the public portion of a public-private keypair, or the key name displayed in italics.
This happens when your PGP keyring files are not available when PGP Tray attempts to start during the boot up of the system. This can occur due to a couple of reasons:
- The keyrings are located in a folder that is temporarily unavailable. By default the PGP keyrings are located in the My Documents\PGP folder and the error can occur if your My Documents folder has been redirected to a network share that is unavailable.
- If your keyring files have been deleted.
If your My Documents folder has been redirected to a network share, confirm the status of the network drive or share.
If your keyring files in the PGP folder in My Documents have been inadvertently deleted use the following steps to correct the error.
- Open Notepad (Start > All Programs > Accessories > Notepad)
- Select File > Save As then navigate to the My Documents > PGP folder.
- In the File name field, type pubring.pkr then click Save.
- Click File > New then Select File > Save As. Confirm you are still in the My Documents > PGP folder.
- In the File name field, type secring.pkr then click Save. You should now have two files in the PGP folder that appear as PGP key icons.
- Close Notepad.
- On the PGP Keyring Files screen, click Try Again.
If you have created a backup of your PGP keyring as a .asc file, you can then import the files to restore your PGP keys.
If you have backed up your keyring files to another location using the automatic backup feature, you can copy the files to the My Documents > PGP folder and then update your keyring properties by right-clicking All Keys under the PGP Keys Control box. Backup keyring files are named secring-bak.skr and pubring-bak.pkr.
You can also move the keyring to a new location that does not use folder redirection using the directions in Knowledge Base Article HOWTO42050.