Verified VCDS User
- Jun 5, 2018
- Reaction score
- VCDS Serial number
Hi Dana,Hmm, there shouldn't be any differences that would explain this behavior but the Auto-Scan from that MS Surface may add clarity if you happen to have one saved.
In the meanwhile, if you still have the MS Surface it might not hurt to install VCDS Release 19 into a new folder (perhaps C:\Ross-Tech\VCDS-19.6.1) so it doesn't overwrite his older install and swap between your interface and his while re-coding the ABS to the existing value.
You could even take that a step further and re-code the ABS to the same using your Win 10 x64 PC and his interface with the current version of VCDS. Doing so may help rule out the interface (while eliminating the PC and VCDS version as possible causes).
I still have both interfaces. I just plugged mine in and tried to gain secure access. I used the key provided, which worked with my friends VCDS, and received the same error....
35 invalid key.
Is there anything I can do to help work through this issue with you? It seems apparent that there is something going on with my cable, computer, VCDS software/firmware, or a combination of them.
I’m available through email if it’s easier.