VCTool works with almost all vehicles built on the MQB, MQBevo, MLBevo, and MEB platforms. You can see the list of supported vehicles by launching VCTool and opening the “About” section.

Support for vehicles on older platforms like PQ, PL, and MLB is currently unavailable, but it is planned for the near future. Stay tuned!

Although we do not offer trial periods, you can create an account and try VCTool without payment—some features will be available in a limited mode.

VCTool is the world’s first third-party application that allows you to unlock control units protected by SFD in real time! You can read more about how to work with SFD here.

The SFD token generation service is provided by a third-party organization and may be unavailable due to reasons beyond VCTool’s control. You can monitor the service status on the status page.

Starting from version 1.16.1.0, dated January 17, 2024, VCTool fully supports working with the SFD2 system in manual mode (without automatic token generation—the user is responsible for this process), uploading .XML packages containing SFD2 tokens, and simulating SFD2 in the UDS ECU Simulator.

SFD2 has nothing to do with SFD v1 and works completely differently, so the concept of “SFD2 Unlock” is not applicable to it. In SFD2, a token is permission to write specific data defined in the token, meaning any data set (adaptations, datasets) you want to write to the control unit must be signed on the VAG server and only then written to the control unit.

At the moment, VCTool fully supports working with the SFD2 system in manual mode only, so, you can gather the necessary data, but obtaining the token is the user’s responsibility.

No, VCTool does not support binding control units to a vehicle, removing component protection, or working with the immobilizer.

VCTool supports a large number of interfaces:

• VAS5054x/6154x, using standard D-PDU API driver. Attention! Stable operation with clone interfaces is not guaranteed!
• To work with the MQBevo*, MLBevo and MEB platforms, the eNet interface can be used via the DoIP protocol.
• Any high-quality J2534 compliant interface that supports the ISO15765 CAN UDS protocol: Tactrix Openport 2.0, Chipsoft, Scanmatik, etc. We do not recommend using copies of well-known brands sold through dropshipping stores.
• (Not recommended) ELM327 compatible adapters built on ELM, STN or MIC chips (Bluetooth and USB): ELM327, OBDLink USB/BT devices, vLinker USB/BT devices. Unfortunately, due to the peculiarities of the data exchange protocol of these interfaces, we do not guarantee stable and fast work with the car when connected via ELM interfaces.

For maximum speed, we recommend using adapters eNet, VAS5054/6154 or J2534.

* Support for the DoIP protocol on the MQBevo platform depends on the vehicle’s configuration.

Yes. VCTool is a client-server application and most of the information needed to work is stored on our server.

The Internet connection is used only during the login process and download of data (for example, backups, datasets or other data), so if, for example, the connection to the Internet is lost during the firmware update of the control unit, this will not affect the process in any way.

Yes. You can use the Stock Service, which is provided by VCTool’s partners for the automatic instant retrieval of factory parameterizations and calibrations upon request. The request can be generated manually, on a connected vehicle, or using data from a backup. This service is paid and not included in any subscription. You can find the terms of service directly in VCTool.

The Stock service is provided by a third-party organization and may be unavailable due to reasons beyond VCTool’s control. You can monitor the service status on the status page.

The problem is that VNCI stops working with the latest 32-bit driver versions by some reason (ODIS use 64-bit version of the driver and it’s not compatible with VCTool).
This is not an issue with VCTool; it is specifically a problem with VNCI.

You can try running the testing utility included with the driver (located in the driver folder at C:\Program Files (x86)\VCTool\PDU-API\VW_D-PDU_API_Tester.exe) and perform the interface testing a couple of times in a row (first tab), and after that run the Performance Test. Sometimes this procedure helps.

If not, please try installing driver version 21.2.0 or 26.0.0 and attempt to connect to the vehicle again.

The original VAS6154 interface does not have such problems and works perfectly with any driver version.

An important point—after the driver flashes the interface during the first connection attempt (a small window appears in the bottom right corner of the screen), you will need to restart VCTool and reselect the interface. Be sure to wait until the flashing process is complete!