> For the complete documentation index, see [llms.txt](https://docs.innova-drilling.com/introduction/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.innova-drilling.com/introduction/generic-documents/innova-generic-documents/installing-updates.md).

# Installing Updates

A guide to installing updates in Well Seeker Pro and Innova Engineering

Occasionally there may be the requirement to update your software. This could be due to the addition of new features or it could be to deal with any bugs that have been discovered and fixed. Updating your software is an easy process which is detailed in the instructions below.

* To begin with, ensure that the relevant program is closed.
* You will receive an update file via email
* * **Well Seeker.xxx (for Well Seeker)**
* * **Innova Engineering.xxx (for Engineering)**
* Save the file to either a designated folder somewhere in your C drive, or the desktop.
* Go to the file and change the file extension from .xxx to .exe
* Firstly, make sure that the file extensions are visible (if they are go to step 4).
* In Windows 10, go to File Explorer and in the View Tab, select File Name Extensions
* For older versions of windows, go to My Computer, in the Tools menu click Folder Options and select the View Tab. In the Advanced Settings box, click to clear the hide extensions for known file types check box.
* Right click the file and select rename. Change the now visible file extension.
* You will see the warning box displayed below. Select Yes.

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-McEwHTOM_v4MexTVGSe%2F-MfmCs69_1Y_wx6bMI03%2F-MfmLcfN0lBKzTwMtCKN%2F1.PNG?alt=media\&token=7fea3783-2c8b-431b-8c4a-c23b4f6be644)

* **This is important, because if the file extension is not changed, then the file will not work.**

For **Well Seeker Pro:**

* Place the **Well Seeker.exe** file in the Well Seeker Pro folder (most common directory path detailed below)
  * *C:\Program Files (x86)\Innova Drilling and Intervention\Well Seeker PRO*
  * There will already be a file of the same name in this folder. Overwrite this file with the new one
  * ***Before overwriting, make a copy of this file (save it to a different folder) which can then be used as a temporary backup in case there are any issues with the new file.***

For **Innova Engineering**:

* Place the **Innova Engineering.exe** file in the Innova Engineering folder (most common directory path detailed below)
  * *C:\Program Files (x86)\Innova Drilling and Intervention\Innova Engineering*
  * There will already be a file of the same name in this folder. Overwrite this file with the new one
  * ***Before overwriting, make a copy of this file (save it to a different folder) which can then be used as a temporary backup in case there are any issues with the new file.***

You have now installed the latest update and can open and run the programs as usual.

**If you experience any issues during this process please contact <sales@innova-drilling.com> for support.**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.innova-drilling.com/introduction/generic-documents/innova-generic-documents/installing-updates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
