Hi @cklassen thanks for getting back to me.
Answer to your question:
Windows 2019 Datacenter version 1809
Gpg4win version 2.3.3
Kleopatra version 2.2.0
To overcome the issue I granted the service account gpg2.exe file.
User has not reported issue since.
Any suggestion will be welcomed as we’d like to upgrade to the newest version
I’m a little bit confused. First you spoke about an “automated job” then about a user who didn’t report anything since your change. Do both access the same service account?
Furthermore, you wrote in the first post
What do you mean by “log in”?
Generally, Gpg4win works with multiple components, e.g. the gpg-agent so if one of them doesn’t work because of missing permissions that might prevent Gpg4win from working as expected.
And my question is: Do you really expect support for a version from 2016?
Update first and if things then do not work, ask again.
You should be aware that several security issues have been found and fixed since 2016.
Hello @eebb and @cklassen point taken.
I have downloaded the newest version of Gpg4Win 4.4.1 on our test server the installation isn’t straightforward.
Are you able to guide on where I can find an installation guidance regarding the Gpg4Win 4.4.1 version ?
Hi @cklassen , @eebb following upgrading GppWin to the latest version on our UAT .
Client are getting the below error “No appropriate OpenPGP secret key for decryption found“
i can’t resist: have you tried turning it off and on again? but seriously, windows might just need a reboot.
if you’re still seeing an old version afterwards, clearly the upgrade process wasn’t successful in discovering and uninstalling all ancient components. in that case i would suggest:
what does where gpg show? there seems to be a second installation of at least gpg on your system, earlier in %PATH%.
btw, what is the software shown in your "Output (error)" screenshot? is that simply an editor the error message was copied to? is it possible a third party app installed its own copy of gpg.exe?