(Note the emphasis on if, only if this is a different version an error can occur which may explain why things worked fine in R2013b but R2014a needed a workaround for 'Image Analyst'). If that is an different version this can lead to the errors. In that case your standalone will get to see this tbb.dll. Some other ('less nice' in terms of not trying to influence other applications) application may have decided to place a tbb.dll here though. 'The Windows\System32 directory.' For things to work correctly tbb.dll should not be found here.As suggested by Peter though you can place a manual copy here of the right version (the one included with MATLAB/MCR) to work around issues which could occur in the further steps. 'The directory from which the application loaded.' for a standalone this is the location containing yourStandalone.exe (which is not the MCR\bin\$arch directory).Then at a later point when tbb.dll gets loaded this is resolved in the following way: It then determines where bin\$arch is (relative to the location of mclmcrrtM_N.dll) and it adds this directory to the front of PATH (for the current application only, not the system wide setting). Directories on the PATH ' (MCR\runtime\$arch directory in this case). A standalone basically starts with loading mclmcrrtM_N.dll and this should be found on '5. For a MATLAB Compiler Standalone however this story is different.
