[CATAHA]

Maybe the answer is more simple
BMW AG preparing for NEW gen vehicles and starting to move it's software to new ways(DoIP with ICOM acting as a DHCP server for assignment of CAR_Client IP_ADDR)
Windows 12/13/14~ 64bit 
Increasing security and making it more of an individual bases ( BASE on ISTAGUI.exe.config )
ENET = DoIP

Base on those files
REGSVR32.BAT
Rplus.ini
REMOTE.ini
EDIABAS.INI

CHECK EDIABAS.INI(attached)
4.45.x
4.46.x ( 
Answer as follows: 
Instead of using "Autodetect" use IP_Addr of an ICOM, because autodetect calls for ICOM DHCP assignment of an IP_addrs for DoIP protocol client(s) but when using direct IP_Addr config bypasses DoIP_DHCP_REQUEST procedures 
)

EXAMPLE(i haven't tested yet):
1. This activates DHCP on ICOM, increasing wait time for connection, this method is been used if multiple ICOM(s) use one computer (3:1 multiple_sessions ) 
Interface        = ENET ; (DoIP, DHCP utilization via ICOM or DHCP_SERVER)
RemoteHost      = Autodetect

2. This does NOT activates DHCP on ICOM, decreasing wait time for connection, this method is been used if connecting directly to computer (1:1)
Interface        = REMOTE ; (Direct connect PC_TO_ICOM)
RemoteHost      = 169.254.1.169 ; (ICOM_IP_ADDRS)

;=============================================================================
[XEthernet]
;=============================================================================
RemoteHost      = Autodetect
VehicleProtocol = DoIP,HSFZ ; (Can be reversed  HSFZ,DoIP )
DoipGatewayAddress = 0010
; ------------------ Beispiele fester IP-Adressen
; RemoteHost      = 169.254.1.1
; RemoteHost      = 192.168.100.1
HeaderFormat    = 0
TesterAddress    = F4,F5
DoIPTesterAddress = 0EF3

;-----------------------------------------------------------------------------
; VehicleProtocol
;      Description :  Transport protocol for Ethernet communication
;      Value      :  [HSFZ|DoIP|HSFZ,DoIP|DoIP,HSFZ] | [0|1|0,1|1,0]
;                      HSFZ or 0 : Set up HSFZ connection with ECU
; DoIP or 1 : Set up DoIP connection with ECU
; HSFZ, DoIP or DoIP,HSFZ or 0,1 or 1,0 : Use protocol where the ECU answered first               
;      Default    = HSFZ
; VehicleProtocol      = HSFZ,DoIP

;-----------------------------------------------------------------------------
; DoipGatewayAddress
;      Description :  Diagnostic Address of the Gateway ECU (only for DoIP Gateways!)
; If there are multiple DoIP Gateways available, DoipGatewayAddress will be used as filter
; If the defined Gateway address can't be found (or can be foud multiple times), the error message "INVALID BUS CONFIGURATION" will be displayed
;      Value      :  two-digit hexadeciamal, without leading "0x":
;                      0010 : The DoIP Gateway ECU with Diagnostic address 0x0010 (16 dez) will be used
; FFFF : Deactivates filtering with Gateway diagnostic address (with this setting on using configuration RemoteHost=Autodetect only one! DoIP gateway can be connected)               
;      Default    = FFFF
; DoipGatewayAddress      = 0010

;-----------------------------------------------------------------------------
; VehicleIdentification
; Description :  Value = 0: If RemoteHost != Autodetect, ENET driver uses HSFZ to contact target ECU on given IP address               
; Value = 1: If RemoteHost != Autodetect, ENET driver uses DoIP to contact target ECU on given IP address       
; Default    =  0
; VehicleIdentification = 0

;-----------------------------------------------------------------------------



My preview's observations
When I installed and used ISTA on Win10 with Group Policy been adjusted i had to adjust both settings
EDIABAS.INI
1. [Configuration]
2. [TCP]
When I used on Win10 without Group Policy been adjusted
EDIABAS.INI
1 [Configuration] (ONLY)

Thanks to @sedoy and @bugfix to pointing out in the right direction, and Here is fix for this mess. I have edited ediabas.ini in both ista and ediabas. With this my ista works perfect and also INPA/tool32/etc. Copy both to respective ediabas location and ista location, assuming ediabas is installed in c:\ediabas, because .ini file is edited according to that. Also make sure you delete entry in SYSTEM VARIABLE ediabas_config_dir.
This works and tried it on my F20.
Glad to help.
If I helped then please thanks+rep

[CATAHA]

With what environment did it help you?
IE: 
OS type
Device Type
Virtual/Physical
Connection Type
Etc.....

NOTE:
that's how troubleshooting and feedbacks work " Cerhio "

Hey. Your files help me as well
What did you change exactly in it?

[CATAHA]

I wonder how long would it take for HIGH paying LAZY BMW engineers to troubleshoot this;
See attached Picture

SIDE-NOTE
I'm not an English Prof. nor english is my primary language

[NeRkO20]

@Cataha but this doesn´t solve the "issue" with triggering DHCP with ICOM (next)?

My only let´s say small problem is that connection manager needs longer to find ICOM and not working DHCP....

I am not sure if ISTA in this version is slower on my system then 4.45.xx before... and I have installed Standard tools and EDIABAS on c:\ because of using other tools

Would u recommend to change anything at the moment on my setup?

[Node]

INVALID_BUS_CONFIGURATION is exactly the internal error ISTA gets from ediabas when trying to enable ICOM's DHCP in 4.46.1x. It does NOT feel like we can do anything about it ATM.

[atomantmk]

Thanks to @sedoy and @bugfix to pointing out in the right direction, and Here is fix for this mess. I have edited ediabas.ini in both ista and ediabas. With this my ista works perfect and also INPA/tool32/etc. Copy both to respective ediabas location and ista location, assuming ediabas is installed in c:\ediabas, because .ini file is edited according to that. Also make sure you delete entry in SYSTEM VARIABLE ediabas_config_dir.
This works and tried it on my F20.
Glad to help.
If I helped then please thanks+rep

With your settings yesterday very quick diagnostic on F10, today on F06 again long time...

[NeRkO20]

INVALID_BUS_CONFIGURATION is exactly the internal error ISTA gets from ediabas when trying to enable ICOM's DHCP in 4.46.1x. It does NOT feel like we can do anything about it ATM.

OK, I have my 2nd LAptop "downgraded" to 4.45.xx....

And on the other one...let´s wait for next update...maybe BMW will solve it...at the moment DHCP is not that big problem I think

[Twointje]

Before we needed IDIABAS 7.3 patched version for a reason ,i am not a specialist and dont now why we exactly needed the patched version of EDIABAS 7.3. But if we now have to copy all files of the new not patched EDIABAS 7.6 to EDIABAS 7.3 to get Ista 4.46.1X to work normally will this then have effect on all the other software that was using the patched version? Dont know with software was using the 7.3 patched version ,is Esys and DR Gini B21 or 22 using it?
Or BMW HU service manager? if all these programs needed the patched version are they not going to stop working after copying all the files of the new EDIABS to the OLd one?

This is something i am asking myself before i update from 4.45.30 to 4.46.1X ,dont want to mess up my system and hope withe new Ista update this problem will be resolved.
I am using Ista with a Enet cable dont have a icom because i just use Ista for personal use not professional.
Best regards

[NeRkO20]

Before we needed IDIABAS 7.3 patched version for a reason ,i am not a specialist and dont now why we exactly needed the patched version of EDIABAS 7.3. But if we now have to copy all files of the new not patched EDIABAS 7.6 to EDIABAS 7.3 to get Ista 4.46.1X to work normally will this then have effect on all the other software that was using the patched version? Dont know with software was using the 7.3 patched version ,is Esys and DR Gini B21 or 22 using it?
Or BMW HU service manager? if all these programs needed the patched version are they not going to stop working after copying all the files of the new EDIABS to the OLd one?

This is something i am asking myself before i update from 4.45.30 to 4.46.1X ,dont want to mess up my system and hope withe new Ista update this problem will be resolved.
I am using Ista with a Enet cable dont have a icom because i just use Ista for personal use not professional.
Best regards

I have "regular" Version of Ediabas 7.3 NOT the patched and all tools are working for me....
ISTA 4.46 works, I am not sure if it is slower than 4.45...

[ivanp]

Hello,

Did somebody find a solution to have latest version of ista (with ediabas 7.6) working with dkan cable?
I have tried to copy BIN from Ista installation to C:/ec-apps/ediabas (adjusting accordingly - Interface = STD:OBD  and Port = 6001) but still not working.
With Icom is working in both configs of BIN in C:/ec-apps/ediabas - from 7.3 and from 7.6

Thank you!