I've actually observed the opposite. I upgraded sequentially through the versions (v7 → v10 → v12 → ... → v18), and with each upgrade I noticed additional features being added rather than removed. (BTW, if someone needs a Win7 VM with v18 or older versions, let me know)
What I still can't explain is why some vehicles don't report their VIN when Techstream performs the initial connection. This happened to me with a cheap MVCI clone on a 2021 RAV4. As soon as I switched to a VCX Nano, everything worked as expected—the VIN, model, and engine were detected automatically.
The last vehicle I connected to was a 2010 RX450h, and I had to select everything manually. I have no idea why the VIN wasn't detected. My only guess is that the ECU may have been replaced and never updated with the vehicle's VIN.
Has anyone else experienced something similar?
First, I'm apologizing in advance for the length of this post. Hopefully you see fit to actually read it, lol.
I read on a different post of yours that you're successfully using the VCX Nano. If you have the time, I'd greatly appreciate you answering a few questions about your setup. I can get connected to my 2024 Tundra, and it properly displays the VIN during the initial pop-up, and on the left sidebar where it also shows the vehicle build date. I can even the health checks, but I'm seeing some other strange behavior that's keeping me from registering a new key.
1. Are you launching Techstream using the patch that you can get from VXDiag? I chose to go the route of purchasing a key from someone who has a keygen. Since Techstream seems to start up and connect fine, I don't think this is my problem.
2. Which version of VX Manager are you running? I'm able to download and install V1.8.9.0601 just fine with Microsoft Defender running. But if I accept the prompt to update to V1.9.1.0420, then Defender goes nuts about Trojan viruses. I do think it's a little suspicious that this most recent version is not available for a stand-alone download from VXDiag and can only be obtained via following the update process of an already installed version. This is my main laptop, so I'm being pretty cautious right now.
3. Still talking about within VX Manager, what version of the Passthru and Toyota TIS "apps" are you running? VX Manager shows an update available for the Passthru app, but if I accept it then it's another spot where Defender goes crazy.
4. Switching to talking about Techstream, which VIM are you selecting? The drop-down menu shows I can select "Toyota - J2534" or "VXDIAG". I've been selecting the latter, since I'm using the VCX Nano.
5. Lastly, if you think it's vital to disable AV to get all of this working properly, what would be involved in me taking you up on your offer about a VM with Win7 and Techstream? I've never set up a VM, but I'm good at following instructions, lol.
While running Techstream, I kept getting a pop-up error telling me that my license was expired and I needed to update the VCI. I could tell this was a pop-up being generated by VXDiag not Techstream. I believe this was because I needed to update the license on the Nano itself. I've now done that, but I'm trying to iron out some of these other wrinkles before I make additional attempts at registering a key.
The other weird thing is that while trying to register a new key, I got to the point where it generates the seed codes, but weirdly the VIN that was displayed had an extra "1" at the end. I haven't run across anyone else mentioning this happening, so I don't know if this is normal or if it's the reason my key registration failed. Each passcode I purchase is $15 and is a one-time use, so I'm trying to figure this all out without burning through additional passcodes.
Thanks for any assistance or knowledge shared!
I've read mixed reports of whether it works with my 2005 Lexus. I'm not sure whether it supports K-line protocols or not but I'll soon find out.
