I think we are all saying the same thing different ways here.

The basic runtime msvbvm60.dll is on the systems but that is not what is really needed to run a basic program. So whats the use of not including that one single file? You have to have an installer anyways regardless of that. I dont think there is a decent program that anyone would install that only used the msvbvm60.dll anyways.

The VB "runtimes" are pural so its not just isolated to the single virtual machine dll but several core vb dll/ocx's. This is the main issue and why its so important to not depend on only the msvbvm60 being present.