It has run very well on Windows 8. Just not compatible with Sample tank. Since my copy of Sonar Home Studio is 5 years old I can safely say it's time to upgrade. Teach me to try something new .

Updating Plugin Manager might help. I believe that Plugin Manager is a shared resource and installing a trial copy of the latest version of Sonar would effectively update Plugin Manager for the existing Sonar 7 installation. SampleTank might behave differently after the update. Just a suggestion.

opie1
...Since my copy of Sonar Home Studio is 5 years old...

 
So it's Sonar Home Studio 7 rather than Sonar 7. That was a slightly different product, released a year later, and after Sonar 8. Crazy times.

Kev999

chuckebaby
It probably has something to do with a product that was made for Windows XP (10 years ago).
Sonar 7 was released in Sept of 2007...

I've just looked at the Sonar 7 documentation and it says XP and Vista. For a short while I ran it on Windows 7 and it was very stable on that platform.

Maybe I need work on my approach,
The point I was trying to make to the OP is...it might be time to move to a newer version.

Pro audio 9.0 loaded my old projects and ran on Windows 7 as well but wouldn't load plug ins.
And Sonar 7 HS XL (which I also have) would run but wouldn't load certain plug ins anymore (like Studio Devil VGA) in Windows 10.

I have Sample Tank 2 and Sonik Synth 2! Try running Sonar in administrative mode, rescan and they should work!

ronboy1952
I have Sample Tank 2 and Sonik Synth 2! Try running Sonar in administrative mode, rescan and they should work!

 
This.
 
Many moons ago after installing X3 and taking the advice of someone here that I should select  "reset all" in the plug-in manager, I had quite a few problems among which Sampletank 2.5 and Miroslav which had always worked fine, were no longer recognised and wouldn't show up in the synth menu no matter how many re-scans I did. Open in admin mode and they were there and work fine. No idea why this should be, but it works for me.

Could it be a VST 3 issue?