# Problem with cluster after Windows Server patch

**URL:** <https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183>\
**Category:** Elastic Search\
**Created:** [March 20, 2025, 1:03pm UTC](https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183 "2025-03-20T13:03:55Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![mbooh](https://avatars.discourse-cdn.com/v4/letter/m/e495f1/32.png) [@mbooh](https://discuss.elastic.co/u/mbooh)\
**Post date:** [March 20, 2025, 1:03pm UTC](https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183/1 "2025-03-20T13:03:55Z")

</div>

Hi!

A week a go we added a Microsoft patch to our three test servers and after that we have major issues with Elastic. We often get timeout when doing a full reindex.

This is the startup log:

```auto
[2025-03-20 13:17:19] [debug] ( prunsrv.c:1994) [3020] Apache Commons Daemon procrun log initialized.
[2025-03-20 13:17:19] [info] ( prunsrv.c:2002) [3020] Apache Commons Daemon procrun (1.3.1.0 64-bit) started.
[2025-03-20 13:17:19] [info] ( prunsrv.c:1906) [3020] Running Service 'elasticsearch-service-x64'...
[2025-03-20 13:17:20] [debug] ( prunsrv.c:1677) [3676] Inside serviceMain()...
[2025-03-20 13:17:20] [debug] ( prunsrv.c:1123) [3676] reportServiceStatusE: dwCurrentState = 2 (SERVICE_START_PENDING), dwWin32ExitCode = 0, dwWaitHint = 3000 milliseconds, dwServiceSpecificExitCode = 0.
[2025-03-20 13:17:20] [info] ( prunsrv.c:1422) [3676] Starting service...
[2025-03-20 13:17:20] [debug] ( prunsrv.c:497 ) [3676] Checking Java options for environment variable requirements
[2025-03-20 13:17:20] [debug] ( prunsrv.c:501 ) [3676] Checking environment variable requirements for '-XX:+UseSerialGC'
[2025-03-20 13:17:20] [debug] ( prunsrv.c:501 ) [3676] Checking environment variable requirements for '-Des.path.home=C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0'
[2025-03-20 13:17:20] [debug] ( prunsrv.c:501 ) [3676] Checking environment variable requirements for '-Des.path.conf=C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0\config'
[2025-03-20 13:17:20] [debug] ( prunsrv.c:501 ) [3676] Checking environment variable requirements for '-Des.distribution.type=zip'
[2025-03-20 13:17:20] [debug] ( prunsrv.c:501 ) [3676] Checking environment variable requirements for '-Dcli.name=windows-service-daemon'
[2025-03-20 13:17:20] [debug] ( prunsrv.c:501 ) [3676] Checking environment variable requirements for '-Dcli.libs=lib/tools/server-cli,lib/tools/windows-service-cli'
[2025-03-20 13:17:20] [debug] ( javajni.c:216 ) [3676] Explicit RuntimeLib specified 'C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0\jdk\bin\server\jvm.dll'
[2025-03-20 13:17:20] [debug] ( javajni.c:280 ) [3676] Adding Java bin path to the PATH to fix loading of awt.dll: 'C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0\jdk\bin'
[2025-03-20 13:17:20] [debug] ( javajni.c:286 ) [3676] Loading JVM DLL 'C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0\jdk\bin\server\jvm.dll'
[2025-03-20 13:17:20] [debug] ( javajni.c:414 ) [3676] Loaded JVM DLL 'C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0\jdk\bin\server\jvm.dll', home '(null)'.
[2025-03-20 13:17:20] [debug] ( javajni.c:419 ) [3676] JNI_GetCreatedJavaVMs...
[2025-03-20 13:17:20] [debug] ( javajni.c:817 ) [4104] JVM Option[0] -XX:+UseSerialGC
[2025-03-20 13:17:20] [debug] ( javajni.c:817 ) [4104] JVM Option[1] -Des.path.home=C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0
[2025-03-20 13:17:20] [debug] ( javajni.c:817 ) [4104] JVM Option[2] -Des.path.conf=C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0\config
[2025-03-20 13:17:20] [debug] ( javajni.c:817 ) [4104] JVM Option[3] -Des.distribution.type=zip
[2025-03-20 13:17:20] [debug] ( javajni.c:817 ) [4104] JVM Option[4] -Dcli.name=windows-service-daemon
[2025-03-20 13:17:20] [debug] ( javajni.c:817 ) [4104] JVM Option[5] -Dcli.libs=lib/tools/server-cli,lib/tools/windows-service-cli
[2025-03-20 13:17:20] [debug] ( javajni.c:817 ) [4104] JVM Option[6] -Djava.class.path=C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/ecs-logging-core-1.2.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/elasticsearch-8.17.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/elasticsearch-cli-8.17.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/elasticsearch-core-8.17.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/elasticsearch-entitlement-8.17.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/elasticsearch-geo-8.17.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/elasticsearch-grok-8.17.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/elasticsearch-log4j-8.17.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/elasticsearch-logging-8.17.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/elasticsearch-lz4-8.17.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/elasticsearch-native-8.17.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/elasticsearch-plugin-analysis-api-8.17.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/elasticsearch-plugin-api-8.17.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/elasticsearch-secure-sm-8.17.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/elasticsearch-simdvec-8.17.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/elasticsearch-tdigest-8.17.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/elasticsearch-x-content-8.17.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/HdrHistogram-2.1.9.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/hppc-0.8.1.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/jcodings-1.0.44.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/joni-2.1.29.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/jopt-simple-5.0.2.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/log4j-api-2.19.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/log4j2-ecs-layout-1.2.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/lucene-analysis-common-9.12.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/lucene-backward-codecs-9.12.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/lucene-core-9.12.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/lucene-facet-9.12.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/lucene-grouping-9.12.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/lucene-highlighter-9.12.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/lucene-join-9.12.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/lucene-memory-9.12.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/lucene-misc-9.12.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/lucene-queries-9.12.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/lucene-queryparser-9.12.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/lucene-sandbox-9.12.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/lucene-suggest-9.12.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/lz4-java-1.8.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0/lib/cli-launcher/cli-launcher-8.17.0.jar
[2025-03-20 13:17:20] [debug] ( javajni.c:817 ) [4104] JVM Option[7] exit
[2025-03-20 13:17:20] [debug] ( javajni.c:817 ) [4104] JVM Option[8] abort
[2025-03-20 13:17:20] [debug] ( javajni.c:1062) [4104] Java worker thread started for org/elasticsearch/launcher/CliToolLauncher:main
[2025-03-20 13:17:20] [debug] ( javajni.c:1068) [4104] JNI calling static void method org/elasticsearch/launcher/CliToolLauncher:main
[2025-03-20 13:17:22] [debug] ( prunsrv.c:1486) [3676] Java started 'org/elasticsearch/launcher/CliToolLauncher'.
[2025-03-20 13:17:22] [info] ( prunsrv.c:1585) [3676] Service started in 2062 milliseconds.
[2025-03-20 13:17:22] [debug] ( prunsrv.c:1123) [3676] reportServiceStatusE: dwCurrentState = 4 (SERVICE_RUNNING), dwWin32ExitCode = 0, dwWaitHint = 0 milliseconds, dwServiceSpecificExitCode = 0.
[2025-03-20 13:17:22] [debug] ( prunsrv.c:1832) [3676] Waiting for worker to finish...
[2025-03-20 13:17:22] [debug] ( javajni.c:1157) [3676] apxJavaWait -> WaitForSingleObject (0x00000000000002A0, -1 milliseconds) (-1=INFINITE)...
[2025-03-20 13:18:21] [debug] ( javajni.c:1087) [4104] Java worker thread finished org/elasticsearch/launcher/CliToolLauncher:main with status = 0
[2025-03-20 13:18:21] [debug] ( javajni.c:1160) [3676] apxJavaWait <- WaitForSingleObject (0x00000000000002A0, -1 milliseconds) = 0
[2025-03-20 13:18:21] [debug] ( prunsrv.c:1837) [3676] Worker finished.
[2025-03-20 13:18:21] [debug] ( prunsrv.c:1864) [3676] Waiting for all threads to exit.
[2025-03-20 13:19:22] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:19:22] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:19:22] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:19:35] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:19:37] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:19:38] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:20:22] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:20:22] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:21:22] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:21:22] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:22:22] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:22:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:23:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:23:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:24:22] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:24:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:24:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:25:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:25:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:26:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:26:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:27:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:27:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:28:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:28:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:29:22] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:29:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:29:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:30:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:30:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:31:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:31:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:32:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:32:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:33:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:33:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:34:22] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:34:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:34:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:35:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:35:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:36:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:36:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:37:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:37:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:38:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:38:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:39:22] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:39:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:39:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:40:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:40:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:41:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:41:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:42:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:42:24] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:43:25] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:43:25] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:44:22] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:44:25] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:44:25] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:45:25] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:45:25] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:46:25] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:46:25] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:47:25] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:47:25] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:48:25] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:48:25] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:49:22] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:49:25] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:49:25] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:50:25] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:50:25] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:51:26] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:51:26] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:52:26] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:52:26] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:53:26] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:53:26] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:54:23] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:54:26] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:54:26] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:55:26] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:55:26] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:56:26] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-20 13:56:26] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.

```

What is the Service SERVICE\_CONTROL\_INTERROGATE signalled.? Could that have something to do with our issues?

On the two servers that not master nodes I find this in the log:

```auto
[2025-03-17 13:56:35] [info] ( prunsrv.c:1621) [5956] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-03-17 13:57:05] [info] ( prunsrv.c:1606) [5956] Service SERVICE_CONTROL_STOP signalled.
[2025-03-17 13:57:05] [debug] ( prunsrv.c:1123) [5956] reportServiceStatusE: dwCurrentState = 3 (SERVICE_STOP_PENDING), dwWin32ExitCode = 0, dwWaitHint = 3000 milliseconds, dwServiceSpecificExitCode = 0.
[2025-03-17 13:57:05] [info] ( prunsrv.c:1223) [7320] Stopping service...
[2025-03-17 13:57:05] [debug] ( javajni.c:414 ) [7320] Loaded JVM DLL 'C:\Program Files\Elastic\Elasticsearch\elasticsearch-8.17.0\jdk\bin\server\jvm.dll', home '(null)'.
[2025-03-17 13:57:05] [debug] ( javajni.c:419 ) [7320] JNI_GetCreatedJavaVMs...
[2025-03-17 13:57:05] [debug] ( javajni.c:1062) [7620] Java worker thread started for org/elasticsearch/launcher/CliToolLauncher:close
[2025-03-17 13:57:05] [debug] ( javajni.c:1068) [7620] JNI calling static void method org/elasticsearch/launcher/CliToolLauncher:close
[2025-03-17 13:57:06] [debug] ( prunsrv.c:1273) [7320] Waiting for Java JNI stop worker to finish for org/elasticsearch/launcher/CliToolLauncher:close...
[2025-03-17 13:57:06] [debug] ( javajni.c:1157) [7320] apxJavaWait -> WaitForSingleObject (0x00000000000002AC, -1 milliseconds) (-1=INFINITE)...
[2025-03-17 13:57:19] [debug] ( javajni.c:1087) [7620] Java worker thread finished org/elasticsearch/launcher/CliToolLauncher:close with status = 0
[2025-03-17 13:57:19] [debug] ( prunsrv.c:1123) [5464] reportServiceStatusE: dwCurrentState = 3 (SERVICE_STOP_PENDING), dwWin32ExitCode = 0, dwWaitHint = 0 milliseconds, dwServiceSpecificExitCode = 0.
[2025-03-17 13:57:19] [debug] ( javajni.c:1160) [7320] apxJavaWait <- WaitForSingleObject (0x00000000000002AC, -1 milliseconds) = 0
[2025-03-17 13:57:19] [debug] ( prunsrv.c:1278) [7320] Java JNI stop worker finished.
[2025-03-17 13:57:19] [debug] ( prunsrv.c:1868) [5464] JVM destroyed.
[2025-03-17 13:57:19] [debug] ( prunsrv.c:1123) [5464] reportServiceStatusE: dwCurrentState = 1 (SERVICE_STOPPED), dwWin32ExitCode = 0, dwWaitHint = 0 milliseconds, dwServiceSpecificExitCode = 0.
[2025-03-17 13:57:19] [debug] ( prunsrv.c:1123) [7320] reportServiceStatusE: dwCurrentState = 3 (SERVICE_STOP_PENDING), dwWin32ExitCode = 0, dwWaitHint = 300000 milliseconds, dwServiceSpecificExitCode = 0.
[2025-03-17 13:57:19] [info] ( prunsrv.c:1908) [5956] Run service finished.
[2025-03-17 13:57:19] [error] ( prunsrv.c:1146) [7320] Failed to set service status.
[2025-03-17 13:57:19] [error] ( prunsrv.c:1146) [7320] The handle is invalid.
[2025-03-17 13:57:19] [debug] ( prunsrv.c:1386) [7320] Waiting for worker to die naturally...
[2025-03-17 13:57:19] [debug] ( prunsrv.c:1397) [7320] Worker finished gracefully in 0 milliseconds.
[2025-03-17 13:57:19] [info] ( prunsrv.c:1407) [7320] Service stop thread completed.
[2025-03-17 13:57:19] [info] ( prunsrv.c:2086) [5956] Apache Commons Daemon procrun finished.

```

Elastic is still running on all the server when I browse [http://server1:9200/](http://server1:9200/)

Any idea what this issues migth be?

Thanks!

/Kristoffer

---

<div class="post-metadata">

**Author:** ![mbooh](https://avatars.discourse-cdn.com/v4/letter/m/e495f1/32.png) [@mbooh](https://discuss.elastic.co/u/mbooh)\
**Post date:** [April 3, 2025, 7:00am UTC](https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183/2 "2025-04-03T07:00:15Z")

</div>

Hi!

Anyone? We still have this issue, any idea?

Thanks!

/Kristoffer

---

<div class="post-metadata">

**Author:** ![mbooh](https://avatars.discourse-cdn.com/v4/letter/m/e495f1/32.png) [@mbooh](https://discuss.elastic.co/u/mbooh)\
**Post date:** [April 27, 2025, 8:12am UTC](https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183/3 "2025-04-27T08:12:35Z")

</div>

Hi!

Here is an update.  
The error:

```auto

[2025-03-20 13:53:26] [info] ( prunsrv.c:1621) [3020] Service SERVICE_CONTROL_INTERROGATE signalled.

```

Only occurs if I run Elastic as a Windows Service. If I start it from the command prompt the error does not show in the log.

I have also upgraded to Elasticsearch 9.0.

Any thougths?

/Kristoffer

---

<div class="post-metadata">

**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\
**Post date:** [April 27, 2025, 1:44pm UTC](https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183/4 "2025-04-27T13:44:23Z")

</div>

Have you tried to remove the ES service, and install again?  
Stop the elasticsearch process. Run the commands:

```auto
bin\elasticsearch-service.bat remove ElasticSearch
bin\elasticsearch-service.bat install ElasticSearch
bin\elasticsearch-service.bat manager ElasticSearch

```

Check in services what is the correct name for Elasticsearch.

---

<div class="post-metadata">

**Author:** ![mbooh](https://avatars.discourse-cdn.com/v4/letter/m/e495f1/32.png) [@mbooh](https://discuss.elastic.co/u/mbooh)\
**Post date:** [April 28, 2025, 6:56am UTC](https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183/5 "2025-04-28T06:56:25Z")

</div>

Yes, I've done exactly that but still the same error, and it only occurs when Elastic is run as a Windows Service. If started from the command prompt, the error does not occur.

---

<div class="post-metadata">

**Author:** ![mbooh](https://avatars.discourse-cdn.com/v4/letter/m/e495f1/32.png) [@mbooh](https://discuss.elastic.co/u/mbooh)\
**Post date:** [April 28, 2025, 6:57am UTC](https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183/6 "2025-04-28T06:57:50Z")

</div>

```auto
[2025-04-28 08:52:07] [debug] ( javajni.c:419 ) [6384] JNI_GetCreatedJavaVMs...
[2025-04-28 08:52:07] [debug] ( javajni.c:817 ) [7972] JVM Option[0] -XX:+UseSerialGC
[2025-04-28 08:52:07] [debug] ( javajni.c:817 ) [7972] JVM Option[1] -Des.path.home=C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0
[2025-04-28 08:52:07] [debug] ( javajni.c:817 ) [7972] JVM Option[2] -Des.path.conf=C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0\config
[2025-04-28 08:52:07] [debug] ( javajni.c:817 ) [7972] JVM Option[3] -Des.distribution.type=zip
[2025-04-28 08:52:07] [debug] ( javajni.c:817 ) [7972] JVM Option[4] -Dcli.name=windows-service-daemon
[2025-04-28 08:52:07] [debug] ( javajni.c:817 ) [7972] JVM Option[5] -Dcli.libs=lib/tools/server-cli,lib/tools/windows-service-cli
[2025-04-28 08:52:07] [debug] ( javajni.c:817 ) [7972] JVM Option[6] -Djava.class.path=C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/ecs-logging-core-1.2.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/elasticsearch-9.0.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/elasticsearch-cli-9.0.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/elasticsearch-core-9.0.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/elasticsearch-entitlement-9.0.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/elasticsearch-geo-9.0.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/elasticsearch-grok-9.0.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/elasticsearch-log4j-9.0.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/elasticsearch-logging-9.0.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/elasticsearch-lz4-9.0.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/elasticsearch-native-9.0.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/elasticsearch-plugin-analysis-api-9.0.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/elasticsearch-plugin-api-9.0.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/elasticsearch-secure-sm-9.0.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/elasticsearch-simdvec-9.0.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/elasticsearch-tdigest-9.0.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/elasticsearch-x-content-9.0.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/HdrHistogram-2.1.9.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/hppc-0.8.1.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/jcodings-1.0.44.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/joni-2.1.29.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/jopt-simple-5.0.2.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/log4j-api-2.19.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/log4j2-ecs-layout-1.2.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/lucene-analysis-common-10.1.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/lucene-backward-codecs-10.1.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/lucene-core-10.1.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/lucene-facet-10.1.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/lucene-grouping-10.1.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/lucene-highlighter-10.1.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/lucene-join-10.1.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/lucene-memory-10.1.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/lucene-misc-10.1.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/lucene-queries-10.1.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/lucene-queryparser-10.1.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/lucene-sandbox-10.1.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/lucene-suggest-10.1.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/lz4-java-1.8.0.jar;C:\Program Files\Elastic\Elasticsearch\elasticsearch-9.0.0/lib/cli-launcher/cli-launcher-9.0.0.jar
[2025-04-28 08:52:07] [debug] ( javajni.c:817 ) [7972] JVM Option[7] exit
[2025-04-28 08:52:07] [debug] ( javajni.c:817 ) [7972] JVM Option[8] abort
[2025-04-28 08:52:07] [debug] ( javajni.c:1062) [7972] Java worker thread started for org/elasticsearch/launcher/CliToolLauncher:main
[2025-04-28 08:52:07] [debug] ( javajni.c:1068) [7972] JNI calling static void method org/elasticsearch/launcher/CliToolLauncher:main
[2025-04-28 08:52:08] [debug] ( prunsrv.c:1486) [6384] Java started 'org/elasticsearch/launcher/CliToolLauncher'.
[2025-04-28 08:52:08] [info] ( prunsrv.c:1585) [6384] Service started in 1383 milliseconds.
[2025-04-28 08:52:08] [debug] ( prunsrv.c:1123) [6384] reportServiceStatusE: dwCurrentState = 4 (SERVICE_RUNNING), dwWin32ExitCode = 0, dwWaitHint = 0 milliseconds, dwServiceSpecificExitCode = 0.
[2025-04-28 08:52:08] [debug] ( prunsrv.c:1832) [6384] Waiting for worker to finish...
[2025-04-28 08:52:08] [debug] ( javajni.c:1157) [6384] apxJavaWait -> WaitForSingleObject (0x00000000000002A8, -1 milliseconds) (-1=INFINITE)...
[2025-04-28 08:52:34] [debug] ( javajni.c:1087) [7972] Java worker thread finished org/elasticsearch/launcher/CliToolLauncher:main with status = 0
[2025-04-28 08:52:34] [debug] ( javajni.c:1160) [6384] apxJavaWait <- WaitForSingleObject (0x00000000000002A8, -1 milliseconds) = 0
[2025-04-28 08:52:34] [debug] ( prunsrv.c:1837) [6384] Worker finished.
[2025-04-28 08:52:34] [debug] ( prunsrv.c:1864) [6384] Waiting for all threads to exit.
[2025-04-28 08:52:42] [info] ( prunsrv.c:1621) [1008] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-04-28 08:52:42] [info] ( prunsrv.c:1621) [1008] Service SERVICE_CONTROL_INTERROGATE signalled.
[2025-04-28 08:53:42] [info] ( prunsrv.c:1621) [1008] Service SERVICE_CONTROL_INTERROGATE signalled.

```

---

<div class="post-metadata">

**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\
**Post date:** [April 28, 2025, 8:39am UTC](https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183/7 "2025-04-28T08:39:54Z")

</div>

> [@](#):
>
> [2025-04-28 08:52:08] [info] ( prunsrv.c:1585) [6384] Service started in 1383 milliseconds.

The service has been started. Others are info messages. Can you check does the process run on TCP 9200? Use netstat or curl to check

---

<div class="post-metadata">

**Author:** ![mbooh](https://avatars.discourse-cdn.com/v4/letter/m/e495f1/32.png) [@mbooh](https://discuss.elastic.co/u/mbooh)\
**Post date:** [April 28, 2025, 11:04am UTC](https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183/8 "2025-04-28T11:04:29Z")

</div>

Yes, the service is up and working just fine so maybe that info message is nothing to worry about?

---

<div class="post-metadata">

**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\
**Post date:** [April 28, 2025, 11:34am UTC](https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183/9 "2025-04-28T11:34:56Z")

</div>

If is working in the services mode, don't see any need to investigate. Maybe someone from Elastic team has more ideas about this.

---

<div class="post-metadata">

**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\
**Post date:** [April 28, 2025, 12:00pm UTC](https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183/10 "2025-04-28T12:00:53Z")

</div>

> [@mbooh](#):
>
> Yes, the service is up and working just fine so maybe that info message is nothing to worry about?

That's good to hear, but how does this square with earlier observation

> [@mbooh](#):
>
> we have **major issues** with Elastic. We **often** get timeout when doing a full reindex.

Are those issue also resolved?

---

<div class="post-metadata">

**Author:** ![mbooh](https://avatars.discourse-cdn.com/v4/letter/m/e495f1/32.png) [@mbooh](https://discuss.elastic.co/u/mbooh)\
**Post date:** [April 28, 2025, 12:35pm UTC](https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183/11 "2025-04-28T12:35:46Z")

</div>

Hi!

No, we still get the timeouts and I thought that the service info message might have something to do with it, perhaps that is not the case?

/Kristoffer

---

<div class="post-metadata">

**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\
**Post date:** [April 28, 2025, 3:09pm UTC](https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183/12 "2025-04-28T15:09:47Z")

</div>

Timeouts in the elastic log or from Kibana or app?

---

<div class="post-metadata">

**Author:** ![mbooh](https://avatars.discourse-cdn.com/v4/letter/m/e495f1/32.png) [@mbooh](https://discuss.elastic.co/u/mbooh)\
**Post date:** [April 28, 2025, 3:34pm UTC](https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183/13 "2025-04-28T15:34:31Z")

</div>

Timeout in the .net core application that calls Elastic

---

<div class="post-metadata">

**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\
**Post date:** [April 28, 2025, 9:09pm UTC](https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183/14 "2025-04-28T21:09:13Z")

</div>

You can follow next steps:

1. Run ES as service to be a stable. There should be a trace something like this  
`[2025-04-28T10:34:23,928][INFO][o.e.h.AbstractHttpServerTransport] [elk1] publish_address {192.168.1.111:9200}, bound_addresses {[::]:9200}`  
[2025-04-28T10:34:27,280][INFO][o.e.c.r.a.AllocationService] [elk1] current.health="YELLOW" message="Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[.ds-.logs-elasticsearch.deprecation-default-2025.04.17-000001][0]]])." previous.health="RED" reason="shards started [[.ds-.logs-elasticsearch.deprecation-default-2025.04.17-000001][0]]"

2. Run `elasticsearch-service.bat manager Elasticsearch`. Review "Java virtual Machine" and "Java Classpath",check are path correct.  
There was [a bug](https://discuss.elastic.co/t/not-entitled-component-repository-s3-after-update-from-8-17-4-to-8-18-0/377166/11) with the drive's capital letter on Windows, but I don't think is your case. Check and exclude a possibility.  
Check how the service does start, default is the account Local System account

3. Use curl to test ES APIs. Run it on every node, maybe one of them or index has an issue.  
GET '[http://server1:9200/\_cat/health](http://server1:9200/_cat/health)  
GET [http://server1:9200/\_cat/indices?bytes=b&s=store.size:desc&v&pretty](http://server1:9200/_cat/indices?bytes=b&s=store.size:desc&v&pretty)

4. Might be issues with the local firewall, check opened ports.

5. Set log level to info, not debug. It's flood the log and slow down.

6. Check do you have enough disk space. Reindexing is like index cloning + little bit additional space. How large are indices?

7. Can you copy more lines, instead of 1-2? The best option is from the start until a problem show up.You can put on gdrive or A similar location.

---

<div class="post-metadata">

**Author:** ![mbooh](https://avatars.discourse-cdn.com/v4/letter/m/e495f1/32.png) [@mbooh](https://discuss.elastic.co/u/mbooh)\
**Post date:** [April 30, 2025, 5:50am UTC](https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183/15 "2025-04-30T05:50:58Z")

</div>

Thanks for alla the tips, I will try them.

I can now confirm that the info message has to do with the server patch.  
This nigth our productions servers, who did not have the messages, was updated with the latest Windows Server patch and after restart the message started to appear in the logs.  
Not sure the message is a problem, just curious what is means?

/Kristoffer

---

<div class="post-metadata">

**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\
**Post date:** [April 30, 2025, 6:26am UTC](https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183/16 "2025-04-30T06:26:58Z")

</div>

> [@mbooh](#):
>
> `] [debug] (`

If you started servers in the debug mode, that might mean someone had changed the log level and after restart, changes were applied. Not sure how the node had been restarted, removing/adding the cluster with stopping services or simply restarted.  
Also might be on ES side, however ES use Java not .Net or simply something has been changed long time before restart, and after restart changes were applied. Might be Java, the env. settings, etc.

In any case, you can open [a new issue](https://github.com/elastic/elasticsearch/) with much more information than here.

---

<div class="post-metadata">

**Author:** ![mbooh](https://avatars.discourse-cdn.com/v4/letter/m/e495f1/32.png) [@mbooh](https://discuss.elastic.co/u/mbooh)\
**Post date:** [April 30, 2025, 12:11pm UTC](https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183/17 "2025-04-30T12:11:18Z")

</div>

Ok, I'll look into to open an issue.

These are the Windows patches:  
**KB5055519** | [April 8, 2025—KB5055519 (OS Build 17763.7136) - Microsoft Support](https://support.microsoft.com/en-us/topic/april-8-2025-kb5055519-os-build-17763-7136-417d1340-ce40-4d0b-98ac-637c0f6dca35)

**KB5055175** | [April 8, 2025-KB5055175 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10, version 1809 and Windows Server 2019 - Microsoft Support](https://support.microsoft.com/en-us/topic/april-8-2025-kb5055175-cumulative-update-for-net-framework-3-5-and-4-8-for-windows-10-version-1809-and-windows-server-2019-8d44fff8-49a4-4db7-ae4c-408c8b78bade)

/Kristoffer

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 28, 2025, 12:11pm UTC](https://discuss.elastic.co/t/problem-with-cluster-after-windows-server-patch/376183/18 "2025-05-28T12:11:28Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.