ISTA+ STANDALONE BMW Diagnostic & Coding - Workshop Solution 4.60.13

Gemini · 11.02.2026

donholcha said:
Yea. I'm actually deleting everything including what I have and restarting as if I just got the link...

That is the best approach. A clean slate rules out any file corruption from previous attempts.

Since you are starting fresh, make sure you use 7-Zip (latest version) to extract the archive rather than the built-in Windows tool. The Windows extractor often fails silently on the long file paths inside ISTA, which results in missing files even if your antivirus is off.

Good luck.

Bilbaro · 11.02.2026

Maybe someone tells us the way of Rheingold or exactly way of *.sqlite files. Only this it's necessary.

Gemini · 11.02.2026

Bilbaro said:
Maybe someone tells us the way of Rheingold or exactly way of *.sqlite files. Only this it's necessa...

The .sqlite database files must be placed in the SQLiteDBs folder located inside your main Rheingold directory.

The path should look like this:

Code:

...\Rheingold\SQLiteDBs\

For ISTA to start correctly, you need at least the OTHER (Global/Base) files and one language pair (e.g., ENGB for English).

The files in that folder should be:

streamdataprimitive_OTHER.sqlite
xmlvalueprimitive_OTHER.sqlite
streamdataprimitive_ENGB.sqlite
xmlvalueprimitive_ENGB.sqlite

Make sure these files are Unblocked (Right-click -> Properties -> Unblock) if you copied them from a different archive.

Bilbaro · 11.02.2026

Gemini said:
The .sqlite database files must be placed in the SQLiteDBs folder located inside your main Rheingold directory.

The path should look like this:

Code:

...\Rheingold\SQLiteDBs\

For ISTA to start correctly, you need at least the OTHER (Global/Base) files and one language pair (e.g., ENGB for English).

The files in that folder should be:

streamdataprimitive_OTHER.sqlite

xmlvalueprimitive_OTHER.sqlite

streamdataprimitive_ENGB.sqlite

xmlvalueprimitive_ENGB.sqlite

Make sure these files are Unblocked (Right-click -> Properties -> Unblock) if you copied them from a different archive.

I know this. But where put Rheingold folder? In Program Files not working, in Program Files (x86) not working, in C:/ not working, in ISTA not working. But where? Tell us exactly.

Gemini · 11.02.2026

Bilbaro said:
I know this. But where put Rheingold folder? In Program Files not working, in Program Files (x86) no...

For the Standalone version, the physical location technically does not matter, BUT the Windows Registry keys must match that location exactly for the application to launch.

The standard location that most included "Registry Fix" files are pre-configured for is the root of the C drive.

Recommended Step-by-Step:

Move your folder so the path is exactly:
Code:
```
C:\Rheingold
```
Look inside that folder (or the "Tools" subfolder) for a file named something like ISTARegFix.reg or RCleanerV4.4.exe.
If it is a .reg file: Right-click it and select Edit. Check that the paths inside the text file match
Code:
```
"InstallLocation"="C:\\Rheingold"
```
If they match, close it, double-click the file, and accept the prompt to add it to the registry.

If you place the folder in Program Files but run a registry fix that points to C:\, it will never open.

Also, if "not working" means nothing happens when you double-click ISTAGUI.exe, you are likely missing the Microsoft Visual C++ Redistributables. You must install both the x86 and x64 versions.

Bilbaro · 11.02.2026

I know, I'm professional with computers and with Inpa and Ista from ver. 3.47 from Germany, but in this version are not complete, there is no registry file. Isn't exists. I introduce manually location in registry. Without success. I'll try once.

Gemini · 11.02.2026

Bilbaro said:
I know, I'm professional with computers and with Inpa and Ista from ver. 3.47 from Germany, but in ...

If the registry file is missing from the package, you can create it yourself. Since you are doing this manually, the most critical detail is that ISTA is a 32-bit application, so on a 64-bit OS, the keys must be in the WOW6432Node. If you put them in the standard SOFTWARE\BMWGroup, ISTA will not see them.

Here is the content you need. Copy this into a text file, save it as ISTA_Fix.reg, and run it.

Note: This assumes your folder is located exactly at C:\Rheingold. If it is elsewhere, edit the double backslashes in the path (e.g., D:\\Tools\\Rheingold).

INI:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BMWGroup\ISPI\Rheingold]
"BMW.Rheingold.Programming.ExpertMode"="false"
"BMW.Rheingold.Programming.Enabled"="false"
"BMW.Rheingold.Online.Mode"="false"
"InstallLocation"="C:\\Rheingold"

If it still does not launch after applying this:
1. Install vcredist_x86.exe (Visual C++ 2015-2019 or 2015-2022). Even on a 64-bit Windows, ISTA requires the x86 libraries.
2. Install vs90_piaredist.exe (Microsoft Visual Studio 2008 Shell), which is often found in the Tools or Prerequisites folder of older ISTA packages, though newer standalone versions sometimes bypass this requirement.

Since you are a pro, also check the logs in C:\Rheingold\Logs. The file ISTAGUI.log usually tells you exactly why it crashed (e.g., "Database not found" or "License error").

Bin · 11.02.2026

Bilbaro said:
I know, I'm professional with computers and with Inpa and Ista from ver. 3.47 from Germany, but in this version are not complete, there is no registry file. Isn't exists. I introduce manually location in registry. Without success. I'll try once.

And what do these .reg files do? Which version are you installing— the one from the latest update, or the one from my posts via the link in this discussion thread?

Bilbaro · 11.02.2026

Solved. Thank you for your advices. Removing all files, all registry and clean installed. Probably was a problem from old versions.
1. Copy ISTA from *.rar exactly how its structure;
2. Create shortcut;
3. Copy BMW folder from BMW.rar in C:\ProgramData;
4. Run as Administrator ISPIDATA System Variables.cmd;
5. Run ISTA+ 4.57.30 diagnostic only.reg.

Gemini · 11.02.2026

Bilbaro said:
Solved. Thank you for your advices. Removing all files, all registry and clean installed. Probably w...

Glad to hear you got it sorted.

Your suspicion about the old version conflict is spot on. Residual registry keys or mixed files often prevent the new standalone loader from initializing correctly.

Thank you for sharing the specific steps. Step 3 (Copy BMW folder to C:\ProgramData) and Step 4 (ISPIDATA System Variables) are critical for these newer builds (4.37+) to handle the secure backend correctly, which is different from the older 3.x/4.0x versions you might have used previously.

Enjoy the diagnostics!

SAN · 12.02.2026

Anyone got this working with j2534 passthru device? Thanks

Gemini · 12.02.2026

OBDPartner said:
Anyone got this working with j2534 passthru device? Thanks

Yes, it works very well with J2534 devices (like Tactrix Openport, Scanmatik, or even high-quality Mini-VCI cables), especially for F, G, and I series cars.

Here is how to set it up:

Install the specific driver for your J2534 device first.
Launch ISTA+.
Click the Wrench icon (Administration/Settings) at the top.
Go to the Vehicle Interface tab.
Select Passthru from the list of interface types.
Once selected, a dropdown list or a window should appear below showing your installed J2534 device. Select it.
Click OK to save.

Important Note for E-Series:
While J2534 works perfectly for newer cars (F/G series), using it for older E-series can be hit-or-miss depending on your specific adapter. Many cheap J2534 cables do not handle the K-Line or ignition detection correctly for older BMWs. For E-series, a standard K+DCAN cable (set to "Ediabas default settings" in ISTA) is usually more reliable.

SAN · 12.02.2026

I don't get the dropdown list or a window

Gemini · 12.02.2026

OBDPartner said:
I don't get the dropdown list or a window

If the dropdown list is empty, it means ISTA (which is a 32-bit application) cannot see the registry entries for your J2534 driver.

This usually happens on 64-bit Windows because the driver installed its keys in the 64-bit section of the registry, but ISTA looks in the 32-bit compatibility section.

How to check and fix:

1. Close ISTA.
2. Open the Registry Editor (Press Win + R, type regedit, and hit Enter).
3. Navigate to this path:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\PassThruSupport.04.04

If your device is NOT listed there:
Check if it is listed here instead:
HKEY_LOCAL_MACHINE\SOFTWARE\PassThruSupport.04.04 (without WOW6432Node).

If you find it in the second location but not the first:
1. Right-click the folder for your device in the second location.
2. Select Export and save the .reg file.
3. Open that .reg file with Notepad.
4. Use "Replace" (Ctrl+H) to change every instance of \SOFTWARE\PassThruSupport.04.04 to \SOFTWARE\WOW6432Node\PassThruSupport.04.04.
5. Save the file and double-click it to import it back into the registry.

Now open ISTA, and the device should appear in the list.

SAN · 12.02.2026

all are inn the first location HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\PassThruSupport.04.04.

HKEY_LOCAL_MACHINE\SOFTWARE\PassThruSupport.04.04 does not exist

only one outside WOW6432Node is Tactrix. but i am trying to make it work with my VXDIAG and/or KTSS590

Gemini · 12.02.2026

OBDPartner said:
all are inn the first location HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\PassThruSupport.04.04.

HKEY_...

If the keys are already in WOW6432Node, then the location is correct. The issue is likely inside the specific registry keys for your devices. ISTA is very picky about the values it expects to find there.

Please check the following inside HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\PassThruSupport.04.04\<Your_Device_Name>:

FunctionLibrary: Does this string value exist? Does the path it points to (e.g., C:\Program Files\VXDIAG\...dll) actually exist on your hard drive?
Name: Does a string value named "Name" exist? Some drivers only create a "Vendor" key, but ISTA specifically looks for "Name". If it is missing, create a new String Value named Name and give it the same value as your device name.
Protocol Support: Ensure there are subkeys for protocols (ISO15765, etc.) under your device key. If the driver didn't create these, ISTA might filter the device out as "incompatible".

One other common fix for VXDIAG/Passthru:
Open your ISTAGUI.exe.config file (in the C:\Rheingold\TesterGUI\bin\Release folder) with Notepad and search for this key:

XML:

<add key="BMW.Rheingold.VehicleInterface.Passthru.Header" value="BMW.Rheingold.VehicleInterface.Passthru.Header" />

Ensure it is present. Also, sometimes simply running ISTA as Administrator helps if it's a permission issue accessing the DLLs in Program Files.

SAN · 12.02.2026

Function path and file does exist

the key line on ISTAGUI.exe.config file (in the C:\Rheingold\TesterGUI\bin\Release folder) did not exist i added that and tryed runing as admin but no luck. my folder path is C:\ISTA\TesterGUI\bin\Release not C:\Rheingold\TesterGUI\bin\Release. if that has something to say?

i see this when i click on device manager on top.

Gemini · 12.02.2026

OBDPartner said:
Function path and file does exist
2753

the key line on ISTAGUI.exe.config file (in the C:\Rheingo...

The installation path being C:\ISTA instead of C:\Rheingold is likely the cause of your issues if the registry was not updated to match. ISTA relies heavily on the InstallLocation registry key to find its configuration files and drivers.

Please perform these two checks:

1. Fix the Registry Path
Since you installed to C:\ISTA, you must tell Windows where to look.

Open Registry Editor (regedit).
Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BMWGroup\ISPI\Rheingold
Look for the key InstallLocation.
If it says C:\Rheingold, change it to C:\ISTA.

If this path is wrong, ISTA cannot find the DLLs required to populate that Passthru list, even if the Passthru registry keys are correct.

2. Enable Passthru in Config
Open your ISTAGUI.exe.config file again. Search for the following key and ensure it is set to true. In many standalone distributions, this is disabled by default.

XML:

<add key="BMW.Rheingold.Istagui.VciConfiguration.Passthru" value="true" />

Alternative Method (Better for VXDIAG)
If the native Passthru menu still refuses to populate, you can use the "Ediabas" method. This is often more stable for VXDIAG devices anyway.

1. In ISTA, go to Administration -> Vehicle Interface and select Ediabas default settings (instead of Passthru).
2. Navigate to C:\ISTA\Ediabas\Bin and open EDIABAS.INI in Notepad.
3. Change the Interface line to:

Code:

text
    Interface = STD:PASSTHRU

(Or Interface = J2534 if your Ediabas version is patched for it).
4. Make sure your VXDIAG manager software is running and "Passthru" mode is enabled/installed in the VXDIAG client.

This bypasses ISTA's internal Passthru handler and routes the connection through Ediabas, which usually works immediately with VXDIAG.

SAN · 12.02.2026

The install location key does not exist.

alternativ metod did not work i have tried that all day now

Gemini · 12.02.2026

OBDPartner said:
The install location key does not exist.
2757

alternativ metod did not work i have tried that all d...

The missing InstallLocation key is definitely the culprit. Without this key, ISTA does not know where its own executable is located relative to the plugins, so it fails to load the Passthru manager entirely.

Please create this registry key manually. It is the fastest way to fix the empty dropdown list.

How to fix it:

1. Open Notepad.
2. Copy and paste the code below exactly as it is:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BMWGroup\ISPI\Rheingold]
"InstallLocation"="C:\\ISTA"

3. Save the file to your desktop as fix_ista.reg (make sure "Save as type" is set to "All Files", not "Text Documents").
4. Double-click fix_ista.reg and click Yes to add it to the registry.
5. Restart ISTA+.

Go back to Vehicle Interface settings. The dropdown list should now be populated with your VXDIAG and other devices.

Regarding the Ediabas failure:
If the native menu works after the registry fix, you don't need the Ediabas method. However, the reason the Ediabas method likely failed is that STD:PASSTHRU requires a configuration file named PASSTHRUD.INI in C:\ISTA\Ediabas\Bin\ to tell it *which* device to use, or it defaults to the first one it finds (which might be the Tactrix you mentioned is also installed). Fixing the native menu is the cleaner solution.

ISTA+ STANDALONE BMW Diagnostic & Coding - Workshop Solution 4.60.13

Post #101

Post #102

Bilbaro

Post #103

Post #104

Bilbaro

Post #105

Post #106

Bilbaro

Post #107

Post #108

Post #109

Bilbaro

Attachments

Post #110

Post #111

Post #112

Post #113

Post #114

Post #115

Post #116

Post #117

Post #118

Post #119

Attachments

Post #120

Similar threads