Does running SONAR as admin addresses this specific issue?

I suspect I've never had a problem with Sampletank 2 (in any version of Sonar) because I don't install anything on my C: drive normally.  So it's issue never really came up.  But something has changed in how Bit Bridge works that is causing Sampletank to now have an admin right issue it's never had before.
 
Running Sonar as Admin does seem to get around it, but it's not an ideal solution though. Perhaps if I understood what has changed I could mitigate it?

Noel, I will give this a it a try in the morning. 

subtlearts
Sampletank 2 runs fine here under Everett, as long as I run Sonar as administrator - otherwise it fails. It's been like that for some time now though.

I just re-install ST2 (2.5.4) still ST2 is working fine & I run Sonar as Admin.  I can confirm what 'subtlearts' wrote is true. Tim410 you should give it a try..

Thanks Alfabooty and subtlearts for verifying this, something has definilty changed in this new release. I did not need to elevate privilegies before.

timp410
Thanks Alfabooty and subtlearts for verifying this, something has definilty changed in this new release. I did not need to elevate privilegies before.

Indeed. Since the new Platinum the more they fixing stuff & at the same time they broke it. 

msorrels
Running Sonar as Admin does seem to get around it, but it's not an ideal solution though. Perhaps if I understood what has changed I could mitigate it?

Thank you - this is useful information.
 
Bitbridge was rebuilt in this release for the first time in several years (since we acquired the code which was originally licensed). The reason we changed Bitbridge this release is because we fixed a serious issue that would cause crashes with plugins that had a large amount of persist data. 
 
We built it with the newest Microsoft compiler and its likely that this enforced some of the more strict user account control that Microsoft has. As a result it is likely  exposing UAC bugs in the original plugins preventing them from loading for unknown reasons to us. While this is technically not a bug in our code we will do what we can to work around it since these are legacy plugins. Once we have addressed this issue we will release an update to Bitbridge.
 

For what it's worth, despite my other serious misgivings about this release, the Bitbridge change has apparently fixed one of my other synths which would never initialise properly until I loaded a preset for it. So it's not all bad!

One thing I did notice while doing a full rescan is that one of my older Crysonic (yes I still have them) plugins crashed freeing memory in the Microsoft C runtime DLL (I think it was msvc90 but I can't remember and don't have time this morning to reproduce).  As a rule it's very tricky to mix C runtime DLLs.  This was different.  It's not that big a deal but a full reset and scan had a handful of 32bit plugins that were working fine before crashing.  Nothing I cared about really though, but very different.
 

This issue has nothing to do with runtime dll's. Keep in mind that at Cakewalk we do our best to support legacy plugins (more so than any other DAW) but there is only so long that we can support plugins that have bugs and limitations that make them obsolete to run in modern software. If it indeed becomes impossible to support we may release the old bitbridge as is with no fixes as an alternate download, and move on to the newer version which will have future fixes.