Changing this to priority low until I see a second report from a different user with a similar log.
This looks more like a broken Outlook setup on this users account then a problem where we can actually help.

No, which addons are active is a user property. So maybe you can try disabling all others but GpgOL, and then basically bisect which one it is that is conflicting.

In general there always might be problems with incompatibilities of other addins installed on a system.

I am running in a setup where my GnuPG 2.3 is connected to a gpg-agent / scdaemon running at GnuPG 2.2.12.

Okay, I usually only keep hitting crl+w in that case. But I see the point when doing imports this can be annoying.

there was an issue that has been fixed in 3.1.14 which was creating problems / crashes when the home directory of a user had a unicode character in it. So maybe your one user had such a username?

Right that description sounds like it is ~20 years old ;-)

Will be fixed with 3.1.14

Works, I've tested with Kleopatra.

I really like that you do stuff like this.

We understand the problem, it's a regression from August. For T4083 we changed an internal function to better work with Windows UTF-16 filenames in preperation to at some point fully support UTF-16 and only use the wide character functions as system calls.
But that broke places where internally the local 8 bit encoding was still used.

I can reproduce this.

Hi Zetrick,

Hi Zetrick,