PC running on Windows 10, v.22H2, build 19045.5198 (Windows 10 version 2009 (x86_64)) I updated from gpg4win-4.3.1.exe to gpg4win-4.4.0.exe. New Kleopatra 3.3.0 generates an error message at start: "Der Prozedureinsprungspunkt "npth_get_version" wurde in der DLL "C:\Program Files (x86)\GnuPG\bin\dirmngr.exe" nicht gefunden" This message shows up 2 times. After confirming both by "OK", Kleopatra starts apparently without further problems. Kleopatra selftest dirmngr konfiguration fails: "The configuration file is invalid. Sie sollten "gpgconf --check-options dirmngr" manuell von der Befehlszeile ausführen."
I suspect that something went wrong during the update. After installing the update, have you been asked if you want to reboot the system now or later? If yes, did you click Later and then forgot to reboot? Please reboot (Neustarten) your computer. Shutting it off and on again may not be sufficient because Windows plays tricks to start very quickly. If a reboot of Windows does not fix the problem then it's best to uninstall Gpg4win, reboot the computer (to make sure that really everything is uninstalled), and then re-install Gpg4win. Uninstalling Gpg4win won't delete any of your data, but it's always advisable to make a backup.
Am 06.12.2024 um 15:19 schrieb Ingo Klöcker: > https://bugs.kde.org/show_bug.cgi?id=497127 > > --- Comment #1 from Ingo Klöcker <kloecker@kde.org> --- > I suspect that something went wrong during the update. > > After installing the update, have you been asked if you want to reboot the > system now or later? If yes, did you click Later and then forgot to reboot? > > Please reboot (Neustarten) your computer. Shutting it off and on again may not > be sufficient because Windows plays tricks to start very quickly. > > If a reboot of Windows does not fix the problem then it's best to uninstall > Gpg4win, reboot the computer (to make sure that really everything is > uninstalled), and then re-install Gpg4win. Uninstalling Gpg4win won't delete > any of your data, but it's always advisable to make a backup. Thank you very much. Uninstall - reboot - re-install made it! I must confess that I was dumb not to try this method by myself first... :-\
Great to hear that re-installation fixed the problem.