Please tell us some details. For example the OS used to create the file and
used for decryption, the command lines uses etc.

The file is copied to a network share on a MS Windows Server 2003 (Enterprise
Edition, Service Pack 1). I believe the file is also created on a MS Windows
Server 2003 but need to have that verified. I used this command from the
command line to verify the problem: gpg --output CRB070404.PGP --set-filename
CRB070404.txt --encrypt --recipient cdw.gis@cdw.com --batch CRB070404.txt
I decrypted with: gpg --decrypt --output CRB070404.again --batch CRB070404.PGP

I was signed on remotely to the server using Remote Desktop Connection. I
copied the file to the GnuPG folder. From the command line I changed working
directory to GnuPG to perform encryption/decryption.

The original file is 7.84 GB. The decrypted file was around 4GB.

I'm aware that we're using an older version. An upgrade can be scheduled for
the future. An upgrade will need to be "pushed" to 6 different servers and will
require extensive testing on all servers. It isn't an immediate fix and I will
need to justify the upgrade.

This seems to be the usual 4GB limit. Old versions of gpg for windows had some
problems but I can't remember the details anymore. To avoid problem with large
files it is safer to use

gpg --set-filename foo.txt --recipient xyz --batch <input.txt >output.txt

This way only the shell (cmd.exe) needs to care about large file support as gpg
does not know the length of the file. Do a similar thing for decryption.

For security reasons you should really update to a supported version.

Thank you for your assistance. The encrypt/decrypt commands are normally
created by a program & need to be the way I tested. We will be upgrading in the
near future.