Hi,
thanks for your report. We already have this on our todo with high priority: T3514
I'm resolving this report as a duplicate.

@simypat Please try to move away GnuPG's data directory ( %APPDATA%\gnupg ) and start GPA again. That should fix it as the problem was a corruption of an internal database that lives in the Home directory (and is not removed when uninstalling).

According to our tests and the Message board this is fixed.

Thanks for that assessment.

What happens in the log:

All source code which makes up the installer is distributed by us. Signed by one or more of the core developers.

Yes, I downloaded from "gpg4win.org".
Notice that the SHA256 from VirusTotal and gpg4win.org for "gpg4win-3.0.1.exe" are identical.
SHA256: f05e5d272a794002149effc516f4b32f62fa575563f632b084bd044017b1206f

I can't reproduce I sent myself serveral messages in which i pasted a PGP Message and they worked. I tried both HTML and Text plain messages.
To be sure I also installed Gpg4win 2.3.0 and sent myself a message with that and that also worked :-/

we uninstalled the old version, restarted, installed the new 3.01, and it still does the error

Virus scanner look for patterns seen in known viruses. However, legitimate software may have the same pattern as other software and thus also in viruses.

Thanks for that clarification Jochen; at least it confirms I'm not going mad. I've got it installed now so will update this if it happens again although, in the meantime, it might be taking a look at the log I attached (if you haven't already) to see if it hints at any behaviour that you know has been fixed.

by "just released" I mean: minutes before i wrote that comment. Since you mentioned gpg4win 3.0.0 in your post, I think you worked with the now old stable release.

Updated this morning and just had a freeze again. Enabled debug mode now. For me the freeze often happens when my pc is locked and I'm not using it for a while, then return to my PC and select another email.

Jochen, I've uninstalled the previous version and now installed the most current release. Unfortunately it did not result in a successful run. Here are the details from the event log.

When you say "just was released", do you know what time that was at? My reason for asking is that I checked for an update just before posting this bug report! I'll try it and see how it goes.

@cosimo193 ; gpg4win 3.0.1 just was released. May you check if this error still exists with that new version?

Unfortunately chocolaty is not managed by us and we don't have the knowledge about this. The Chocolaty Forums/Pages are the better place for this.

Hey @pkoevesdi, Gpg4win Version 3.0.1 was just released. Can you may download and install it and check if this issue still exists?

Hey @cprezalor, the new Gpg4win Version was just released. Can you please download it and check if this error still persists?

Hey, while installing the new Version for checking T3476, you may can check if this issue still persists as well?

@uwestoehr - Gpg4win 3.0.1 just hitted and tehre are several bugfixes including invoking kleopatra from the right-click menu. Can you please install the new version and check if the error still persists?

Version 3.0.1 just hitted. @madjari - may you can check if the various bugfixes in that version fixed your issue as well?

@simypat, version 3.0.1 just hitted. I can't recreate this error anymore. Can you verify this?

With the Release of Gpg4win 3.0.1 this error doesn't appear anymore for me while testing.

With the Release of Gpg4win 3.0.1 the Error doesn't appear anymore while testing with Windows 10 (64bit) with Outlook 2016 and Windows 7 (64bit) with Outlook 2010.

File uploaded is the gpgol debug log file, 7-zipped (it's 165MB without zipping).

The problem is that gpgme-w32spawn.exe uses DETACHED_PROCESS which means that the newly created process does not inherit the console of the parent process.

rO13950a985228 Works around this problem by launching Kleopatra in the background when Outlook is started.
This should both speed up the first operation and work around this issue. In my opinion it's better to waste some resources in the background if Kleo is not needed then to create a bad user experience if encryption does not work and results in a hang of outlook.

Not yet located or identified the bug, but some information.

I could not reproduce it again on Friday. Did some code staring to find the issue but failed. Everything looks Ok.

Forgot to mention this bug in the commit addressing this. ( 278893850ed926d4646929ee97576a8d09fd4998 )

Should avoid the problem. Then import or create n OpenPGp key first and the next time you should(tm) not be bnotered by the bug.

Thanks for your reports.
I can finally reproduce this on a new Test VM which I gave little resources. Most of the time it does not work. Sometimes it works. Looks like a timing issue, on my main development VM which is fairly quick it always works. I'll work on it.

Sorry for the confusion. We tried to reduce the interactions necessary to encrypt a file and our rationale was that users mostly want to either always use textmode or never. (Also See T3486 )

Thanks for your feedback. But this is intentional. There were two problems with with this:

Thank you Werner. Do you know when the next release will be? Is there a way for me to temporarily fix the current version in the code?

This is verly likely be fixed with commit 5ecef193bc2144e6d51a6bd5727bfd08a0d28b66 which will be released with the next gpg4win version.

I am connected via IMAP. Sometimes Outlook also crashes when I handle a message that is in a local inbox not directly associated with an account. It may be relevant that I have two IMAP accounts configured that run on different key pairs and all messages are shifted to a local inbox on arrival.

How are you connected to your server? I mean IMAP, or Exchange MAPI or is it a Hotmai / Outlook.com account?

Not possible to replace it through config as we can't "check" like with sha1sum and the format differs.

Outlook 2007 is deprecated and we will only fix security issues there (or remove it altogether in the future as Outlook 2007 is no longer maintained by MS). GpgOL for Outlook 2010 and Later in Gpg4win 3 has HTML Mail support.

FWIW, I added a gpgtar.1

I resolve this. If it is not displayed anymore it means that outlook should handle it.

Pushed to 2.2

You could use the --directory option. However< I agree that your suggested changes is less surprising then the current behaviour. Thus I would consider this a bug fix. Can you please apply to 2.2?

In Kleopatra this should be possible through the Checksum definition config without any code changes. I'll look into it.

That does not look like a GnuPG or GPGME bug but more like an incompatibility in python-gnupg. Please report this to the maintainers of python-gnupg. I would have suggested to use the GPGME Python bindings but unfortunately we don't have a Windows version on them yet.

Multiple bugs fixed here:

Tested with Gpg4win-3.0.0-beta17 with GpgOL-2.0.2-beta8 on Windows 10 (64bit) with Outlook 2016.

The Documentation is installed. You can find it under Help -> Gpg4win Compendium in Kleopatras menu.

In T3442#105339, @aheinecke wrote:

In T3442#104402, @JochenSaalfeld wrote:

1. Mails encrypted with S/MIME are stored with "No Data" in the sent EMail folder, but arrive properly at the recipients (you will recieve a readable copy, if you add yourself to the list of recipients). This Issue breaks the GpgOL Plugin after some time which is leading to the described Problem.

Fixed with 474cc15d8e331c9def298dbbfe3b99e6c8cf8035

Versions Used: Gpg4win-3.0.0-beta17 with GpgOL-2.0.2-beta8 on Windows 10 (64bit) with Outlook 2016.

@tstreibl thanks for helping with your feedback!
Please note that this issue (T3442) still has the status "testing", because we want to perform some more tests before declaring it resolved. :)

In T3442#105466, @tstreibl wrote:

Starting Outlook still bring up the "Fehler in der Benutzeroberfläche von XML von "GpgOL .....Unbekannte Office.Steuerelemente-ID: TabComposerTool" Message Box.

Sorry for my inpatience...but it's a little bit hard to understand why the above, very simple test procedure obviously isn't reproducible on your systems.

Starting Outlook still bring up the "Fehler in der Benutzeroberfläche von XML von "GpgOL .....Unbekannte Office.Steuerelemente-ID: TabComposerTool" Message Box.

tested your new .dll. Created a new email. Choosed "sign". Pasted an email adress from outlook address book into the "an" field. Outlook crashs. Took me 2 seconds to test. What the hell are you testing?

Thank you very much. Both the signed only and the encrypted mail are fully valid for me (checked on the IMAP server and with kmail) and don't contain any references to gpgolXXX.dat. This means they were correctly converted to valid PGP/MIME Mails.

Dear Andre

Thanks for the report. This is indeed badly broken. I'll work on this now.
I can reproduce and also have a reproducable crash when trying to encrypt a special folder. This must be a recent regression because I tested this some months ago and it worked fine.

Indeed this was a todo that was overlooked.

This might be a reason that we got multiple reports for Kleopatra since 3.0 was released that it hangs on keylisting: https://bugs.kde.org/show_bug.cgi?id=381910

Everything works correctly but the warning message is probably too cryptic. It means that the signature could not be checked because the public key that created this signature is not found. It needs to downloaded, imported and verified. (See: https://www.gpg4win.org/package-integrity.html )
We improved the warning message with gpg4win-3.0