VCDS Interface Detection Issue: Elevator 10, Driver Installation, No COM Port Created

Hello

I searched a lot of forums, but I did not solve the problem ... I have Elevator 10 and after three days I managed to install the only drivers that could be installed at all (I upload in the attachment). The problem is that the drivers that I installed did not create a COM port, and that's why VCDS can not see the interface ... I do not know what to do anymore, I'm also uploading manager's photos. The cable that I have also send a photo. greetings

After all you can see the interface on the list, what is the problem? Is this the original equipment or some Chinese clone?

The original, so how can I see why I can not connect?

Added after 50 [seconds]:

And when it comes to the com4 communication port it was already before installation.

When installing VCDS, I went through the installation stage of the drivers, the interface I had was working immediately, with Windows 10. Uninstall the device together with the driver files, uninstall the VCDS and install the program again. It will install the drivers and the interface will start after connecting it to the computer - only remember that the program is choosing a USB connection, not a COM port. The original moves ...

I have 100% original but I lost the plate I've tried it several times, after installing the drivers, and so the manager has an exclamation mark.

Added after 54 [seconds]:

Only those Russian drivers installed the cable.

You download the program for free from the manufacturer's website. You do not even have to have an interface, it detects the originality of the hardware itself.

beniu1212 wrote:

I have the original 100%

https://www.a6klub.pl/kabel-vcds-vt60955.htm
http://www.vag-com.pl/index.php?mod=site&id=29

dizba wrote:

beniu1212 wrote:

I have the original 100%

https://www.a6klub.pl/kabel-vcds-vt60955.htm
http://www.vag-com.pl/index.php?mod=site&id=29

There is no need to give The legal interface will work on the program downloaded from the manufacturer, and the Polish version is not so obvious.

Works without a problem, but on win xp, the program downloaded from the producer. I gave for this wire 7 years ago PLN 600, used from a mechanic, must be the original.

he must - he does not have to. The system reports as "Ross-Tech Direct Interface", that is, PID_FA30. In new drivers, this interface is no longer supported. Personally, I have never met HEX-CAN with this PID, all of them had an FA24 which is still supported. Besides looking at the photos, I've been repairing the same Chinese clones. If you want, I will send you a program to read the interface and check this alleged originality.

Hello, I can ask for a program to check the interface? Because I also have a problem with a similar one and I see the program before connecting to the car that the status is not connected to the car and when connecting to the car does not detect the interface at all. Maybe the cable released? What is the cost of repair and how does it go?

Hello, um, not come clone from ali with a clean cd, is it possible to download a clone program?

I have the same problem. Cable from Ali with a clean CD where to download vcds?

for me on a hamster http://chomikuj.pl/krzychu.ml is or write to a Chinese, talking about 18.9

It worked and the cable came to life. For the VAG182 version of the cable, I found the VCDS version I was interested in (21.3.0), and I also found the loader (detected as a Trojan) from Kolimer in version 9.2. The package with the loader included everything needed. I used the VAGCOM_EEWriteLang application to flash the cable connected to the OBD, and then I installed VCDS and that's it. Of course, you have to run the program with the loader connected and everything works fine. It is known that it will no longer support newer cars.

Hello, this is a bit of a dusty topic and I decided to dust it off a bit.
At the beginning of :
Have a healthy and Merry Christmas.

Gentlemen, I have a question. I have the same cable as the author of the topic, except that the newer version, 12.12.3, works for me, but with one of my cars, specifically a VW Polo from 2004, it loses connection.
Sometimes you can connect without any problems with the engine turned off. After starting it, it works for some time and then loses connection.
Sometimes it loses connection when the engine is turned off. Then, if it loses power with the engine turned off, I have to turn the laptop off and on again to connect.
In another case, it connected without any problems with the engine running.
What could be the reason ?

The second question is whether I can update my cable to version 15..., this is what I see and can I upload the Polish language version? The cable was bought in China.

What version of VCDS would I need to download to safely install the Polish language version?
Thank you and best regards.

Freshly purchased HEX-V2 cable from Ali. The problem was under Win11. In the system device manager, the Ross-Tech device's USB port was showing with an exclamation mark symbol. It didn't help to reinstall the software or add alternative USB drivers (I tried several different ones, newer and older, from different vendors, including those supplied with the cable).
The solution turned out to be quite simple, although not entirely elegant due to the need to disable one of the system's protections. Namely, the memory integrity protection (core isolation/core isolation) had to be turned off. After this, the interface became visible and VCDS could be used normally.