I am pretty sure I have been doing it right but I printed out the doc and went to the car to remove it and follow all the steps to reinsert it. I have also checked the black cube for connection. And I can not get a picture inside the lid but I was also very careful on putting that on and feeling for evidence it was clicking in place and that the pin in the top right was properly lined up.
Done - I will see how/if this improves things. I guess it is easier to explain that I was getting a hyper-v error even trying to launch the TIS VirtualBox environment from alfoy's links above. I then turned on "virtualization" in the BIOS (not hyper-v) and then I stopped getting the hyper-v errors trying to launch. I can now launch the virtual environment inside VM VirtualBox and can connect my nano and have it report back in the VX Manager that it is visible. I can launch the version 12 included of Techstream and configure things to work with the VXDiag but then when I try to connect to the car it would not connect. "toyota techstream error s302-05" I'll see if the added expansion pack helps with this issue.
If you're still having issues with VB, then try a fresh install using this link : https://blog.obdii365.com/2022/06/06/free-download-toyota-techstream-v17-10-012/
Bottom Line on Top: I have finally resolved this. Long story since my last post I've actually experienced "when it rains it pours". We had the most rain fall in a 24 hour period ever in the history of our area. This caused a lot of flash flooding in our area and that included washing out a good portion of our gravel driveway. Had to use a front loader to recover as much as possible from the highway in front of our place before the county hauled it away. Tractor got stuck and had to use a truck to pull it out. Lost my keys but didn't know it until after I spent 2 hours moving gravel. Spent hours with a rake and shovel trying to find the keys. Found a friend with a metal detector that let me borrow it and I spent an hour finding the keys. I did all this alone as around my last post my wife of 25 years finally left and took my boys with her. Not the emotional loss you'd think it was as I've been the only one trying for the last 16 years to make it work and I have since given up and she finally just moved out like she's been asked to several times. The hard part was not having a helper around to go'fer things, etc. Boy's will be back on Wed and we'll rotate from here on out. OK - to the actual fix... (aside from replacing the brake actuator) Each of you have been extremely helpful with places to look. Items to install. And expertise. I can't thank you enough. I was able to use the most recent version with a patch to finally adjust the breaks through TechStream for a reasonable price. However, before I could get to that I figured something else out. It was the side comment about checking the voltage at the 12v battery and in the front... Turns out that the 12v battery was basically dead causing many extra dash lights to come on but the system to not actually fully come on and confuse everything. Even after figuring out the voltage was low it appears my problem was prolonged because while the battery charger was on it the tailgate was "propped" open (maybe an inch - just not latched) because the drop cord fed into there (apparently causing internal lights to be on - unnoticed by me). And also somewhere along the line I had inadvertently caused the turn signal to be on all continually draining the battery while attempting to be charged. Today I connected my Toyota Sienna to the 12v battery with jumper cables for about 40 minutes while I also ran TechStream and went through the utilities. I've driven a couple times since and no dash lights appear and it brakes as expected. Actually feels like it is running better than any time during the 13 months I've owned the vehicle. Those who took the time to respond here were simply amazing and very patient with me. You guys are the best. Thank You!
Congrats, what we like to hear. Struggling 12 volt battery has a tendency to throw a wrench into diagnosing CELs.