<!-- ** Please read the guidelines below. ** Issues that do not follow these guidelines are likely to be closed. GitHub is reserved for bug reports and feature requests. The best place to ask a general question is at the Elastic forums: https://discuss.elastic.co/c/elasticsearch GitHub is not the place for general questions. Documentation for the Elasticsearch Windows Installer can be found at https://www.elastic.co/guide/en/elasticsearch/reference/current/windows.html Be sure to select the documentation version relevant to the installer version you are using. ### Failed Installations If you are reporting an issue that occurred during installation, we ask that you attach the installation log file to your issue to help diagnose the root cause. When installing using the UI, a link to the log file will be provided at the end of a failed installation. If you have already closed the UI, the log file can be found in the %TEMP% directory with a randomly generated name adhering to the format MSI<random>.LOG. It should be the most recent log file. When installing from the command-line, the log file can be captured by passing the /l*v <logfilename> flag as per the documentation: https://www.elastic.co/guide/en/elasticsearch/reference/current/windows.html#install-msi-command-line --> ### Environment <!-- Are you running behind a corporate proxy? --> <!-- Where are you based geographically? --> ### Expected Behaviour ### Actual Behaviour ### Steps to reproduce the behaviour <!-- Is this a fresh install or an upgrade --> 1. 2. 3. <!-- attach any screenshots that may help --> [MSI72f8b.LOG](https://github.com/elastic/windows-installers/files/8103006/MSI72f8b.LOG)
Environment
Expected Behaviour
Actual Behaviour
Steps to reproduce the behaviour
MSI72f8b.LOG