....
4) Start up VCDS (it may have already started at the end of the installation, which is fine). If VCDS won't start up at all after updating, make sure that Zone Alarm or your virus scanner are not blocking/quarantining the file. Make sure it says Release 18.9 at the top of the screen. If says an older version then something didn't go right. Check the shortcut on your desktop to make sure it's for Release 19.6. If needed, exit out of VCDS then repeat steps 1-3.
...
There are at least four control modules in that car that your "legacy" interface can't communicate with. So yes, an interface upgrade would be recommended.
Recently, I had upgraded to a new laptop that runs Windows 10 64 bit version. I installed VCDS version 19.6.1. When I launch VCDS from desktop shortcut, the program does not launch. Following are the checks I have performed.
1. When I check the task manager, the program is not listed in the processes.
2. Tried running the program in Administrator mode.
3. Tried troubleshooting compatibility issues and ran in Win8 and Win7 compatibility modes.
4. Checked that firewall has been configured to allow VCDS.
5. Added VCDS.exe as an exception in the antivirus software.
None of these work. Any pointers to what could be the problem?
Thanks in advance.
Edit: I have the Hex-V2 interface with a 3-VIN license.
Recently, I had upgraded to a new laptop that runs Windows 10 64 bit version. I installed VCDS version 19.6.1. When I launch VCDS from desktop shortcut, the program does not launch.
At this point, I think there are more people running Windows 10 and the x64 version of VCDS than any other combination, so there has to be something peculiar about your computer.
Try the "Install 32-bit EXE on 64-bit System" option in the installer to see if that helps.
If that still doesn't work, I would suggest uninstalling and and all bloatware and nannyware that came pre-installed on this computer.
Hello!
I have a problem with latest version of VCDS (19.6.1). When I try to access some of control modules of my car (for example, ABS and steering angle sensor), the error balloon above "Advanced ID" button is shown: "Vehicle is unsupported". Every other button stays disabled.
I know about legacy interfaces and 2019+ cars... BUT! My car is 2013 Polo sedan (russian market model), my interface is HEX-USB+CAN, OS is Windows 10 x64. When I've reinstalled previous version (19.6.0 - thank God I kept distro) - all work fine again.
Here is the log from the "Advanced ID" window (sorry don't know how exactly it's called):
Code:
Wednesday,21,August,2019,20:57:06:05202
VCDS -- Windows Based VAG/VAS Emulator Running on Windows 10 x64
VCDS Version: 19.6.1.0 (x64)
Data version: 20190529 DS308.0
www.Ross-Tech.com
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Address 03: ABS Brakes
Control Module Part Number: 6R0 907 379 AQ
Component and/or Version: ABS9.0 front H01 0003
Software Coding: 50DD2F64212504C10A18F472845720000000
Work Shop Code: WSC 01530
VCID: 0D115EF2DC450C27E2-8058
Advanced Identification/FAZIT
Serial number: --------------
Identification: BPA-085
Date: 08.08.13
Manufacturer number: 0040
Test stand number: 2660
Flash Status
Programming Attempts(application): 1/0
Flash Date: 00.01.01
Misc.
Hardware number: 6R0 907 379 AQ
Workshop System Name: J104
ASAM Dataset: EV_Brake1ABS90BOSCH
ASAM Dataset Revision: 003017
VCDS Info:
VCID: 0D115EF2DC450C27E2-8058
Labels: Redir Fail!
ROD: ERROR - EV_Brake1ABS90BOSCH 003017 (VN75)
Modules ## 37, 56 and 77 are not "real", i.e. their functions is handled by 5F - Information Electr. (Discover Media). When I've tried to remove them from gateway's installation list - there was an "module incorrectly coded" error.
But "Cannot be reached" on engine is a different story... I think it may be related to low battery charge... It discharged right after the scan, when I tried to start the vehicle with no success. I've recharged it but I think it's dying and I need to replace it ASAP.
Can it be related to "Unsupported vehicle" error in 19.6.1? But why there's no such error in 19.6.0 and earlier versions? I've tried two versions (19.6.1 and 18.9.0 RUS) one after another, in one shot, with different results. Then, after battery recharging, I've tried 19.6.0, and it worked fine, like 18.9.0 before.