ISTA+ STANDALONE BMW Diagnostic & Coding - Workshop Solution 4.57.30
- Thread starter Bin
- Start date
- Tagged users None
Post #442
FFWD
Stock Member
Tried connecting to the car, but getting:
Error
An unexpected fault occurred. The vehicle session cannot be continued. BMW support must be contacted.
The following technical fault message occurred:
Unable to load DLL 'api64.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
First off, I had to install on the D: drive because C: is full and I'm waiting on a new laptop to arrive. So I extracted everything in to D:\ISTA
I also noticed the D:\ISTA\Ediabas\BIN\EDIABAS.INI file contained paths to the C:\drive so I switched them to the appropriate directories in D: \ISTA, but it still gives me the same error.
There are 3 copies of api64.dll under D:\ISTA:
D:\ISTA\EdiabasLib - 5.79MB
D:\ISTA\Ediabas\BIN - 154 KB
D:\ISTA\EdiabasForIDES\BIN - 153 KB
They don't exist anywhere else on C: or D: - the instructions didn't say to copy or move them anywhere, but which one goes where? In the meantime, I also:
- reinstalled both x86 and x64 Visual C++ 2015-2019
Any ideas?
Error
An unexpected fault occurred. The vehicle session cannot be continued. BMW support must be contacted.
The following technical fault message occurred:
Unable to load DLL 'api64.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
First off, I had to install on the D: drive because C: is full and I'm waiting on a new laptop to arrive. So I extracted everything in to D:\ISTA
I also noticed the D:\ISTA\Ediabas\BIN\EDIABAS.INI file contained paths to the C:\drive so I switched them to the appropriate directories in D: \ISTA, but it still gives me the same error.
There are 3 copies of api64.dll under D:\ISTA:
D:\ISTA\EdiabasLib - 5.79MB
D:\ISTA\Ediabas\BIN - 154 KB
D:\ISTA\EdiabasForIDES\BIN - 153 KB
They don't exist anywhere else on C: or D: - the instructions didn't say to copy or move them anywhere, but which one goes where? In the meantime, I also:
- reinstalled both x86 and x64 Visual C++ 2015-2019
Any ideas?
Post #443
abdo2u
Stock Member
Hi everyone
I am really happy to have installed the ISTA 4.57.30, I followed all the steps, but unfortunately, when I run the ISTA and start the scan diagnosis using USB K-Dcan, it won't detect the VIN as shown in the pop-up message (No connection to vehicle possible), I have tried many ways to solve this issue, but unsuccessfully.
I tried using ICOM next, and the system can read the VIN, but the voltage at KL 15 & KL 30 is showing 0.0V in red, and a pop-up message says (is the switch on or PAD active?). Then the system quit, as shown in the photos. unable to complete scanning ....
Need help to solve this issue, please....
Thanks
I am really happy to have installed the ISTA 4.57.30, I followed all the steps, but unfortunately, when I run the ISTA and start the scan diagnosis using USB K-Dcan, it won't detect the VIN as shown in the pop-up message (No connection to vehicle possible), I have tried many ways to solve this issue, but unsuccessfully.
I tried using ICOM next, and the system can read the VIN, but the voltage at KL 15 & KL 30 is showing 0.0V in red, and a pop-up message says (is the switch on or PAD active?). Then the system quit, as shown in the photos. unable to complete scanning ....
Need help to solve this issue, please....
Thanks
Attachments
Post #444
- Joined
- 03.05.2025
- Messages
- 1,834
- Reaction score
- 40,590
@Gemini help
Post #445
Gemini
Staff member
- Joined
- 09.05.2025
- Messages
- 2,012
- Reaction score
- 606
The error
Unable to load DLL 'api64.dll': The specified module could not be found. usually indicates an issue with the ISTA installation or its dependencies, particularly with the api64.dll file which is part of the Ediabas communication library.Here are some steps to troubleshoot this:
1. Verify Ediabas Configuration:
* Ensure the
EDIABAS.INI file is correctly pointing to your ISTA installation directory. Since you installed on D:\ISTA, all paths within EDIABAS.INI should reflect this, e.g., RemoteHost=127.0.0.1, Interface=STD:OBD.* Check the
INST.INI file (if present) for any conflicting paths.2. DLL Placement:
* The
api64.dll file is crucial for 64-bit communication. ISTA typically expects it in D:\ISTA\Ediabas\BIN.* While you found multiple copies, the one in
D:\ISTA\Ediabas\BIN is the most likely candidate for the primary installation.* Try copying the
api64.dll from D:\ISTA\EdiabasLib (the larger one) to D:\ISTA\Ediabas\BIN and overwrite the existing file. This larger file might contain more complete components.* Ensure that the system's PATH environment variable includes
D:\ISTA\Ediabas\BIN. If not, add it.3. Reinstall Ediabas:
* Sometimes, a corrupted Ediabas installation is the culprit. You might need to reinstall Ediabas.
* Locate the Ediabas installer within your ISTA package or download a standalone Ediabas version compatible with your ISTA.
* Uninstall any existing Ediabas, then install it again, ensuring it's directed to your
D:\ISTA directory.4. Visual C++ Redistributables:
* You've already reinstalled Visual C++ 2015-2019. Ensure you have both x86 and x64 versions installed correctly. ISTA and its dependencies rely on these.
5. ISTA Installation Directory:
* While installing on
D: should be fine, ensure there are no unusual characters or spaces in the D:\ISTA path.* Try reinstalling ISTA to a simpler path, like
D:\BMWTools, to rule out any path-related issues.6. Run as Administrator:
* Always run ISTA and any related tools (like NCSExpert, INPA if you use them) as an administrator to avoid permission issues.
Regarding the other issue with voltage readings and the K+DCAN not reading the VIN:
- Voltage Readings (0.0V): This often indicates a problem with the vehicle's communication bus or the power supply to the diagnostic port.
* Check the fuse for the cigarette lighter/12V socket, as some cables draw power from there or the OBD port itself.
* Try connecting to a different BMW model if possible to rule out a vehicle-specific issue.
* Verify that the K+DCAN cable's switch is set correctly for the E-series or F-series car you are working on.
- K+DCAN Not Reading VIN:
EDIABAS.INI is set to Interface=OBD (for K+DCAN) and that RemoteHost is 127.0.0.1.* Driver Issues: Ensure the correct drivers for your K+DCAN cable are installed and recognized by Windows.
* ISTA Settings: In ISTA, go to
Settings -> VCI and ensure your K+DCAN adapter is correctly selected.Start with verifying the
api64.dll placement and Ediabas configuration, as this is the direct cause of your current error message.Post #446
abdo2u
Stock Member
Dear Gemini...
Thank you for your replies....
I have checked all connections from the PC to OBD, and all are plugged in properly..
Even if I used ICOM, it runs properly in the beginning, then stops as the photo I sent..
in the file api64.dll when I open it it shows like corrupted, are it normal !? please see photos...
Thanks
Thank you for your replies....
I have checked all connections from the PC to OBD, and all are plugged in properly..
Even if I used ICOM, it runs properly in the beginning, then stops as the photo I sent..
in the file api64.dll when I open it it shows like corrupted, are it normal !? please see photos...
Thanks
Attachments
Post #447
- Joined
- 03.05.2025
- Messages
- 1,834
- Reaction score
- 40,590
@Gemini mention her to get a reply in this thread — auto-replies aren’t working.
Post #448
abdo2u
Stock Member
I have tried using E-net & USB (k-DCan) & ICOM, USB failed to continue Scanning, ICOM & E-net unable on the beginner, then ISTA operation deducting the Voltage of the vehicle is 0.0 Volt , ISTA stop operating due to 0Volt...
I checked on Ediabas folder could not found file OBD.ini, it's not access on the folder...
Could please someone knowledge about the issue here .....
I checked on Ediabas folder could not found file OBD.ini, it's not access on the folder...
Could please someone knowledge about the issue here .....
Post #449
FFWD
Stock Member
Since Tuesday, I made so many small and big changes to get this working, I can't even remember all of them, nevermind what was relevant. But it included:
- a friend installed BMW Standard Tools on my computer to get past the api64.dll error. This installed another version of EDIABAS in C:\EC-APPS\Ediabas as well as created a link from C:\EDIABAS to that directory.
- Windows Device Manager - Ports (COM & LPT) - USB sеriаl Port properties - Port Settings - Advanced to set Latency Timer to 1 and also match COM Port to obd.ini (or vice-versa)
- Modified the System Environment Variables PATH to reflect Ediabas directory
I also modified a couple of Registry entries to point to C:\EC-APPS\Ediabas directory instead of D:\ISTA\Ediabas, but then also noticed a whole bunch of entries that refer to D:\ISTA. At this point since it's working I'm hesitant to mess with it, but if I were to reinstall once I get my new computer, I'll unzip to C:\ to hopefully make things go smoother.
Post #450
abdo2u
Stock Member
Post #451
Gemini
Staff member
- Joined
- 09.05.2025
- Messages
- 2,012
- Reaction score
- 606
The observation that the
api64.dll file appears "corrupted" when opened is not normal. DLL files are binary executables and are not meant to be human-readable in a text editor. If you are seeing readable text or gibberish, it likely means the file is either incomplete, corrupted, or you are trying to open it with the wrong application.Let's address the multiple issues:
1.
api64.dll Error:This error, "Unable to load DLL 'api64.dll': The specified module could not be found," strongly suggests that the ISTA application cannot locate or access this critical file.
- Re-check Installation Directory: Confirm that
api64.dllis present inD:\ISTA\Ediabas\BIN. If you have installed BMW Standard Tools separately, it might have placed its own Ediabas components inC:\EC-APPS\EdiabasorC:\EDIABAS. - Path Environment Variable: Ensure that
D:\ISTA\Ediabas\BIN(or the directory where the correctapi64.dllresides) is correctly added to your system's PATH environment variable. If BMW Standard Tools installed its own Ediabas, its directory might be overriding ISTA's. - Registry Entries: You mentioned modifying registry entries. Be extremely cautious here. Incorrect registry modifications can cause system instability. If ISTA was installed to
D:\ISTA, ensure that any registry keys related to Ediabas or ISTA point to the correctD:\ISTApaths. If Standard Tools installed its Ediabas inC:\EC-APPS\Ediabas, and ISTA is trying to use that, it might resolve theapi64.dllerror but could lead to other compatibility issues. - Clean Installation: The most reliable solution for DLL errors is often a clean reinstallation.
2. Manually delete any remaining ISTA/Ediabas folders (e.g.,
D:\ISTA, C:\EDIABAS, C:\EC-APPS\Ediabas).3. Ensure all Visual C++ Redistributables (2015-2019, both x86 and x64) are installed.
4. Reinstall ISTA to a simple path like
D:\ISTA without any spaces or special characters.5. Configure
EDIABAS.INI to point to D:\ISTA and set the interface correctly.2. No
OBD.ini File Found:The
OBD.ini file is typically part of the BMW Standard Tools installation (INPA, NCSExpert), not ISTA itself. ISTA uses EDIABAS.INI for its primary configuration.- If you intend to use INPA or NCSExpert with your K+DCAN cable, you will need to install BMW Standard Tools separately. The installation process for Standard Tools usually creates the
OBD.inifile within the Ediabas directory (e.g.,C:\EDIABAS\BIN). - Ensure that the
Interfacesetting inEDIABAS.INIis correct for your connection method:
Interface=OBD* For ICOM:
Interface=TCPIP (or ETHERNET depending on version)3. Voltage Readings of 0.0V and Connection Issues (ICOM/E-net/K-DCAN):
This is a critical issue that points to a communication problem between ISTA and the vehicle's ECUs, or a power issue to the diagnostic interface.
- Power Supply: The 0.0V reading is highly suspicious.
* ICOM: ICOM devices typically draw power from the vehicle's OBD port or an external power adapter. Ensure the ICOM is receiving adequate power.
* Vehicle Battery: A very low or dead vehicle battery can cause communication issues. Ensure the car battery is healthy and adequately charged.
- VCI Configuration in ISTA:
Settings -> VCI tab.* For K+DCAN: Select
Ediabas or K+DCAN. Ensure the EDIABAS.INI path is correctly set.* For ICOM: Select
ICOM. Ensure the ICOM's IP address is correctly entered and that ISTA can connect to it.- Cable Integrity: Even if connections appear plugged in, the cables themselves (K+DCAN, Ethernet, ICOM) can be faulty internally. If possible, test with a known good cable.
- Vehicle Communication Bus: The issue might be with the vehicle's diagnostic bus (e.g., CAN bus). This is less likely if you have issues with multiple connection methods unless there's a widespread power or ground problem affecting the OBD port.
Given the complexity and the fact that you've made many changes, a clean reinstallation of ISTA and potentially BMW Standard Tools is the most recommended path to resolve the
api64.dll error and ensure a stable configuration. After that, focus on verifying the VCI settings and power supply for the vehicle interface.Post #452
abdo2u
Stock Member
Finally I have add Eidabas file on C:\EIDABAS, I copy it from other PC, then using Enet, it's work and complete the scan, just I got worning of some error missing data!!
Post #453
abdo2u
Stock Member
Post #454
adetolua
Watchlisted
Post #455
trun10tion
Bolt-On Member
Post #456
fslabbertf73
Watchlisted
This is a great program
Post #457
abdo2u
Stock Member
Check the folder named ISTA+4.57.30 config; inside, you will find the BMW.RAR file.
Attachments
Post #458
jure.krane
Stage I
- Joined
- 05.01.2026
- Messages
- 4
- Reaction score
- 0
Post #459
Gemini
Staff member
- Joined
- 09.05.2025
- Messages
- 2,012
- Reaction score
- 606
It's good that you've made progress with the E-net connection and ISTA is completing scans. The "missing data" warnings are common and often relate to specific vehicle options or regions not present in your ISTA data files.
The persistent issue with ICOM showing 0.0V for KL.15 and KL.30 is still the main concern. This indicates a fundamental communication or power problem with the ICOM interface itself or its connection to the vehicle when using that specific interface.
Here's a breakdown of potential causes and solutions:
1. ICOM Configuration in ISTA:
* Settings -> VCI: Double-check that the correct ICOM interface is selected and that its IP address is correctly entered. If you are using an ICOM Next, ensure it's set to the appropriate Ethernet/IP configuration.
* Network Settings: Ensure your PC's network adapter is configured to be on the same subnet as the ICOM. For example, if your ICOM is at
192.168.1.10, your PC's adapter should be something like 192.168.1.5 with a subnet mask of 255.255.255.0.* ICOM Firmware: Although less likely to cause a 0V reading, ensure your ICOM's firmware is up-to-date. You can usually check/update this via its web interface.
2. ICOM Hardware/Connection:
* Power: The 0.0V reading for KL.15 (Ignition) and KL.30 (Battery) strongly suggests the ICOM is not receiving power or is not properly communicating power status to ISTA.
* OBD Power: Ensure the ICOM is receiving adequate power from the OBD port. Some vehicles or older OBD ports might not supply enough stable power for the ICOM.
* External Power Supply (if applicable): If your ICOM model supports an external power adapter, ensure it's connected and functioning.
* Test ICOM on another vehicle: If possible, try connecting the ICOM to a different BMW vehicle to rule out a vehicle-specific OBD port issue.
* Cable Integrity: Test the Ethernet cable connecting your PC to the ICOM, and the OBD cable connecting the ICOM to the vehicle. A faulty cable can interrupt communication and power signals.
* ICOM Unit: In rare cases, the ICOM unit itself might be faulty.
3. EDIABAS Configuration for ICOM:
* While ISTA often handles ICOM configuration directly, it still relies on EDIABAS for some lower-level communication.
* Check your
EDIABAS.INI file (usually located in C:\EDIABAS\BIN or C:\EC-APPS\Ediabas\BIN).* Ensure the
Interface is set to TCPIP or ETHERNET (depending on your ISTA version and ICOM type).* Verify the
RemoteHost setting points to your ICOM's IP address. Example:
Code:
ini
[Configuration]
Interface=TCPIP
RemoteHost=192.168.1.10192.168.1.10 with your ICOM's actual IP address).4. Vehicle Communication (Less Likely for 0V):
* While a general CAN bus issue could prevent communication, it's less likely to manifest as a specific 0.0V reading for both KL.15 and KL.30 from the VCI itself. However, a severely low vehicle battery could cause the OBD port to not supply enough power, leading to this symptom.
Troubleshooting Steps:
1. Verify ICOM IP and Network: Confirm your ICOM's IP address and that your PC is on the same subnet. Access the ICOM's web interface directly.
2. Test ICOM Power: Check if the ICOM has any indicator lights that show it's receiving power when connected to the vehicle's OBD port.
3. Re-check ISTA VCI Settings: Go through the VCI settings in ISTA meticulously.
4. Test with a different ICOM cable/vehicle: If possible, isolate the variable by trying different cables or a different vehicle.
5. Review EDIABAS.INI: Ensure the TCP/IP settings are correct for your ICOM.
The fact that E-net works suggests your ISTA installation and basic configuration are sound. The ICOM issue is likely related to its specific connection, power, or configuration.
Post #460
FFWD
Stock Member
FYI, if you download the original file, it's not included. But that download includes another tоrrеnt file that contains the exact same files PLUS the BMW,RAR file under the config directory. So you end up having to download ISTA+4.57.30 twice.
Activity
So far there's no one here
Similar threads
