It's really sad when so many vendors rely SO heavily on such a dangerous tool instead of writing things more safely. We've found even printer drivers don't like to install with our security in place (blocking autorun.inf files)
But when vendors decided to go against Microsoft's plans and certification requirements and install software under user profiles instead of under "program files" that sort of told me something...............
What we've done to get around this is allow autorun.inf files to do anything in a very specific folder, so our helpdesk staff puts anything they need to install into the special folder and runs it from there. So far, so good.................
What happens is that some of these installs "extract" the install files from the EXE that you run, then they move on via an autorun.inf file, and if that file can't be read, the extraction happens, the next EXE in line runs, but it literally stops from there.......... or you get other weird errors and they VARY WILDLY depending on the application's install processes. Some give no error and simply quit, since they can't read the autorun.inf file. Others give errors. Again, each will be different, so the specific error is unimportant in this diagnosis.
Bottom line, try to put the software into a folder where you have excluded your autorun.inf blocking.