When installing Elastic Agent on a machine running Windows 10 in German actions status, diagnostics, restart and version always provide a permissions error, similar to the one below:

Error: failed to communicate with Elastic Agent daemon: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing open [\\\\.\\pipe\\elastic-agent-system](file:///pipe//elastic-agent-system): Zugriff verweigert"

Version provides the binary version, but fails to provide the Daemon with <failed to communicate> then a similar message as above.

Status fails completely with a similar message.

Diagnostics fails completely.

Diagnostics collect will generate the content (at least partially), including error messages in file and in screen.

Restart fails completely.

The exact same setup on a Windows 10 in English machine works normally, so it seems a localization problem.

Even though data seems to be flowing, I'm not sure it's complete and the lack of "administrative" tasks makes the use of Elastic Agent mostly impossible.

This behaviour is independent of integrations, or being installed with Fleet or standalone.

For confirmed bugs, please report:

• Version: Elastic Agent 8.2.3
• Operating System: Windows 10 Home
• Steps to Reproduce:
  1. Spin a machine (or VM) with Windows 10 in German
  2. Install Elastic Agent following the instructions from Fleet (or from Elastic docs)
  3. Run ./elastic-agent.exe status (or the other commands) and see it fail

@ckauf @jstrassb FYI