Opensearch 3.2 as Service fails to start on Windows with 1067 Error

OpenSearch 3.2 on Windows server fails to start as Service with error 1067 Proccess terminated unexpectedly. No meaningfull details in logs.

If I start it from console, it runs OK. Opensearch 2.19.3 on same sever starts as Service like a charm.

Could please anyone help to solve the problem.

@romanmohan What do you see in OpenSearch logs? Could you share the logs output of the faulty service?

What is the Windows version?

Hi @pablo

opensearch-service-x64.2025-08-26.log

[2025-08-26 14:24:59] [info]  [ 2692] Starting service 'opensearch-service-x64' ...
[2025-08-26 14:24:59] [info]  [15444] Commons Daemon procrun (1.1.0.0 64-bit) started
[2025-08-26 14:24:59] [info]  [15444] Running 'opensearch-service-x64' Service...
[2025-08-26 14:24:59] [info]  [ 7352] Starting service...
[2025-08-26 14:25:00] [error] [ 2692] apxServiceControl(): dwState(4) != dwCurrentState(1); dwWin32ExitCode = 1067, dwWaitHint = 0, dwServiceSpecificExitCode = 0
[2025-08-26 14:25:00] [error] [ 2692] apxServiceControl(): returning FALSE
[2025-08-26 14:25:00] [error] [ 2692] Failed to start service 'opensearch-service-x64'
[2025-08-26 14:25:00] [info]  [ 2692] Start service finished, returning 0
[2025-08-26 14:25:00] [error] [ 2692] Commons Daemon procrun failed with exit value: 5 (Failed to start service)

opensearch-service-x64-stderr.2025-08-26.log

2025-08-26 13:44:03 Commons Daemon procrun stderr initialized
Failed to start service

Windows Server 2019 Standard

@romanmohan Could you share command that set the service in that Windows Server?

@pablo I use built-in tool - opensearch-service.bat install

@romanmohan I’ve reproduced your issue in all 3.x versions. 2.19.3 was the last working version.
According to this GitHub issue, -javaagent option could cause it.

I’ve already made a comment there with my testing results.

Hi @pablo ,

thank you for information. Hope, this will be fixed soon.

@romanmohan I was able to start the OpenSearch service with opensearch-service.bat start on Windows Server 2019.
However, it worked when I removed Microsoft Visual C++ 2015-2022 Redistributable (x64). This was installed as part of the VMware tools installation.

Hi Folks, I just pulled 3.4, and I’m hitting the same error. Does anybody know any updates?

@JeffBlumenthal The GitHub issue is still opened. You can comment there to check for any progress.

1 Like