[Red_bean_bun]

Just curious - if both sets of applications have their own Ediabas - why would ISTA be making calls to ST’s Ediabas ?

Does ISTA use the environment path to ediabas.ini as well ?

Since not everyone has problems with the new version, I think it's because not everyone installs a second version of Ediabas, e.g. with StandardTools. The problem exists because two different versions of Ediabas(v7.3.0 in StandardTools and v7.6.0 in ISTA) apparently lead to problems in ISTA. This situation cannot happen in a BMW workshop because only ISTA is installed there, which is why no one at BMW will have noticed it.

The problem is easy to solve, just delete/move/rename the ediabas.ini from C:\ec-apps\ediabas\bin.

Another option(not tested) is to copy the new Ediabas from "C:\Program Files (x86)\BMW\ISPI\TRIC\ISTA\Ediabas\BIN" to "C:\ec-apps\ediabas\bin". Of course, you first have to test whether all old tools such as INPA still work.

Other solutions welcome.

Edit:
Ok, after research with several users i can say that only one option for those who have problems with slow ISTA exist, you have to copy all files from "C:\Program Files (x86)\BMW\ISPI\TRIC\ISTA\Ediabas\BIN" to "C:\ec-apps\ediabas\bin" or "C:\ediabas\bin" depend on your installation. After that, INPA should also work, you may have to adjust the ediabas.ini a little, e.g. enter the IP of the car directly instead of autodetect(only if don't work). Check also paths.

---

You can delete the Ediabas folder, perform a Format C://,
or simply remove the entry in the environment variables

https://cartechnology.co.uk/attachment.php?aid=186115

So this environment variable is used by both ISTA and Standard Tools ?