Scaler 3.05 VST3 in Windows 10 scan fails with error 2 and no new plugins seen

Scaler 3 Support Bug Reports
1

When I try to scan VST’s in Scaler 3 I get an error 2 message. I have deleted the file in the appData folder that Scaler 3 creates and rebooted without changing the behavior. I have done it with with my anti virus software disabled. I have scanned the VST2 folder alone and gotten the error. I have scanned the VST3 folder alone and gotten the error. This happens both in the standalone version and the VST3 version of Scaler 3.05 in Ableton Live 12.1.

When I first installed Scaler 3 I did a scan with just 2 plugins in place, Unify and Stylus RMX. They both still show up but nothing else seems to be seen with subsequent scans and I get error 2 as stated.

I am on Windows 10 Home 64 bit
OS Build19045.5737

Processor 11th Gen Intel(R) Core™ i7-1165G7 @ 2.80GHz 2.80 GHz|
|Installed RAM|16.0 GB (15.7 GB usable)|
|Storage|477 GB SSD Intel Optane H10 with SSD 512GB|
|Graphics Card|Intel(R) Iris(R) Xe Graphics (128 MB)|
|System Type|64-bit operating system, x64-based processor|
|Pen and touch|Pen and touch support with 10 touch points|

2

I followed the instructions for a clean reinstall and then did the plugin scan for VST3 plugins at the end of the install process and found that my plugins are now all showing up and I am not getting the error 2 anymore. I guess this is solved now at least for me for now.

3

This is how one user fixed this problem:

4

That’s pretty interesting. I checked and the Scaler 3 folder that was the parent of those was read only so the subfolders probably had the same permissions as I did not install the app with admin privileges. I changed the protections to allow write access so that hopefully I won’t have any problems with trying to rescan my plugins.

5

Also experiencing the same Error2 bug when using the Windows standalone app or as a VST3 within Reaper. I don’t think the workaround is sufficient for normal users who just want to simply rescan without issues after adding new plugins.

6

Hi @BredS are you still unable to resolve this plugin scan error? We are looking into this. Another temporary workaround seems to be opening Scaler 3 standalone via right click - run as administrator. This should allow the plugin scan to complete without error, but please let us know if it does not.

7

Hi Tristan.
Still Error2 when running normally.
Running as admin it re-scans successfully.
Regards.