"Oops, we had a problem communication with our services"

This is a follow-up to ticket #12197, which I had opened a fortnight ago and which has unfortunately been closed without providing me with a solution. However, the problem surprisingly has been fixed for quite a few users.

The problem is again indicated by the error message "Oops, we had a problem communication with our services". It occured the first time (#12197) just after the update to version 2.0.0-20180604093219+f899a761a7. I'm now at version 2.1.1-20180620155301+d1d498c61f.

I was told that the problem was related to Named Pipes. That's why I include a hardcopy of the two Named Pipes created by keybase.

C:\SysUtil\SysInternals\PipeList>pipelist | find "Key"
kbservice\Users\Tom\AppData\Local\Keybase\keybased.sock 3
-1
kbservice\Users\Tom\AppData\Local\Keybase\kbfsd.sock 1 -1

my log id: c7c533b0423001b60f4ccb1c

Start by reviewing follow-up issue #12197 and the supplied log ID and Windows named-pipe output. Identify a reproducible service-communication failure and document a confirmed fix for the reported error; the issue names no source file or test to run.

Written by the indexing model from the issue text.