[Gpg4win-users-en] gpg4win 3.0.0 - post-install errors, Qt5, Vista-32bit
andrew.skretvedt at gmail.com
Mon Sep 25 12:24:03 CEST 2017
Hi list, this is directed to the gpg4win maintainers:
I write to report this problem with the install of the recently released
3.0.0 version under Windows Vista 32-bit.
Prior to install, absent specific advice available about migrating to
the new release, I removed a previously installed release, gpg4win
2.3.3, using its uninstaller, and restarted.
The gpg4win 3.0.0 install wizard proceeded normally (GnuPG, Kleopatra,
GpgEX selected). Kleopatra failed to launch post-install. Windows
reported an error with the faulting module being Qt5Core.dll 220.127.116.11.
This is the final error reported. Before this, two other error dialog
boxes were presented.
Upon launch, the first error dialog read:
> kleopatra - This application failed to start because it could not
> find or load the Qt platform plugin "windows" in "". Reinstalling
> the application may fix the problem.
After clicking "OK" to dismiss, another error dialog box appears:
> Microsoft Visual C++ Runtime Library - This application has
> requested the Runtime to terminate it in an unusual way. Please
> contact […snip]
A quick check of my system with _Process Explorer_ reveals that
Kleopatra did in fact utilize the version installed at "C:\Program
Files\Gpg4win\bin\Qt5Core.dll", the base directory being the installer
default, as I left it.
My msvcrt.dll version is 7.0.6002.18551
My guess is that the version of this library bundled is inappropriate
for Vista 32-bit, but perhaps suited for other versions?
While kleopatra does not function, GnuPG appears to be semi-operable. I
find that enigmail+Thunderbird seems to work, but any operation that
requires use of pinentry.exe (e.g. signing mail, decrypting mail) fails
for what appears to be the same reasons as kleopatra did above.
I believe there is little I can do further to address the problem, and I
request no special assistance. I can always revert to my previously
installed release in the meantime, which works fine.
Please confirm: is this a problem with the gpg4win 3.0.0 distribution
as-released, and if so should I simply wait for a fixup release?
Separately, I'm also using an older release of gpg4win on a WinXP 32-bit
system as well. It's working fine and while I intended to update it
there too, I will hold off for now.
Thanks for all the hard work!
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 4004 bytes
Desc: S/MIME Cryptographic Signature
More information about the Gpg4win-users-en