Page MenuHome GnuPG
Create Task
Maniphest T5411

After upgrading from gpg4win 3.1.13 to gpg4win 3.1.15 GpgOL does not load, Outlook crashes.
Closed, WontfixPublic
Actions

Description

Starting outlook 2019 leads to "procedure entry point "gpgrt_access" not found in "C:\Program Files (x86)\GnuPG\bin\gpgconf.exe".
Outlook does not start in tune.

Deinstalling GunPG4win complete, then reinstalling does not help.

Details

Version
Gpg4win-3.1.15

Related Objects

Event Timeline

tps800 renamed this task from After upgrading from gpg4win 3.1.13 to gpg4win 3.1.15 to After upgrading from gpg4win 3.1.13 to gpg4win 3.1.15 GnuOL does not load, Outlook crashes..Apr 27 2021, 2:06 AM
tps800 created this task.
• werner renamed this task from After upgrading from gpg4win 3.1.13 to gpg4win 3.1.15 GnuOL does not load, Outlook crashes. to After upgrading from gpg4win 3.1.13 to gpg4win 3.1.15 GpgOL does not load, Outlook crashes..Apr 27 2021, 2:39 PM
• werner triaged this task as Normal priority.Aug 1 2021, 10:56 AM
• werner edited projects, added Support, gpg4win; removed Bug Report.
• werner added a subscriber: • werner.

Please try 3.1.16 and make sure that you don't have other variants of gpg4win installed or Outlook plugins also using parts of gpg4win or its libraries.

keegan added a subscriber: keegan.EditedSep 21 2021, 3:03 AM

I had the same issue opening GPA or Kleopatra going from 3.1.14 to 3.1.16 on Windows 10. I don't have Outlook installed.

• aheinecke added a subscriber: • aheinecke.Sep 21 2021, 9:48 AM

Our windows explorer plugin keeps libgpg-error loaded when you install an upgrade. That is why our installer asks for a reboot at the end of the install. You have ignored the reboot and you then get the error.

We have another ticket T5012 for this issue.

• aheinecke closed this task as Wontfix.Sep 21 2021, 9:49 AM
• aheinecke claimed this task.
keegan added a comment.EditedSep 21 2021, 10:03 AM
In T5411#149872, @aheinecke wrote:

Our windows explorer plugin keeps libgpg-error loaded when you install an upgrade. That is why our installer asks for a reboot at the end of the install. You have ignored the reboot and you then get the error.

We have another ticket T5012 for this issue.

I wasn't asked to restart. The last thing I saw was it offered to open Kleopatra and/or readme.

Restarting after the upgrade didn't resolve the issue.

However, this did fix the issue

  1. Uninstall 3.1.14
  2. Reboot
  3. Install 3.1.16