I've been struggling a bit on this issue, and wanted to share to see if others have the same experience, or if I'm just missing something obvious:
I've got a senario where a user is using PGP 10.3 (that would be Symantec Encryption Desktop 10.3.0):
They place a text document in the File Share Encrypted folder (located on a Windows 2008r2 Std server rigged for file services). It becomes encrypted (like it should). They then open the text document (doc1.txt), modify it, and save as a different document name(doc2.txt), then close the renamed text document. It is saved in the same file share encrypted folder as doc1.txt is.
The issue:
When opening up doc2.txt, it shows corruption at the end of the file.
Additional Observation:
If the user creates a new document (doc3.txt) and copies the contents from doc1.txt into doc3.txt, saves the file in the same FSE, opening it works as intended.
This same behavior seems to be found when the user is attempting to modify Access databases in office 2007 and 2010. Any modification of the encrypted file and changing the name corrupts the file. The users have to maintain the encryption of the document.