# Elasticsearch service not working due to latest JRE update

**URL:** <https://discuss.elastic.co/t/elasticsearch-service-not-working-due-to-latest-jre-update/200648>\
**Category:** Elasticsearch\
**Created:** [September 23, 2019, 8:52am UTC](https://discuss.elastic.co/t/elasticsearch-service-not-working-due-to-latest-jre-update/200648 "2019-09-23T08:52:25Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mukul\_Vaidya](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mukul_vaidya/32/54712_2.png) [@Mukul\_Vaidya](https://discuss.elastic.co/u/Mukul_Vaidya)\
**Post date:** [September 23, 2019, 8:52am UTC](https://discuss.elastic.co/t/elasticsearch-service-not-working-due-to-latest-jre-update/200648/1 "2019-09-23T08:52:25Z")

</div>

[2019-09-23T14:16:48,815][WARN][o.e.b.ElasticsearchUncaughtExceptionHandler] [node-1] uncaught exception in thread [main]  
org.elasticsearch.bootstrap.StartupException: ElasticsearchException[X-Pack is not supported and Machine Learning is not available for [windows-x86]; you can use the other X-Pack features (unsupported) by setting xpack.ml.enabled: false in elasticsearch.yml]  
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:163) ~[elasticsearch-7.1.1.jar:7.1.1]  
at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:150) ~[elasticsearch-7.1.1.jar:7.1.1]  
at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) ~[elasticsearch-7.1.1.jar:7.1.1]  
at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124) ~[elasticsearch-cli-7.1.1.jar:7.1.1]  
at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-cli-7.1.1.jar:7.1.1]  
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:115) ~[elasticsearch-7.1.1.jar:7.1.1]  
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92) ~[elasticsearch-7.1.1.jar:7.1.1]  
Caused by: org.elasticsearch.ElasticsearchException: X-Pack is not supported and Machine Learning is not available for [windows-x86]; you can use the other X-Pack features (unsupported) by setting xpack.ml.enabled: false in elasticsearch.yml  
at org.elasticsearch.xpack.ml.MachineLearningFeatureSet.isRunningOnMlPlatform(MachineLearningFeatureSet.java:105) ~[?:?]  
at org.elasticsearch.xpack.ml.MachineLearningFeatureSet.isRunningOnMlPlatform(MachineLearningFeatureSet.java:96) ~[?:?]  
at org.elasticsearch.xpack.ml.MachineLearning.createComponents(MachineLearning.java:416) ~[?:?]  
at org.elasticsearch.node.Node.lambda$new$9(Node.java:440) ~[elasticsearch-7.1.1.jar:7.1.1]  
at java.util.stream.ReferencePipeline$7$1.accept(Unknown Source) ~[?:1.8.0\_212]  
at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(Unknown Source) ~[?:1.8.0\_212]  
at java.util.stream.AbstractPipeline.copyInto(Unknown Source) ~[?:1.8.0\_212]  
at java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source) ~[?:1.8.0\_212]  
at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(Unknown Source) ~[?:1.8.0\_212]  
at java.util.stream.AbstractPipeline.evaluate(Unknown Source) ~[?:1.8.0\_212]  
at java.util.stream.ReferencePipeline.collect(Unknown Source) ~[?:1.8.0\_212]  
at org.elasticsearch.node.Node.(Node.java:443) ~[elasticsearch-7.1.1.jar:7.1.1]  
at org.elasticsearch.node.Node.(Node.java:252) ~[elasticsearch-7.1.1.jar:7.1.1]  
at org.elasticsearch.bootstrap.Bootstrap$5.(Bootstrap.java:211) ~[elasticsearch-7.1.1.jar:7.1.1]  
at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:211) ~[elasticsearch-7.1.1.jar:7.1.1]  
at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:325) ~[elasticsearch-7.1.1.jar:7.1.1]  
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:159) ~[elasticsearch-7.1.1.jar:7.1.1]

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 23, 2019, 9:03am UTC](https://discuss.elastic.co/t/elasticsearch-service-not-working-due-to-latest-jre-update/200648/2 "2019-09-23T09:03:22Z")

</div>

You need to use 64-bit Java.

---

<div class="post-metadata">

**Author:** ![Mukul\_Vaidya](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mukul_vaidya/32/54712_2.png) [@Mukul\_Vaidya](https://discuss.elastic.co/u/Mukul_Vaidya)\
**Post date:** [September 23, 2019, 9:17am UTC](https://discuss.elastic.co/t/elasticsearch-service-not-working-due-to-latest-jre-update/200648/3 "2019-09-23T09:17:41Z")

</div>

Hi Chiristian,  
The current JRE update that we have received is 64 bit one only.

PFA ![Untitled](https://us1.discourse-cdn.com/elastic/original/3X/3/b/3b1bdb788c36deb0e8867031a144e10265111dc6.png)

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 23, 2019, 9:19am UTC](https://discuss.elastic.co/t/elasticsearch-service-not-working-due-to-latest-jre-update/200648/4 "2019-09-23T09:19:26Z")

</div>

Are you running on a 64-bit OS?

---

<div class="post-metadata">

**Author:** ![Mukul\_Vaidya](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mukul_vaidya/32/54712_2.png) [@Mukul\_Vaidya](https://discuss.elastic.co/u/Mukul_Vaidya)\
**Post date:** [September 23, 2019, 11:29am UTC](https://discuss.elastic.co/t/elasticsearch-service-not-working-due-to-latest-jre-update/200648/5 "2019-09-23T11:29:13Z")

</div>

Yes we are running on 64 bit OS win 10

---

<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:** [October 21, 2019, 11:29am UTC](https://discuss.elastic.co/t/elasticsearch-service-not-working-due-to-latest-jre-update/200648/6 "2019-10-21T11:29:20Z")

</div>

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