Re: GnuPG 2.4.8 / Kleopatra Hanging - gpg --list-keys and keyboxd Unresponsive on Windows Server

"niveditharao.kulkarni--- via Gnupg-users" <[email protected]> Mon, 27 Jul 2026 09:49:50 +0530
Newsgroups gmane.comp.encryption.gpg.user
Message-ID <CAJGfpUHe1de=sC1yW4xDNpX_qiq_mNwMtpRQWedSd0bOEbkX6A@mail.gmail.com>
--===============1205155824029882161==
Content-Type: multipart/alternative; boundary="0000000000003d73cf065790094e"

--0000000000003d73cf065790094e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,
Thank you       Alexander, for the response and helpful reply.
Your second suggestion was exactly the cause. We found that the socket
files in the GnuPG home dir were stale. S.keboxd in particular had a
last modified timestamp frozen on the day the failure began and was never
updated after that. We stopped all GnuPG processes and renamed those socket
files to .bak, which forced GnuPG to regenerate them on the next run.
Encryption started working immediately.

Thank you
Best regards
Nivedta

On Fri, Jul 24, 2026 at 6:35=E2=80=AFPM Alexander Kulbartsch <
[email protected]> wrote:

> Hello Niveditha!
>
> From what you wrote in your detailed description I assume you
> installed Gpg4win 4.4.1. But for automation you use the gpg CLI
> tool.
>
> Since that version a few fixes to the keyboxd were made. So I
> recommend that you install a recent version. The current release
> is 5.0.2.
> (Don't mind the major release number change, the crypto is
> fully compatible with the previous versions.)
>
> If you are still on Windows Server 16, Gpg4win 4.4.1 was the
> latest supported version, because of a QT bug for old Windows
> versions. But you can use the recent CLI gpg version.
>
> Another idea:
> In case you started gpg with another user than usual one, the
> socket files might have wrong rights. Try to delete them here:
> %LOCALAPPDATA%\gnupg\S.*
>
> Hope that helps!
>
> Best regards
>        Alexander
>
>

--0000000000003d73cf065790094e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div id=3D"gmail-:12j" class=3D"gmail-Am gmail-aiL gmail-a=
O9 gmail-Al editable gmail-LW-avf gmail-tS-tW gmail-tS-tY" aria-label=3D"Me=
ssage Body" role=3D"textbox" aria-multiline=3D"true" tabindex=3D"1" style=
=3D"direction:ltr;min-height:85px" aria-controls=3D":1d4" aria-expanded=3D"=
false">Hi,<div>Thank you=C2=A0

<span style=3D"color:rgb(136,136,136)">=C2=A0 =C2=A0 =C2=A0Alexander,</span=
>=C2=A0for the response and helpful reply.=C2=A0</div><div>Your second sugg=
estion was exactly the cause. We found that the socket files in the GnuPG h=
ome dir were stale. S.keboxd in particular=C2=A0had a last=C2=A0modified ti=
mestamp frozen on the day the failure began and was never updated after tha=
t. We stopped all GnuPG processes and renamed those socket files to .bak, w=
hich forced GnuPG to regenerate them on the next run. Encryption started wo=
rking immediately.</div><div><br></div><div>Thank you=C2=A0</div><div>Best =
regards</div><div>Nivedta</div></div></div><br><div class=3D"gmail_quote gm=
ail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jul 24, =
2026 at 6:35=E2=80=AFPM Alexander Kulbartsch &lt;<a href=3D"mailto:alexande=
[email protected]">[email protected]</a>&gt; wrote:<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex">Hello Niveditha!<br>
<br>
>From what you wrote in your detailed description I assume you<br>
installed Gpg4win 4.4.1. But for automation you use the gpg CLI<br>
tool.<br>
<br>
Since that version a few fixes to the keyboxd were made. So I<br>
recommend that you install a recent version. The current release<br>
is 5.0.2.<br>
(Don&#39;t mind the major release number change, the crypto is<br>
fully compatible with the previous versions.)<br>
<br>
If you are still on Windows Server 16, Gpg4win 4.4.1 was the<br>
latest supported version, because of a QT bug for old Windows<br>
versions. But you can use the recent CLI gpg version.<br>
<br>
Another idea:<br>
In case you started gpg with another user than usual one, the<br>
socket files might have wrong rights. Try to delete them here:<br>
%LOCALAPPDATA%\gnupg\S.*<br>
<br>
Hope that helps!<br>
<br>
Best regards<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0Alexander <br>
<br>
</blockquote></div>

--0000000000003d73cf065790094e--


--===============1205155824029882161==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Gnupg-users mailing list
[email protected]
https://lists.gnupg.org/mailman/listinfo/gnupg-users

--===============1205155824029882161==--