Use of the Microsoft runtime library msvcr100.dll is critical, but using msvcp100.dll is a mistake because we do not ship that library.

In the makefiles, either at image creation (Release.gmk) or in the install makefiles, or maybe both, we should run dumpbin /dependencies and make sure we are not dependent on these files.

Recording the library and exe dependencies in the log might be a good thing to have anyway, perhaps a ldd -r on Solaris/Linux too.
Although there are libraries where the 'ldd -r' will complain about missing libjvm.so, may need to temporily set LD_LIBRARY_PATH to point at a libjvm.so before running ldd -r.???

IF we deploy a jdk that has a dependency on msvcp100.dll, as soon as it is run on a fairly clean windows system (one without VS2010 installed) then the java will fail.
Also make sure the debug runtime msvcr100d.dll is not used. See 6912135.