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

VCTool also supports working with PQ, PL, and MLB platforms, but currently without one-click function activation presets.

The Porsche brand is not officially supported in VCTool for diagnostics.
However, you can work with these vehicles in MLBevo platform compatibility mode, and also use the Porsche Security Lock module to make manual configuration changes (not applicable to vehicles with SFD2).

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.

The generation of SFD tokens are not included in any subscription and are provided for an additional fee!

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 wide range of interfaces:

• VAS5054x / VAS6154x, using the standard D-PDU API driver. Stable operation with clone interfaces is not guaranteed.

• For the MQBevo*, MLBevo, MEB, PPC, and PPE platforms, the eNet interface can be used via the DoIP protocol.

• Any high-quality J2534-compliant interface that supports the ISO 15765 CAN UDS protocol, such as Tactrix Openport 2.0, Chipsoft, Scanmatik, etc. The use of copies of well-known brands sold through dropshipping stores is not recommended.

• Support for ELM interfaces will be discontinued in future versions of VCTool.

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

J2534 and VAS5054 interfaces are supported only in the x86 version of the application, as x64 drivers are not available for them.

Some J2534 interfaces can be used in the x64 version of VCTool via the D-PDU API driver; however, this approach reduces interface performance by approximately 2–3 times compared to using the native driver.

We strongly advise against using VxDiag / VCX interfaces. Their use may lead to unpredictable results and is entirely at your own risk.

* Support for the DoIP protocol on the MQBevo platform depends on the vehicle 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.

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!

We strongly advise against performing remote diagnostics via USB port forwarding or VPN‑DoIP. These types of connections do not meet required standards for reliability, speed, or stability and can lead to unpredictable consequences, including damage to control units. Any such operations are carried out at your own risk, and you assume full responsibility for them.

No, we do not provide this type of support. All requests are accepted and handled only through contact forms and email.