# Elasticsearch doesn't find bundled JDK **URL:** \ **Category:** Elasticsearch\ **Created:** [June 22, 2019, 4:21pm UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-find-bundled-jdk/186962 "2019-06-22T16:21:26Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![dandago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dandago/32/56215_2.png) [@dandago](https://discuss.elastic.co/u/dandago)\ **Post date:** [June 22, 2019, 4:21pm UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-find-bundled-jdk/186962/1 "2019-06-22T16:21:26Z")
I've just downloaded Elasticsearch 7.1.1 and am trying it out on Windows 10. Just today I learned that 7.0+ comes with a bundled JDK, so I decided to give it a try without setting JAVA\_HOME. However, it cannot find the JDK at the directory where it actually exists: ``` C:\tools\elasticsearch-7.1.1\bin>dir C:\tools\elasticsearch-7.1.1\jdk Volume in drive C is [redacted] Volume Serial Number is [redacted] Directory of C:\tools\elasticsearch-7.1.1\jdk 05/23/2019 02:13 PM . 05/23/2019 02:13 PM .. 05/23/2019 02:12 PM bin 05/23/2019 02:12 PM conf 05/23/2019 02:12 PM include 05/23/2019 02:12 PM jmods 05/23/2019 02:12 PM legal 05/23/2019 02:12 PM lib 05/23/2019 02:12 PM 1,217 release 1 File(s) 1,217 bytes 8 Dir(s) 643,659,010,048 bytes free C:\tools\elasticsearch-7.1.1\bin>elasticsearch.bat "could not find java in JAVA_HOME or bundled at C:\tools\elasticsearch-7.1.1\jdk" C:\tools\elasticsearch-7.1.1\bin> ``` It does work if I set JAVA\_HOME to that same jdk directory, so I'm wondering whether this may be a bug. ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [June 24, 2019, 10:34am UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-find-bundled-jdk/186962/2 "2019-06-24T10:34:52Z")
Hey, can you tell us, which file you exactly downloaded from which URL in addition? --Alex ---
**Author:** ![dandago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dandago/32/56215_2.png) [@dandago](https://discuss.elastic.co/u/dandago)\ **Post date:** [June 24, 2019, 7:40pm UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-find-bundled-jdk/186962/3 "2019-06-24T19:40:11Z")
Just the one on the download page, see below. What's strange is that I downloaded this on my work laptop today and did not get the same problem. It's different hardware and never had the JDK or Elasticsearch on it, unlike my home laptop which had the problem. ![elastic-download-windows](https://us1.discourse-cdn.com/elastic/original/3X/9/b/9b9bd969850532c26e17979277a48e1ed93a5108.png) ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [June 26, 2019, 6:28am UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-find-bundled-jdk/186962/4 "2019-06-26T06:28:14Z")
would you mind opening a github issue with the above information? especially being detailed about what setup works and what does not? Thanks a lot! ---
**Author:** ![dandago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dandago/32/56215_2.png) [@dandago](https://discuss.elastic.co/u/dandago)\ **Post date:** [July 9, 2019, 8:25pm UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-find-bundled-jdk/186962/5 "2019-07-09T20:25:24Z")
Sorry for the delay, I've done that and here's the [issue](https://github.com/elastic/elasticsearch/issues/44139). I'd like to provide more detail but I'm not sure what more I can provide that will help reproduce the problem. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 6, 2019, 8:25pm UTC](https://discuss.elastic.co/t/elasticsearch-doesnt-find-bundled-jdk/186962/6 "2019-08-06T20:25:24Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.