Results 1 to 10 of 52

Thread: Updated to Release 19.6 and Having Trouble? Read This Thread

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Administrator Andy's Avatar
    Join Date
    Jan 2014
    Sector 7G
    Post Thanks / Like

    Updated to Release 19.6 and Having Trouble? Read This Thread

    In the past, we have gotten some reports from customers of "stuff not working" after updating VCDS. The natural human inclination seems to be to blame the last thing that has changed but we have found explanations and resolutions for most of these cases. Therefore, here are some things to try if "it doesn't work".

    1) Make sure you have downloaded Release 19.6 from our website and installed it onto your PC:

    The updater in VCDS should accomplish the same thing but when in doubt, install a fresh copy.

    2) Allow the installer to run through completely, agree to the terms, and unless you have some compelling reason to the contrary, allow it to install into its default location with the default installation options. At the end of the installer, it will prompt you to install USB drivers which you should let it do as well.

    3) If your interface is plugged into a USB port, unplug it, leave it unplugged for 5 seconds then plug it back in. Depending on the version of Windows it may pop up with a USB Driver Installation Wizard or it may just automatically do its thing. If you encounter difficulties, try these instructions:

    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 19.6 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.

    5) You should get a message saying something about "First Use, No Config File". You should acknowledge that message then go to Options and click Test. In order to fully test the interface, it needs to be connected to a car so that the interface has 12V of power. It doesn't matter if it's a VW/Audi, just something with an OBD-2 port with the key ON. If you test without a car it will be unable to check for a firmware update and will be unable to update.

    6) If the Options>Test result shows everything OK but Firmware Update Required, click OK then Update. It should count up to 100%. When it's done click Close then Save.
    • HEX-NET or HEX-V2 interfaces need Internet access to update but do not need to remain connected to the car, just plugged in via USB. Use the Config button to update firmware as explained in this HEX-NET video or this HEX-V2 video. When it's done click Save.
    • Legacy dongle HEX-, Micro-, KII-, KEY- interfaces do not need Internet access to update but DO need to remain connected to both the car and USB. Click OK then Update. It should count up to 100%. When it's done click Close then Save

    7) At this point all of the buttons in VCDS should be available so you should try communicating with the car, for example by clicking on Select then 01-Engine then Fault Codes-02.

    If you encounter difficulties, check FAQ 2.4 and 2.5

    Specifically, check to make sure that Windows is not turning off the USB ports: go to Device Manager, Universal Serial Bus Controllers, USB Root Hub, Properties, Power Management, and uncheck "Allow Windows to turn off this device to save power". There are may be several entries with "Root Hub" so make sure to uncheck this on each of them like this:

    Make sure you have write permission where VCDS is installed (reinstall in the Documents folder if necessary), and remove any extension cable between the PC and the interface. Install and run the software while logged in as an Administrator if needed.

    We have had some reports from users of VCDS running very slowly after some recent updates to Microsoft Security Essentials virus scanner. If verify that is the problem, you can add VCDS to the Exception list in Security Essentials. As of October, 2017 BitDefender may prevent VCDS.EXE from starting. Also in November, 2017 we received a report that an expired McAffee prevented the VCDS.EXE from running.

    One customer reported success by completely removing VCDS then performing a registry scan and *.DLL cleanup followed by a reinstall. It shouldn't hurt to try this if you encounter difficulties.

    One more thing: if you are using a Virtualized OS like Parallels, Virtual PC, remember those are NOT SUPPORTED as explained in FAQ 1.4

    • We have some reports of customers having difficulty updating firmware or connection problems or even using VCDS at all. A Mac running Bootcamp is fine but any kind of virtual OS is not. If it works for you, great, but if it doesn't the first thing we will suggest is trying a real Windows PC.

    • We have had customers reporting problems using VCDS since they have something else connected to the diagnostic port, either a GPS tracker (which can be well-hidden) or add-on gauges like Polar FIS. VCDS needs exclusive access to the diagnostic port in order to communicate.

    • We have also had customers who were able to test VCDS successfully but the Config utility could not see the HEX-NET or HEX-V2 due to an HID utility for add-on mice or keyboards being in use at the same time. Run msconfig on your PC to check Startup programs and turn off any that may be interfering.

    • If VCDS won't start at all by clicking on the desktop or start menu shortcuts, try reinstalling VCDS and tell it to install 32-bit in a 64-bit system.

    • Error 39 in Windows 10 is mentioned in post #30 -and- post #31.
    Last edited by Andy; 10-24-2019 at 03:25 PM. Reason: Error 39 in Windows 10

  2. Likes Uwe, Eric, Dana, smokey08, DrPeter, Boki Ar liked this post

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts