NI has reproduced this issue and found one possible cause. This behaviour can occur if you have a particular registry key present on your system. The NI autorun.exe application uses Windows APIs to read configuration information from autorun.inf located in the same folder as autorun.exe. When the particular registry key is on the system, it causes the Windows APIs to read from an autorun.inf file in a folder pointed to by the registry key(s) instead of from the autorun.inf in the folder with autorun.exe.
To see if this is the cause of your issue, check for the presence of either or both of the following registry keys (case doesn't matter):
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\IniFileMapping\autorun.inf
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\IniFileMapping\autorun.inf
You can work around this error by not running the autorun at all. Instead, run the appropriate setup.exe directly.
Alternatively, you can modify your registry to remove or rename the offending registry keys, either permanently or temporarily. If you choose this alternative, please read the following Microsoft KB to understand the risks and proper processes for modifying your registry: http://support.microsoft.com/kb/136393.
We plan to modify the NI autorun to avoid this issue in future versions of NI software.
