Unknown-setting-cluster-initial-master-nodes error in ES 7.6.2

[fstewart]

According to the discussion and breaking doc in this post, ES 7.x should recognize the setting cluster.initial_master_nodes.

Here's the yml after installing ES 7.6.2 on Windows 7:

bootstrap.memory_lock: true
cluster.initial_master_nodes:
  - NEWUSER-PC
cluster.name: elasticsearch
http.port: 9200
node.data: true
node.ingest: true
node.master: true
node.max_local_storage_nodes: 1
node.name: NEWUSER-PC
path.data: C:\ProgramData\Elastic\Elasticsearch\data
path.logs: C:\ProgramData\Elastic\Elasticsearch\logs
transport.tcp.port: 9300
xpack.license.self_generated.type: basic
xpack.security.enabled: false

Here's the exception logged after running elasticsearch.bat to start the service:

Exception
java.lang.IllegalArgumentException: **unknown setting [cluster.initial_master_nodes.0]** please check that any required plugins are installed, or check the breaking changes documentation for removed settings
	at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:293) ~[elasticsearch-6.0.0-rc1.jar:6.0.0-rc1]

I notice the es jar version is 6.0.0. Which version number is in question?

UPDATE:

changed setting to:

discovery.zen.ping.unicast.hosts: ["NEWUSER-PC"]

but still get

Exception
java.lang.IllegalArgumentException: unknown setting [cluster.initial_master_nodes.0] please check that any required plugins are installed, or check the breaking changes documentation for removed settings

If the service startup is not reading the setting from the yml, how do I modify it so the service can start?

[Christian_Dahlqvist]

It seems you are running Elasticsearch 6.0 and not 7.6, which is why the new ly added settings are not valid.

[fstewart]

See UPDATE. I tried the v6 setting but got same error which indicates the setting isn't being read from the yml. Thoughts as to what's going on?

NOTE: I used the Windows download for ES v 7.6.2. This generated the yml with the problem setting, which I changed to comply with v6.0 but the problem persisted.