# Elasticsearch 6.8 Windows .msi upgrade from 6.8.2 to 6.8.20, using a service

**URL:** <https://discuss.elastic.co/t/elasticsearch-6-8-windows-msi-upgrade-from-6-8-2-to-6-8-20-using-a-service/289126>\
**Category:** Elasticsearch\
**Tags:** windows-installer\
**Created:** [November 13, 2021, 9:10pm UTC](https://discuss.elastic.co/t/elasticsearch-6-8-windows-msi-upgrade-from-6-8-2-to-6-8-20-using-a-service/289126 "2021-11-13T21:10:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![newschapmj1](https://avatars.discourse-cdn.com/v4/letter/n/dbc845/32.png) [@newschapmj1](https://discuss.elastic.co/u/newschapmj1)\
**Post date:** [November 13, 2021, 9:10pm UTC](https://discuss.elastic.co/t/elasticsearch-6-8-windows-msi-upgrade-from-6-8-2-to-6-8-20-using-a-service/289126/1 "2021-11-13T21:10:07Z")

</div>

We are patching a single node cluster from 6.8.2 to 6.8.20 on Windows server 2012 R2.  
The original version was installed with .msi

I have only had experience using the .zip file previously on Windows  
I've read the notes here: [Install Elasticsearch with Windows MSI Installer | Elasticsearch Guide [6.8] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/6.8/windows.html)

I'm not planning to uninstall the old Elasticsearch.

I'm planning on keeping the CONFIG, DATA AND LOGS folder the same and only change the INSTALL directory from 6.8.2 to 6.8.20

I will stop the service before installation.  
How does the .msi cope with the existing service?  
Does it create a new service with a different name and keep the old one intact?

---

<div class="post-metadata">

**Author:** ![newschapmj1](https://avatars.discourse-cdn.com/v4/letter/n/dbc845/32.png) [@newschapmj1](https://discuss.elastic.co/u/newschapmj1)\
**Post date:** [November 14, 2021, 5:42pm UTC](https://discuss.elastic.co/t/elasticsearch-6-8-windows-msi-upgrade-from-6-8-2-to-6-8-20-using-a-service/289126/2 "2021-11-14T17:42:55Z")

</div>

The msi did a good job of detecting my existing installation and replacing the existing service.  
e:\program files\Elasticsearch\6.8.2 contained my old version  
Running the .msi file it automatiically installed into  
e:\program files\Elasticsearch\6.8.20

It detected the Ingest Attachment Processor plugin installed in v6.8.2 and upgraded it

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/2/72484ae0f4b50fad764ae88226a3208ff7dbd39b.png)  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/1/313262524b38e8b95f32290429bd5cbe8a2c7604.png)  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/c/4cd5c9b2d2a60e405ff29af33487aca996813d99.png)  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/b/5b48a567a2a8ea8b81686fa9713e481a2e20c546.png)

---

<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:** [December 12, 2021, 5:43pm UTC](https://discuss.elastic.co/t/elasticsearch-6-8-windows-msi-upgrade-from-6-8-2-to-6-8-20-using-a-service/289126/3 "2021-12-12T17:43:43Z")

</div>

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