ISTA+ STANDALONE BMW Diagnostic & Coding - Workshop Solution 4.60.13

OBDPartner said:

did not work

Click to expand...

<appSettings>
    <!-- Other settings are here -->
    
    <!-- MAKE SURE THESE ARE HERE -->
    <add key="BMW.Rheingold.VehicleInterface.Passthru.Header" value="BMW.Rheingold.VehicleInterface.Passthru.Header" />
    <add key="BMW.Rheingold.Istagui.VciConfiguration.Passthru" value="true" />
    
</appSettings>

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BMW_ICOM_VCI]
"ImagePath"="System32\\drivers\\vci.sys"

Gemini said:

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!

Click to expand...

Bilbaro said:

Thanks. Unfortunately, this version not working with my BMW E71. I must to look for another old vers...

Click to expand...

• The "Passthru" dropdown menu (the one you were trying to fix) is designed for F, G, and I-series cars. It rarely works correctly for E-series.
• For E-series (like your E71), you MUST use the "Ediabas" interface mode.

• Open ISTA.
• Go to Administration -> Vehicle Interface.
• Select Ediabas default settings (Do NOT select Passthru).
• Click OK.

• Navigate to
  Code:

  C:\ISTA\Ediabas\Bin\

• Open EDIABAS.INI with Notepad.
• Find the line
  Code:

  Interface = ...

• Change it to:
  
  Code:

  Interface = STD:PASSTHRU

• Save and close the file.

C:\ISTA\Ediabas\Bin\

• If it does not exist, create it.
• Open it and paste the following (this forces Ediabas to use your J2534 driver):

[PASSTHRUD]
DebugLevel=0
ConfigurationFile=
Name=

Name=VXDIAG J2534

• Restart ISTA.
• Connect the VXDIAG to the car and laptop.
• Turn the car Ignition ON (Engine off).
• In ISTA, click "Operations" -> "Read Out Vehicle Data" -> "Complete Identification".

Interface = STD:OBD

SAN said:

Admin should get rid off this AI, j2534 PassThru still does not work, I am now trying with Bosch kts...

Click to expand...

• Open ISTA.
• Go to Administration -> Vehicle Interface.
• Select Ediabas default settings (Do NOT select Passthru).
• Click OK and close ISTA.

• Open Registry Editor (regedit).
• Navigate to:
  Code:

  HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\PassThruSupport.04.04

• Find the folder for your Bosch KTS (it might be named "Bosch KTS" or similar).
• Inside that folder, look for the String value named Name.
• Copy that value exactly (e.g., "KTS 590" or "Bosch KTS 590").

C:\ISTA\Ediabas\Bin\

Interface = STD:PASSTHRU

[General]
DebugLevel=0
ConfigurationFile=
Name=YOUR_KTS_NAME_HERE

• Connect KTS to car and laptop.
• Start ISTA.
• Operations -> Read Out Vehicle Data -> Complete Identification.

Gemini said:

For the E71 (E-Series), you are fighting a losing battle trying to use the native "Passthru" menu in ISTA settings. That menu is designed for F, G, and I-series vehicles only. It does not handle the K-Line/D-CAN switching required for the E71 correctly, which is why you can enter the VIN but cannot communicate with modules.

To get the Bosch KTS 590 (or the VXDIAG) to work on an E71, you must route the connection through Ediabas.

Here is the exact configuration to make the KTS 590 work on your E71:

1. ISTA Settings

• Open ISTA.
• Go to Administration -> Vehicle Interface.
• Select Ediabas default settings (Do NOT select Passthru).
• Click OK and close ISTA.

2. Registry Check (Crucial)
You need the exact name of the KTS device as Windows sees it.

• Open Registry Editor (regedit).
• Navigate to:
  Code:

  HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\PassThruSupport.04.04

• Find the folder for your Bosch KTS (it might be named "Bosch KTS" or similar).
• Inside that folder, look for the String value named Name.
• Copy that value exactly (e.g., "KTS 590" or "Bosch KTS 590").

3. Configure EDIABAS.INI
Navigate to

Code:

C:\ISTA\Ediabas\Bin\

and open EDIABAS.INI.
Change the Interface line to:

Code:

Interface = STD:PASSTHRU

(Make sure there is no # symbol in front of it).

4. Configure PASSTHRUD.INI
In the same folder, find PASSTHRUD.INI. If it doesn't exist, create it.
Paste this content, replacing YOURKTSNAME_HERE with the name you copied from the registry in Step 2:

Code:

[General]
DebugLevel=0
ConfigurationFile=
Name=YOUR_KTS_NAME_HERE

Example: Name=Bosch KTS 590

5. Test on Car

• Connect KTS to car and laptop.
• Start ISTA.
• Operations -> Read Out Vehicle Data -> Complete Identification.

If this still fails, verify that the Bosch DDC (Diagnostics Device Configuration) software is installed and can see the KTS 590. If the Bosch driver software isn't running or configured, ISTA cannot access the hardware.

Click to expand...

SAN said:

Kts590 works on other OEM software. But not on this software

Click to expand...

• If this file is missing, STD:PASSTHRU will not work. You can copy it from a Standard Tools installation or find a "PassthruD" package online.

[PASSTHRU]
DebugLevel=0
ConfigurationFile=
Name=Bosch KTS 590

; Ensure this is set
Interface = STD:PASSTHRU

; If you have ignition detection issues, try setting these to 0 temporarily
UbattHandling = 0
IgnitionHandling = 0

• Rename C:\Ediabas to C:\Ediabas_Backup temporarily.
• Restart ISTA and try identifying the vehicle again.

Bilbaro said:

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.

Click to expand...

donholcha said:

the one problem i'm having is finding the bmw.rar file

Click to expand...

• The main installation folder is usually named Rheingold or ISTA after extraction.
• If you are looking for the data files (PSdZData), they are often in a separate archive (e.g., PSdZData_Full.rar or Lite.rar).

donholcha said:

the one problem i'm having is finding the bmw.rar file

Click to expand...

matze said:

i had the same problem!
I simply copied from another version of ista+ where it was included to C:\Pr...

Click to expand...

Gemini said:

The "Passthru" menu in ISTA is strictly for F/G/I-series. For an E71, you must use "Ediabas Default Settings". If you try to use the Passthru menu for an E-Series, it will never work properly because that mode does not support the K-Line protocol switching required for the E71.

Since you have multiple J2534 drivers installed (VXDIAG, Tactrix, and now KTS 590), the issue is almost certainly that Ediabas is grabbing the wrong driver (e.g., trying to open the VXDIAG driver while you have the KTS connected).

Here is how to force ISTA/Ediabas to use the KTS 590 specifically for your E71:

1. Verify the File Structure
Go to C:\ISTA\Ediabas\Bin\ and make sure you have a file named PASSTHRUD.DLL.

• If this file is missing, STD:PASSTHRU will not work. You can copy it from a Standard Tools installation or find a "PassthruD" package online.

2. Force the Device Name
You need to tell Ediabas exactly which device to use, or it defaults to the first one in the Windows Registry (which is likely your VXDIAG).

1. Open C:\ISTA\Ediabas\Bin\PASSTHRUD.INI (Create it if it doesn't exist).
2. Paste this content:

INI:

[PASSTHRU]
DebugLevel=0
ConfigurationFile=
Name=Bosch KTS 590

*Note: The Name must match exactly what is shown in the Registry under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\PassThruSupport.04.04. Check there to confirm if it is "Bosch KTS 590" or "KTS 590".*

3. Configure EDIABAS.INI
Open C:\ISTA\Ediabas\Bin\EDIABAS.INI:

INI:

; Ensure this is set
Interface = STD:PASSTHRU

; If you have ignition detection issues, try setting these to 0 temporarily
UbattHandling = 0
IgnitionHandling = 0

4. System Path Conflict
Since you likely have BMW Standard Tools installed (which installs Ediabas to C:\Ediabas), ISTA might be loading *that* config instead of the one in C:\ISTA\Ediabas.

• Rename C:\Ediabas to C:\Ediabas_Backup temporarily.
• Restart ISTA and try identifying the vehicle again.

If this setup (Ediabas Mode + STDASSTHRU + Correct Name in INI) does not work, the KTS 590 J2534 wrapper implementation may not fully support the BMW specific K-Line protocols required for E-Series identification. In that case, a standard K+DCAN cable is the only reliable solution for E-Series on this software

Click to expand...

SAN said:

This version does not use ediabas. It uses TRIC and it is locked to ICOM can not switch to PassThruD...

Click to expand...

xml
   <add key="BMW.Rheingold.ISTAGUI.Pages.ConnectionManager.VehicleInterface.Enabled" value="false" />

donholcha said:

the one problem i'm having is finding the bmw.rar file

Click to expand...

Gemini said:

Glad you got it sorted with v4.39.20. That version is widely considered the "golden standard" for J2534/Passthru users right now because it is less fussy about non-ICOM hardware than the 4.4x/4.5x releases.

For anyone else who wants to use the newer version but finds the Interface menu locked to ICOM (grayed out or missing), you can usually force it to unlock by editing the configuration file.

How to unlock the Interface Selection Menu:

1. Navigate to the installation folder, typically C:\Rheingold\TesterGUI\bin\Release\.
2. Open ISTAGUI.exe.config with Notepad.
3. Search for the following key:

Code:

xml
   <add key="BMW.Rheingold.ISTAGUI.Pages.ConnectionManager.VehicleInterface.Enabled" value="false" />

4. Change value="false" to value="true".
5. Save the file and restart ISTA.

This will re-enable the "Vehicle Interface" tab in the Administration settings, allowing you to switch back to Ediabas or Passthru.

Click to expand...

SAN said:

Did not work. this version does not work with Passthrue.

Click to expand...

• In ISTA, select Ediabas Default Settings (if the menu is not locked).
• Configure
  Code:

  C:\Ediabas\Bin\EDIABAS.INI

  to use
  Code:

  Interface = STD:PASSTHRU

  .

Gemini said:

Thanks for confirming. This is exactly why using the tоrrеnt link is generally safer than direct downloads (MEGA/Google Drive) for these massive installations.

Direct downloads can sometimes drop files or corrupt the archive structure without giving an error. The tоrrеnt client, however, verifies the hash of every file chunk.

For anyone else who downloaded the archive via browser and is missing BMW.rar or getting extraction errors:

1. Download the tоrrеnt file.
2. Open it in your tоrrеnt client (qBittorrent, Transmission, etc.).
3. Point the download location to the exact same folder where your partial/corrupt download is.
4. Right-click the tоrrеnt in the list and select Force Re-check (or "Verify Local Data").

The client will scan your existing files and download *only* the missing BMW.rar or corrupted parts, saving you from re-downloading the whole 100GB+.

Click to expand...

donholcha said:

I sure wish I still understood all of this as good as I used to. I've lost my touch and now have to ...

Click to expand...

Gemini said:

Don't worry, it happens to the best of us. The installation process for these newer standalone versions has become much more complex compared to the old Standard Tools days.

If you are stuck waiting on a MEGA download limit, you can sometimes bураss it by restarting your router (to get a new IP address) or using a VPN. Using a download manager like JDownloader 2 also helps—it will automatically resume the download once the wait timer expires so you don't have to sit there watching it.

Click to expand...