# Elasticsearch 7.2.0 MSI installer - Bundled Java cannot be deployed **URL:** \ **Category:** Elasticsearch\ **Created:** [July 11, 2019, 2:02pm UTC](https://discuss.elastic.co/t/elasticsearch-7-2-0-msi-installer-bundled-java-cannot-be-deployed/190032 "2019-07-11T14:02:09Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![mailcube](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mailcube/32/49902_2.png) [@mailcube](https://discuss.elastic.co/u/mailcube)\ **Post date:** [July 11, 2019, 2:02pm UTC](https://discuss.elastic.co/t/elasticsearch-7-2-0-msi-installer-bundled-java-cannot-be-deployed/190032/1 "2019-07-11T14:02:10Z")
Hi all, We are in the midst of deploying a new Elasticsearch instance on different workstations on VMs and noticed that, even though the documentation mentions that the installer is bundled with a OpenJDK package (see [https://www.elastic.co/guide/en/elasticsearch/reference/7.2/windows.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.2/windows.html)), it is impossible through the MSI to deploy a Elasticsearch instance on a machine that does not have a valid Java installation. This seems like a chicken and the egg problem where the installer "could" deploy a Java VM with the installer (and it does have the JDK in its files), but a check is done as the prerequisite to ensure Java is already deployed. Is this intended, is there a workaround or simply a remaining bug from when no bundled JVM was available inside the MSI package? Kind regards, Michael ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 8, 2019, 2:02pm UTC](https://discuss.elastic.co/t/elasticsearch-7-2-0-msi-installer-bundled-java-cannot-be-deployed/190032/2 "2019-08-08T14:02:12Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.