Standard gnupg folder created despite --homedir parameter

Carola Grunwald caro at
Wed Aug 10 01:23:32 CEST 2016

Hello Werner,

many thanks for your involvement in this discussion.  GPG 2.1 took big
steps towards becoming a truly portable application.

On Tue, 09 Aug 2016 12:10:21 +0200, Werner Koch <wk at> wrote:

>On Mon,  8 Aug 2016 18:20, sinclair.andersen at said:
>>  set GNUPGHOME=.
>Don't use a relative path for GNUPGHOME unless you use gnupg 2.1.
>Regarding those portable applications: 
>     On Windows systems it is possible to install GnuPG as a portable
>     application.  In this case only this command line option is
>     considered, all other ways to set a home directory are ignored.
>     To install GnuPG as a portable application under Windows, create an
>     empty file name 'gpgconf.ctl' in the same directory as the tool
>     'gpgconf.exe'.  The root of the installation is than that
>     directory; or, if 'gpgconf.exe' has been installed directly below a
>     directory named 'bin', its parent directory.  You also need to make
>     sure that the following directories exist and are writable:
>     'ROOT/home' for the GnuPG home and 'ROOT/usr/local/var/cache/gnupg'
>     for internal cache files.

May I ask how that translates into the Windows world?  Is it a way to
get rid of the ...\AppData\Roaming\gnupg folder?

I have all executables in my gpg main folder and call gpg.exe
exclusively from that directory with a '--homedir "...\gpg"' parameter,
while that gnupg folder still gets created.



More information about the Gnupg-users mailing list