GpgEX for 64 bit Windows test version

Bob Henson oldbob at
Tue Jun 25 10:25:21 CEST 2013

On 25/06/2013 12:53 AM, Henry Hertz Hobbit wrote:
> On 06/24/2013 06:18 PM, Bob Henson wrote:
>> When I ran
>>  regsvr32 c:\Program Files (x86)\GNU\GnuPG2\bin\gpgex.dll
>> it just caused an error, saying "The module "c:\program" failed to load.
>> Make sure the binary is stored at the specified path or debug it to
>> check for problems with the binary or dependant .dll files. The
>> specified module could not be found."
> Try putting double quotes at the start and end of the  string,
> e.g.:
> regsvr32 "c:\Program Files (x86)\GNU\GnuPG2\bin\gpgex.dll"
> I can NOT assure you that this will work but it probably
> will.

That was my problem - thank you for the explanation.

> I wished Microsoft had used just "C:/Programs/" instead of
> "C:\Program Files\" for %ProgramFiles%.  I don't know what
> to say about 64 bit other than don't mix / match.  Microsoft
> could have used "C:/Programs/64/" but that would have made
> too much sense.  Microsoft wants back-slashes instead of
> slashes and a nice mix of punctuation marks in addition to
> dot "." plus space characters in all folder and file names.
> It doesn't work very well, especially for something done from
> cmd.exe instead of the GUI.  How bad is it?  I COPY 7za.exe
> to use it in scripts because I don't want to make registry
> changes (%Path%) just to make it work from where it is at.
> Sigh

I can see your points. I have only recently started using Linux, and the
command line functions are much more logical - however, using two sets
is even more confusing. Now I can't remember which way to slash :-) I
blame old age - but I get there in the end, with the help of my friends.

GpgEx is now working just fine. I used to use another explorer extension
( I forget the name - I think it used to be in Gpg4win?) which stopped
being developed so it will be handy to have one again.



More information about the Gnupg-users mailing list