# Elasticsearch.bat VS elasticsearch service

**URL:** <https://discuss.elastic.co/t/elasticsearch-bat-vs-elasticsearch-service/216653>\
**Category:** Elasticsearch\
**Created:** [January 27, 2020, 12:02pm UTC](https://discuss.elastic.co/t/elasticsearch-bat-vs-elasticsearch-service/216653 "2020-01-27T12:02:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![CesarPozo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cesarpozo/32/60608_2.png) [@CesarPozo](https://discuss.elastic.co/u/CesarPozo)\
**Post date:** [January 27, 2020, 12:02pm UTC](https://discuss.elastic.co/t/elasticsearch-bat-vs-elasticsearch-service/216653/1 "2020-01-27T12:02:30Z")

</div>

(For Windows) Is there any differences between run elasticsearch.bat and install the service elasticsearch-service.bat and start it?

I have read [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/zip-windows.html#windows-service) that:

"_Elasticsearch can be installed as a service to run in the background or start automatically at boot time without any user interaction_ "

Is that the only advantage? Because we could also do that with elasticsearch.bat by creating a new Task at the Windows Task Scheduler, right?

Thanks a million.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 24, 2020, 12:02pm UTC](https://discuss.elastic.co/t/elasticsearch-bat-vs-elasticsearch-service/216653/2 "2020-02-24T12:02:39Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.