Juce OutOfTheBox Audio App on Windows 10

Hi all I created a OutOfTheBox Audio App with Projucer 5 ( juce-huckleberry-windows.zip ) on Windows 10 with Installed Visual Studio 2013. As I activated the Live Coding right after creating the new Project in Projucer I got a lot of Errors like:

MainComponent.cpp: ‘memory’ file not found
Main.cpp: ‘memory’ file not found
include_juce_audio_basics.cpp: ‘memory’ file not found
include_juce_audio_devices.cpp: ‘windows.h’ file not found

And so on. Always ‘memory’ and ‘windows.h’. I guess there should be installed something. But If I check the Include Folder ( C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include ) then I can find such Files. Not ‘windows.h’ but a ‘memory’ and a ‘memory.h’ File.

Does someone know how I can fix that ?

Thanks a lot

Hi Dirk,

same here with Visual Studio 2017 / Windows 10.
Did you find a solution for this in the meantime ?

Thx in advance,

Hi Matthias, no I don’t. My hope was to get any Help here in the Forum. But seems not to be helpfull.


I have the same problem but with Visual Studio 2015. In fact my VS is installed on D instead of C, so I copied a link to the ‘VC\include’ folder in System header paths in Projucer (as well as other links to required files) but still cannot bring the live-build engine to life. Many different errors about missing files although the links seem to be correct.

Of course all my projects compile and build correctly in Visual Studio. This is related to the live-build engine.

There will be a fix for this shortly.


This is now fixed in the 5.0.1 release.


The Version 5.0.1 doesn’t fix it. You see for a second the Errors:

MainComponent.cpp: ‘memory’ file not found
include_juce_audio_basics.cpp: ‘memory’ file not found
include_juce_audio_devices.cpp: ‘excpt.h’ file not found

And then the Errors disappering and one sees this Message:

JIT process stopped responding!


I just pulled newest develop and compiled Projucer again.
Unfortunately this fix didn’t work for me eighter.

By the way: my system was a clean install Windows Pro 10 (german version) and
then installed Visual Studio 2017 (with NO VS2013 / VS2015 installed before).

So, in my case the include file ‘windows.h’ exists in the following folders:
“c:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Include\Windows.h”
“c:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Include\Windows.h”
“c:\Program Files (x86)\Windows Kits\10\Include\10.0.15063.0\um\Windows.h”
“c:\Program Files (x86)\Windows Kits\8.1\Include\um\Windows.h”

and the include file ‘memory.h’ exists in the following folders:
“c:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt\memory.h”
“c:\Program Files (x86)\Windows Kits\10\Include\10.0.15063.0\ucrt\memory.h”

edit: i just added some more infos and a screenshot of the projucer error messages…

We’ve just released a new version of the compile engine that should have the correct include paths for Visual Studio 2013. To get it, you need to delete all instances of the old JUCECompileEngine.dll file which may be located next to your Projucer.exe file if you downloaded JUCE from https://www.juce.com/get-juce and may also be in your user application data directory (usually at \Users\username\AppData\Roaming\Projucer-version number). Once these have been removed you should see a download button in the live-build tab of the Projucer when you re-open it - this will download the newest version. @MatthiasGehrmann it looks like you are still using an older version of the compile engine, can you try these steps and see if it works?

1 Like

Hi Ed, I removed everything from \Users\username\AppData\Roaming\Projucer and also removed the JUCECompileEngine.dll. I could then reload ( Download ) it with Projucer directly and then I could enable the Live Coding. Then it compiled correctly without any Error Message. But after the JIT Initialization the JIT process stopped working again. Are there any Log Files ?

Thank’s a lot Ed!

Does the compile engine keep crashing if you re-enable it? Can you try and use the compile engine on something like the JUCE Demo project and see if that works OK? If it does then it could be something in your project that’s causing issues.

Unfortunately we don’t generate any detailed log files from crashes but it’s on our backlog.

Hi Ed, yes if I Re-enable it, it will crash again. Also Demos like ‘AnimationAppExample’ will crash.


That’s strange - I can’t reproduce it running JUCE 5.0.1 on Windows 10 with the latest compile engine build. Can you make sure you’re also on the newest version of JUCE by either re-downloading the .zip from www.juce.com/get-juce or pulling the latest tip from GitHub?

Hi Ed, I downloaded it again and also removed the …Engine.dll to get the newest one. But no luck so far - it doesn’t work. I will try it on a different clean Machine and will let you know. Thank you for your Help !

OK, I’m afraid I can’t think of anything else to try. Please let me know how you get on!

ahhh okay, i would have never thought of that.

and yes!
i simply deleted the old JUCECompileEngine.dll and downloaded a newer version directly in the projucer and it works :slight_smile:

thank you very much !

1 Like

I read through the relevant forum posts and the github issues. i’ve tried everything, including the advice above: delete JUCECompileEngine.dll, download within Projucer, and try again… but it does not fix the include errors (i.e. cannot find memory, windows.h, excpt.h, and “jit not responding”, etc.).

I’m using…

  • Windows 10 Enterprise Version 1607 Build 14393.1198
  • Visual Studio Community 2017 Preview (Version 15.3)
  • Windows 10 SDK (10.0.15063.0)
  • Projucer 5.0.1

I’ve rebuilt Projucer from the git master branch and the git develop branch, but both builds produce exactly the same results: same include errors.

Where is your VS installation? The live-build engine looks for those files in

C:\Program Files (x86)\Microsoft Visual Studio (also \Microsoft Visual Studio 14.0 and \Microsoft Visual Studio 12.0 for VS2015 and VS2013, respectively)


C:\Program Files (x86)\Windows Kits

Thanks for your reply.

I didn’t deviate from the default installation options when I installed
Visual Studio Community 2017 Preview or the Windows 10 SDK. Here’s some
info from the command line:

$ cd 'C:\Program Files (x86)\Microsoft Visual Studio\'
$ dir

    Directory: C:\Program Files (x86)\Microsoft Visual Studio

Mode                LastWriteTime         Length Name
----                -------------         ------ ----
d-----        3/10/2017  12:11 PM                2017
d-----        5/19/2017   1:36 PM                Installer
d-----        5/19/2017   1:38 PM                Preview
d-----        5/19/2017   2:00 PM                Shared

$ cd .\Preview\Community\
$ dir

    Directory: C:\Program Files (x86)\Microsoft Visual

Mode                LastWriteTime         Length Name
----                -------------         ------ ----
d-----        5/19/2017   1:41 PM                Common7
d-----        5/19/2017   2:01 PM                CoreCon
d-----        5/19/2017   1:59 PM                DesignTools
d-----        5/19/2017   2:02 PM                DIA SDK
d-----        5/19/2017   1:41 PM                ImportProjects
d-----        5/19/2017   1:42 PM                ItemTemplates
d-----        5/19/2017   1:45 PM                JavaScript
d-----        5/19/2017   1:43 PM                JS
d-----        5/19/2017   1:43 PM                Licenses
d-----        5/19/2017   1:45 PM                MSBuild
d-----        5/19/2017   2:02 PM                SDK
d-----        5/19/2017   2:00 PM                Team Tools
d-----        5/19/2017   1:43 PM                TS
d-----        5/19/2017   1:41 PM                VB
d-----        5/19/2017   2:01 PM                VC
d-----        5/19/2017   1:41 PM                VC#
d-----        5/19/2017   1:43 PM                Web
d-----        5/19/2017   1:41 PM                Xml

$ cd 'C:\Program Files (x86)\Windows Kits\'
$ ls

    Directory: C:\Program Files (x86)\Windows Kits

Mode                LastWriteTime         Length Name
----                -------------         ------ ----
da----        5/19/2017   1:14 PM                10
da----        5/19/2017   1:13 PM                8.1
d-----        5/19/2017   1:43 PM                NETFXSDK

I confirmed that windows.h is under Windows Kits somewhere.

Is the Live Engine closed? I could not find it in the source tree.
Otherwise I would have investigated this myself.


– karl

That looks OK so far. Can you confirm that memory is located at

C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.10.25017\include

and windows.h is located at

C:\Program Files (x86)\Windows Kits\10\Include\10.0.15063.0\um