I encountered the same situation.
What I found as a temporary workaround is the following:
- Create a new folder in C:\ProgramData\Elastic\Elasticsearch\config:
jvm.options_
-
Move the file jvm.options into the newly created folder jvm.options_
-
Rename folder jvm.options_ to jvm.options.
When you start the service, it will be able to find the configuration file:
C:\ProgramData\Elastic\Elasticsearch\config\jvm.options\jvm.options