Hi,
I have a HEX-V2 (H10-004687 -bought form Ross-Tech) with win 7 laptop. So far it has given the support to my problems with my Audi. All earlier updates have been completed successfully, but now when VCDS recommended to update the VCDS SW to 18.9.0 thing went south. The actual VCDS update was successful, but I got a problem with interface module.
After update I got the normal "first use/ No config file found" message and I made the port test which was ok and said that firmware update is required.
--> clik ok and the VCDS Interface config (v2.242) opened. It was totally blank and it said in bottom "Unable to open the interface, it maybe used by another program"
It looks like the drives are not the ones in download package. I tried to remove the interface drives manually, but it seems that windows determines and installing "best" drives in every time when i'm plug-in the interface.
Does any one else had similar problems?
I have a HEX-V2 (H10-004687 -bought form Ross-Tech) with win 7 laptop. So far it has given the support to my problems with my Audi. All earlier updates have been completed successfully, but now when VCDS recommended to update the VCDS SW to 18.9.0 thing went south. The actual VCDS update was successful, but I got a problem with interface module.
After update I got the normal "first use/ No config file found" message and I made the port test which was ok and said that firmware update is required.
--> clik ok and the VCDS Interface config (v2.242) opened. It was totally blank and it said in bottom "Unable to open the interface, it maybe used by another program"
It looks like the drives are not the ones in download package. I tried to remove the interface drives manually, but it seems that windows determines and installing "best" drives in every time when i'm plug-in the interface.
Does any one else had similar problems?