Hello and welcome tot the comunity.
BTW, I am also a Reaper 7.3.5 user.
Did you reboot your computer after the installation?
If not, please try and let us know.
Rebooted many many times, no problem loading a new instance of anything (aside from the plugin scan error, out of interest can other directories be scanned too? it only seems to look at one directory)
The main issue is when it’s integrated in a complex session of mine and I come back to load it up, there is a conflicting vst in there. But obviously finding it is a needle in a haystack and it’s my trusted workflow so I want to keep it’s integrity etc.
For now I can load my session in offline mode, remove scaler 3, reload it and my session is back, alas my work in scaler will have been lost…this is a temporary fix as I don’t want to keep sporadically losing work in scaler and rebuilding it according to my sessions
I’ve also tried different versions of Reaper so that can be safely ruled out.
I checked the faulting path in the report and it is the same as mine. Maybe just the vst is corrupt, but I will leave this to the developers. They are watching Scaler 3 Support thread so we can expect some fixes soon.