"inst_gpgol = false" in the "gpg4win.ini" has no affect.
After Install, the gpgol.dll will find in the Program Folder, the Plugin
will find in Outlook (active or not).
We use "gpg4win.exe /S /C=(path)\gpg4win.ini
Description
Details
- Version
- 2.2.x to 2.3.0
Related Objects
- Mentioned Here
- T1837: GPGOL causes Outlook to crash
Event Timeline
xyzspeedy wrote to me that the behaviour is reproducable with
Windows 7, 8.1 and 10 (each time pro x64)
Hi,
I've looked at the code and everything seems finde there. Config file is read
and if the entry is set the installation section is unselected.
To verify it works:
I've uninstalled gpg4win on a testsystem (Win 10 32 bit but that should really
have no influence at all)
- Verified that GpgOL was unregistered and did not show up in outlook
- Closed outlook
- Installed Gpg4win from the command line: C:\Users\aheinecke>C:\Users\aheinecke\Downloads\gpg4win-2.3.0.exe /S
/C=C:\Users\aheinecke\Desktop\gpg4win.ini
The Gpg4win.ini was minimal and only contained one line:
inst_gpgol=false
-> Confirmed that GpgOL.dll is not installed in the installation direcotry.
-> Confirmed that GpgOL does not show up in Outlook.
Then I've downloaded the gpg4win.ini you've uploaded here and tried again with
that. Still everything works as expected. No GpgOL is installed and it does not
show up in Outlook. Then I've changed inst_gpgex to false in your ini and tried
again and confirmed that GpgEX is also not installed. (Just to verify that
really that file is used.)
Is there something special with the Path where you have the gpg4win.ini ? E.g.
Is it on a Network directory? (This might fail with windows UAC) or does the
Path contain spaces?
Regards,
Andre
Hello Andre,
i think, we can close this Ticket, You're Right.
But:
We have tested on more than five Systems with the attached INI and with
[gpg4win]
inst_gpgol = false
Call: gpg4win.exe /S /C={path}\gpg4win.ini (local or Network)
But gpgOL was installed an all Systems.
Then - after reading your Post - we tested on fresh Systems with Outlook 2013:
In all INI-Variations with 'inst_gpgOL=false', gpgOL was NOT installed.
We think, there ist a Problem in the Oulook-(Plugin)-Config on the tested
Systems, but i'm not shure, what we can do but not creating new Profiles.
I don't know, why the gpgol.dll ist installed on the mismatched
Outlook-Configurations. On fresh Systems 'inst_gpgol=false' works.
December 2015 up to January 2016, Outlook 2010 and 2013 running very
instable (crash one to five times per day) - with or without pgp.
When we have an answer from our Side, we tell you.
Greetings,
Joachim
Hi,
If Gpg4win was already installed a new install with inst_gpgol=false will not
uninstall it. For this you have to uninstall first.
(With the upcoming gpg4win-3.0.0 we are changing that and are always calling
uninstall first on update.)
You can disable an installed GpgOL by setting the registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addins\GNU.GpgOL]
"LoadBehavior"=dword:00000000
As this can be overridden on a user level you might also want to check the same
key in HKEY_CURRENT_USER context.
With regards to the crashes. I'm sorry to hear that. We had an extremely nasty
bug that could cause random crashes unrelated to crypto operations ( T1837 )
that bug was only fixed with gpg4win-2.3.0.
Regards,
Andre
On Friday 26 February 2016 at 11:45:07, xyzspeedy via BTS wrote:
We think, there ist a Problem in the Oulook-(Plugin)-Config on the tested
Systems, but i'm not sure,
An analysis step would be to have remote access to one of your desktops
and have someone from us examine. (Right now it seems that it is likely
to be a problem creating with your specific setup, so we would offer this
as a paid service over gpg4win-professional@ to you.)