Deployment and Versions

I'm not sure if I'm doing something wrong here or what, but I have run into an issue several times now where for example, new product uses 17.2 components, but an older product of ours hasn't been updated in a while and still uses 16.4 components. If you install a copy of older product after newer product is already installed, new product is now broken, I guess because when old product got installed it unregistered the newer OCX files when it registered the older ones. I am putting them always in the Windows system folder. My installer can't avoid  this using it's normal means since the new version uses different filenames from the old ones, but apparently the same GUID internally. Is there a good way to prevent these sorts of issues?

Thanks