Hi, the program recently updated to a newer version. It says that it needs to update the firmware as well, but when going to test it does that ok, and then config, it says it's unable to open the interface which keeps repeating itself. After ok'ing the dialog box and pressing update, it says i have the latest version, but I cannot get any update. It seems not to connect to the interface anymore. Thanks.
VCDS not working after update
- Thread starter Yves
- Start date
Try booting your computer into safe mode with networking, and then try to perform the updates like that. Most likely some third party software like mouse or touchpad software is interfering with the ability to open the interface.
- Joined
- Apr 13, 2015
- Messages
- 2,873
- Reaction score
- 2,200
- Location
- Milwaukee, Wisconsin USA
- VCDS Serial number
- C?ID=174556
Perhaps one of these (links) may help:
VCIConfig has not changed since the last version, so that isn't the problem.
But do have a look here:
forums.ross-tech.com
-Uwe-
But do have a look here:
Solved: "Unable to open interface" error with Logitech Keyboard/Mouse
Hey all! Spent a good hour troubleshooting yesterday and figured I'd post to save someone some headache (and maybe provide our wonderful developer @Uwe with a future fix): I reinstalled VCDS for the first time in a while, and upon connecting my genuine Hex-V2 interface it saw the interface and...
-Uwe-
Similar issue with latest soft update to v.24.5 for HEX-V2.
Downloaded and installed the new version. On starting the application, message to check FW (Options > Test). Clicking on the Config button didn't open the Config extension. Trying to open Config from Start Menu > VCDS > Config didn't work either.
I'm using an older Windows tablet running W10 Home edition. Since the tablet has only 30Gb storage, and OS takes about 23G, I'm keeping it as lean as possible (deleted any W apps possible, no other apps running, except Firefox to be able to email logs to my Mac).
In the end, I've uninstalled the previous VCDS app and reinstalled v.24.5. Got the same FW required update message and used the Config extension to update. Everything went smoothly and in the end was able to scan as usual.
Downloaded and installed the new version. On starting the application, message to check FW (Options > Test). Clicking on the Config button didn't open the Config extension. Trying to open Config from Start Menu > VCDS > Config didn't work either.
I'm using an older Windows tablet running W10 Home edition. Since the tablet has only 30Gb storage, and OS takes about 23G, I'm keeping it as lean as possible (deleted any W apps possible, no other apps running, except Firefox to be able to email logs to my Mac).
In the end, I've uninstalled the previous VCDS app and reinstalled v.24.5. Got the same FW required update message and used the Config extension to update. Everything went smoothly and in the end was able to scan as usual.
I just ran into this problem and resolved it.
Lenovo Legion Y545
Windows 11 Home
VCDS 24.5.0
HEX-V2
The culprit was Logitech Lamparray. I ended the task from task manager and it was able to update the firmware. This process took me like 2 hours to troubleshoot but thanks to this thread I was able to narrow it down to good old Logitech drivers.
Lenovo Legion Y545
Windows 11 Home
VCDS 24.5.0
HEX-V2
The culprit was Logitech Lamparray. I ended the task from task manager and it was able to update the firmware. This process took me like 2 hours to troubleshoot but thanks to this thread I was able to narrow it down to good old Logitech drivers.
Thank you for the useful information.
I have a wired Logitech keyboard that I sometimes connect via USB to my laptop.
I spent ages trying to figure out why it wasn't recognizing the interface.
Starting in safe mode didn't work for me either, as I don't have a network connection and Wi-Fi doesn't work in that mode.
After reading your post, I ended the task, and the update worked without any problems.
Thank you.
Awesome!
- Joined
- Dec 16, 2014
- Messages
- 9,023
- Reaction score
- 8,636
- Location
- Westbury, UK
- VCDS Serial number
- C?ID=1423
I'm still having problems with VCIConfig claiming my HEX-NET is already in use, but VCDS sees the HEX-NET and runs fine.
I spent a couple of hours yesterday looking at all the processes running on my Windows laptop, but no Logitech drivers or software - so I'm stuck unable to update the firmware on my HEX-NET.
All other suggestions welcome...
Shaun has an idea regarding VCIConfig. He may have something for you to test soon.
-Uwe-
Those of you with USB issues, feel free to give this VCIConfig a try: https://vcds-cloud.com/VCIConfigV2.301-HID-5-24.zip
- Joined
- Feb 13, 2014
- Messages
- 2,888
- Reaction score
- 3,321
- Location
- Magdeburg, Germany
- VCDS Serial number
- HN0-nnnnnn
Please use this updater instead, install it on top of your existing VCDS installation.
- Joined
- Dec 16, 2014
- Messages
- 9,023
- Reaction score
- 8,636
- Location
- Westbury, UK
- VCDS Serial number
- C?ID=1423
Will try as soon as I'm back home and report back.
- Joined
- Dec 16, 2014
- Messages
- 9,023
- Reaction score
- 8,636
- Location
- Westbury, UK
- VCDS Serial number
- C?ID=1423
- Joined
- Apr 3, 2020
- Messages
- 1,281
- Reaction score
- 1,159
- Location
- Germany (AIB)
- VCDS Serial number
- C?ID=56975
Fixed on my Office Notebook the issue with our telephone software. No no need to close it for update interface anymore. Thanks @Shaun
Last edited: