It absolutely did not affect all users. We've identified 3 people in total that were affected. The key was to override the default Windows VST2 installation folder, which included a subfolder of \DCO-106, and instead place the plug-in into a custom folder, without the \DCO-106, so that it shared a location with other files. Instead of just clearing out the old DCO-106.dll file, it went nuts and cleared out everything that was in the folder with DCO-106.dll.WasteLand wrote: Tue Oct 13, 2020 7:10 pm so the issue was only with non-standard vst directory? it didn't affect all users?
The issue is absolutely resolved.
- Dan @ Cherry Audio
