Poser 7, initially, forced users to install content into the Poser primary runtime folder nested within Windows Program Files. Remember, this is in the Pre-Windows Vista era before UAC started to be a major headache towards Program File access. Jump ahead, Windows 7 through 10 blocks Program Files access thus preventing Poser from accessing or seeing any installed content in the restricted zone. That is why the most current versions of Poser offer an alternative, shared location for content installation. I scrapped my Poser 7 installation a long time ago and moved my entire runtime to a shared folder, linking it manually to my current iterations of Poser (Pro 2014 and 11). Transferring runtime content to a new installation is risky because so many scripts can be broken that way, easier to link than become frustrated from non-working content. Updating went flawlessly, retained my preferences, did not lose any installed content, did not lose any runtime folders (>20), and DSON still works. But I did install over my original Smith Micro install and any script that was manually imported still remains. Now, IIRC, many years ago there were problems with missing content after a Poser upgrade and it was discovered that much of the content was moved into a virtual location, not removed from the hard drive. There were several posts in the forum but for the life of me, I don't remember how long ago this happened not the titles of the posts addressing the solution.