# Win32 build in Juce 5.4.3 **URL:** \ **Category:** Audio Plugins\ **Created:** [May 27, 2019, 8:32pm UTC](https://forum.juce.com/t/win32-build-in-juce-5-4-3/33606 "2019-05-27T20:32:37Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![mifrag](https://avatars.discourse-cdn.com/v4/letter/m/0ea827/32.png) [@mifrag](https://forum.juce.com/u/mifrag)\ **Post date:** [May 27, 2019, 8:32pm UTC](https://forum.juce.com/t/win32-build-in-juce-5-4-3/33606/1 "2019-05-27T20:32:37Z")
Hi, I created an empty new audio plugin project in Juce 5.4.3. VST-3 builds in Visual Studio 2017/Win32 are not recognised in both Cubase 5.1 win 7 64 and Reaper win 10 64 that I ve tried although they run ok in the juce plugin host. Builds from Juce 5.3.2 are recognised fine. Anyone faced that? Thank you ---
**Author:** ![daniel](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/daniel/32/790_2.png) [@daniel](https://forum.juce.com/u/daniel)\ **Post date:** [May 27, 2019, 8:39pm UTC](https://forum.juce.com/t/win32-build-in-juce-5-4-3/33606/2 "2019-05-27T20:39:47Z")
A quick internet search tells me, that Cubase 5.1 is from 2009 and likely to be pre-VST3… Are you building with legacy VST SDK? You are probably aware, that VST had to be removed, and if you have the License, that you will have to set the path to the old SDK manually… See: [The removal of JUCE’s embedded VST2 SDK](https://forum.juce.com/t/the-removal-of-juce-s-embedded-vst2-sdk/29994) ---
**Author:** ![tomto66](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/tomto66/32/4916_2.png) [@tomto66](https://forum.juce.com/u/tomto66)\ **Post date:** [May 27, 2019, 8:58pm UTC](https://forum.juce.com/t/win32-build-in-juce-5-4-3/33606/3 "2019-05-27T20:58:50Z")
Reaper should do VST3 though, no? ---
**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:** [May 27, 2019, 10:21pm UTC](https://forum.juce.com/t/win32-build-in-juce-5-4-3/33606/4 "2019-05-27T22:21:07Z")
> [@mifrag](#): > > Builds in Visual Studio 2017/Win32 are not recognised in both Cubase 5.1 win 7 64 and Reaper win 10 64 Using a 32-bit plugin in a 64-bit host doesn’t sound right… ---
**Author:** ![mifrag](https://avatars.discourse-cdn.com/v4/letter/m/0ea827/32.png) [@mifrag](https://forum.juce.com/u/mifrag)\ **Post date:** [May 27, 2019, 10:54pm UTC](https://forum.juce.com/t/win32-build-in-juce-5-4-3/33606/5 "2019-05-27T22:54:08Z")
Hi, sorry for not being clear. Its VST 3 that I try. ---
**Author:** ![mifrag](https://avatars.discourse-cdn.com/v4/letter/m/0ea827/32.png) [@mifrag](https://forum.juce.com/u/mifrag)\ **Post date:** [May 27, 2019, 10:57pm UTC](https://forum.juce.com/t/win32-build-in-juce-5-4-3/33606/6 "2019-05-27T22:57:45Z")
It is a common thing to do. The other way around is not supported of course. ---
**Author:** ![xenakios](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/xenakios/32/4047_2.png) [@xenakios](https://forum.juce.com/u/xenakios)\ **Post date:** [May 27, 2019, 11:32pm UTC](https://forum.juce.com/t/win32-build-in-juce-5-4-3/33606/7 "2019-05-27T23:32:13Z")
Reaper’s bit bridging (that allows for example to run 32 bit plugins with 64 bit Reaper) does not work with VST3 plugins. If you want to test a 32 bit build of your VST3 plugin in Reaper, use the 32 bit version of Reaper. ---
**Author:** ![mifrag](https://avatars.discourse-cdn.com/v4/letter/m/0ea827/32.png) [@mifrag](https://forum.juce.com/u/mifrag)\ **Post date:** [May 28, 2019, 7:25am UTC](https://forum.juce.com/t/win32-build-in-juce-5-4-3/33606/8 "2019-05-28T07:25:55Z")
Its the second time you save me from reapers wierd behavior. Thanks a lot!