On a different winxp sp3 box than I've described here before, I have tcmd 9-13 installed. I consider this box my main xp box. I have tcmd 12.11 and 13 open. I ran update from tcmd 13, and as soon as it starts to download an update, I closed the main tcmd 13 and left the update process run. I have been doing this for many version updates since v 9. After the update ran, it said that there were components that it needed to update that it could not. It was referring to the running session of tcmd 12.11. Why would upgrading v 13 trigger an error because of v 12.11 being open? I have already described v13 clobbering a v12.11 upon installing v 13 to a thumbdrive. There seems to be some kind of interaction btwn installing v 13 and an already installed v12.11. Maybe some sharing of files? I don't know, but the install program for v13 is causing errors/messages to be generated from v 12.11. I am posting this because I believe there is a bug in the install routine for v13; I have never seen this behavior before involving v9-12. Each subsequent version installation really had no effect on earlier versions. This installation issue is new for v 13.