Having the option for multiple user module search paths is a bit problematic. It’ll work fine if you’re only ever opening projects that have been created on the same machine as the Projucer that saves them, but if you want to export to another machine then you’ll run into problems like the one you posted.
The issue is that in order to determine which of the folders the module that you are including is contained in, which is needed to added a folder reference to e.g. a Visual Studio solution, then the Projucer needs to be able to scan the specified folders. Obviously there’s no way to do this if you aren’t running on that machine. I think the best thing to do here to avoid any further confusion is to remove the ability to specify multiple global user module folders and instead only allow a single path (like the JUCE module path). I’ve pushed this change here. You’ll need to re-compile the Projucer from the
develop branch, and move your user modules to be in a single, top-level directory (they can be in subdirectories within this one however).