The article linked below describes the exact problem I have when deploying software on a different computer. The article has the solution - have the user install Visual C++ x64 and x86 that works for me, but I don't like to give the end user two distributions and have them install two pieces of software, so I was wondering if there's a more elegant solution to this. Would it be possible to somehow include Visual C++ installers along with my main installer so they're installed first, something like a batch installer file?
For a single installer, you could set that to run in Advanced>>Run Executable at End of Installer. But you should probably use a batch file to delete the runtime installer after it is done.
You could create a batch file and have the user run that or you could try an external installer program (like Inno Setup) to wrap all the installers into a single installer.
