Updated cluster config does not contain myself. Rejecting

I tried to start a fresh cluster under Windows 10 with ArangoDB 3.3.10. I forgot to shutdown the ArangoDB service (local instance) that runs on 8529 on my system in the background. So what happened was that one arangodb starter process kept failing and telling me about a problem with the port 8529 being in use. Two other instances were patiently waiting it seemed.

The 4th starter process however, which I started very shortly after the 3rd (<1s) keeps failing in the terminal, but in the web UI everything seems to be alright:

Even if I Ctrl+C to stop the 4th starter process and run it again with the problem persists:

C:\Demo>ArangoDB\usr\bin\arangodb.exe --starter.join 127.0.0.1 --starter.data-dir db4
2018/06/20 15:40:35 Starting arangodb version 0.11.3, build 5c2faa9
2018/06/20 15:40:35 Relaunching service with id 'b1aa9524' on :8528...
2018/06/20 15:40:35 ArangoDB Starter listening on 0.0.0.0:8558 (:8558)
2018/06/20 15:40:35 Looking for a running instance of dbserver on port 8560
2018/06/20 15:40:35 Starting dbserver on port 8560
2018/06/20 15:40:35 Updated cluster config does not contain myself. Rejecting
2018/06/20 15:40:35 Updated cluster config does not contain myself. Rejecting
2018/06/20 15:40:36 Looking for a running instance of coordinator on port 8559
2018/06/20 15:40:36 Starting coordinator on port 8559
2018/06/20 15:40:36 dbserver up and running (version 3.3.10).
2018/06/20 15:40:37 coordinator up and running (version 3.3.10).
2018/06/20 15:40:37 Your cluster can now be accessed with a browser at `http://localhost:8559` or
2018/06/20 15:40:37 using `arangosh --server.endpoint tcp://localhost:8559`.
2018/06/20 15:40:45 Updated cluster config does not contain myself. Rejecting

Removed all data created by the starter, then tried again and it worked with 4 nodes in terminal and web ui.

arangodb-helper / arangodb

Updated cluster config does not contain myself. Rejecting #163