# How to configure VST3 settings to eliminate errors

**URL:** <https://forum.juce.com/t/how-to-configure-vst3-settings-to-eliminate-errors/36992>\
**Category:** General JUCE discussion\
**Created:** [January 7, 2020, 1:01am UTC](https://forum.juce.com/t/how-to-configure-vst3-settings-to-eliminate-errors/36992 "2020-01-07T01:01:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zen13](https://avatars.discourse-cdn.com/v4/letter/z/c68b51/32.png) [@Zen13](https://forum.juce.com/u/Zen13)\
**Post date:** [January 7, 2020, 1:01am UTC](https://forum.juce.com/t/how-to-configure-vst3-settings-to-eliminate-errors/36992/1 "2020-01-07T01:01:41Z")

</div>

Hi new guy here. Ever since I enabled the “JUCE\_VST3\_CAN\_REPLACE\_VST2” option inside the plugin\_client module, I’ve been getting a couple errors. For example:

_Cannot open include file: ‘pluginterfaces/vst2.x/vstfxstore.h’: No such file or directory synth\_VST3 C:\Users\xxxxx\Juce\modules\juce\_audio\_plugin\_client\VST3\juce\_VST3\_Wrapper.cpp_

My option was using global path for this module, and I also placed the SDK folder in the same directory as JUCE applications for the global paths option. One question I have is for the VST (Legacy) SDK, should I also set the path to \Users\xxxx\Juce\VST\_SDK\VST3\_SDK?

---

<div class="post-metadata">

**Author:** ![mcmartin](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/mcmartin/32/7432_2.png) [@mcmartin](https://forum.juce.com/u/mcmartin)\
**Post date:** [January 7, 2020, 7:42am UTC](https://forum.juce.com/t/how-to-configure-vst3-settings-to-eliminate-errors/36992/2 "2020-01-07T07:42:30Z")

</div>

You should enable `JUCE_VST3_CAN_REPLACE_VST2` only if you already have a VST2 version of your plugin and you want DAWs to support loading the VST3 version in place of the VST2 one, to make your users smoothly transition from one format to the other.

This means that you normally have already built a VST2 plugin and you have a copy of the VST2 SDK. Then you can point Projucer to that SDK, using the global paths, or in the exporter settings.