Ista and inpa issues concerning win 11 home etc.,

Csabek said:

Szuper

Click to expand...

So yes one thing I found out my com port communication was missing I had to go to top find add legacy hardware. Still having inpa issue but got ista to work.

trun10tion said:

Hoping any programmers can give insight on possible windows issues, involving installing ista and inpa. I'm CompTIA A+ certified in repair pc's only. Online I've installed many softwares and it seems under win 11 we're having issues. Previous windows installs worked. We've all followed steps tirelessly and inpa either no ignition light and every one goes to com 1, environmental variables and other basic steps so I'm leaning on software issues or Window issues hopefully a programmer can shed some light on what's really going on.
If I one day figure this out I will surely post.
Thanks for your time.

Click to expand...

Hey,
You don`t have do anything special to install Bmw standard tools on a windows 11 version compared to former versions (10 or 7), i have done it plenty times witout any issues.
good luck.

Agreed with Carjan — Standard Tools (INPA/EDIABAS) installs fine on Win 11, there's no special trick to the install itself. The pain is almost always the interface/COM layer, not Windows version.

For the classic "no ignition light / everything lands on COM1" symptom, the usual culprits are:

• OBD.ini / interface selection — for a K+DCAN USB cable, EDIABAS needs to be set to STD:OBD, not the old COM/ADS path. Check [C]C:\EDIABAS\bin\EDIABAS.ini[/C] → [C]Interface = STD:OBD[/C] and [C]C:\EDIABAS\bin\OBD.ini[/C] pointing to the right port.
• FTDI COM port number — the cable's virtual COM must be set to COM1–COM4 in Device Manager (Port Settings → Advanced). INPA/EDIABAS won't talk on high COM numbers by default. Latency Timer set to 1ms helps too.
• Cable driver — genuine vs counterfeit FTDI matters on Win 11; a bad/newer FTDI driver can silently break comms. Rolling back to a known-good FTDI VCP driver often fixes it.
• Switchable K-line cable — some DCAN cables have a jumper/switch; wrong position kills the ignition/voltage read.

trun10tion already found part of it — the missing COM port needed "Add legacy hardware," which points squarely at the driver/port layer rather than the OS.

To pin it down, what cable are you running (K+DCAN clone or genuine ENET/ICOM), which COM number does it enumerate as, and does INPA show battery/ignition voltage at all or a flat zero?