Over a year later, and I have finally figured this weird problem out. For anybody else who experienced this “problem,” which wasn’t many, need to install SSD5 into a “public” folder on the computer. Usually C:\Users…etc
For some reason, maybe it’s the way the drives were oriented and how they communicate permissions or allow them, a public folder is the full-proof way to always allow permissions for SSD5 and whatever other related resources to be called upon so to speak and work normally rather than be Blacklisted. Problem solved.