Developer

Asok realises that doing – and in particular telling about – too much work backfires.

setup.exe is a file used to install programs. It’s frequently found on driver CDs and such alike, so when it fails to launch, it usually hurts double. The Web is full of reasons and solution attemps why this file won’t work and there is no general remedy. One has to check his or her system and compare to the solutions offered, with some luck one might fit.

A typical failure of setup.exe is noticable due to the lack of any activity whatsoever. A launch of the file results in nothing other than a dead process (0% CPU usage). If it hangs in there for a while like that, it’s safe to kill it and proceed to the steps below.

The most popular reasons of failure include, in random order,

• Virus/firewall software
• Bad registry
• Microsoft Outlook
• Old folder structure
• Missing temp folder
• 16bit

In my particular case, it seemed to relate to the recent installation of Norton 360 v2 on Windows XP. That means my reason of setup.exe failure was the “virus/firewall software” option. I wanted to install a network print server (hooking up my parallel laser printer to the local network) and neither the provided setup file on the CD nor any other downloaded would work.

The solution to this particular case:
(Please note that disabling the virus/firewall program from its own menu likely won’t solve the problem, therefore the more drastic method below)

1. Start > Run > msconfig
2. In first tab, click “Selective Startup”
   1. Disable “Load Startup Items”
3. Click “Services” tab
   1. Disable all processes related to the virus/firewall software/company.
4. Apply and close the program, follow it’s instruction to reboot.
5. Try if setup works now. Finish it and restart if necessary.
6. Redo step 1.
   1. Activate “Normal Startup.
7. Redo step 4.

Even though setup.exe may work during the procedure above, certain other functions might now until after a normal restart. In this case, installing the network print monitor as well as a new network port went well but the new network port could only be accessed by the network print monitor and its install wizard until after a normal restart.

Below some solutions to other possible causes:

• Bad registry entries
  1. Start > Run > regedit
  2. HKLM/Software/Microsoft/Windows/CurrentVersion/App Paths/setup.exe
  2a. Make sure that the default entry is blank and no “path” data entry.
  If either of those two entries contain data, then under some circumstances Windows will try to run the setup.exe pointed to by the registry instead of the setup.exe you are actually trying to run.
• Microsoft Outlook
  Close all Microsoft Outlook (Outlook Express) applications and processes.
• Old folder structure
  Some old install files might look for “DOS-like” file names and folder structures: they might not be able to recognize folder name “Documents and Settings” but instead would require it to be named “Docume~1″.
  Create a folder such as c:\temp and start setup.exe from there.
• Missing temp folder
  Also part of the old install files is the problem of a missing c:\temp folder. Create it for the sake of installation and remove it at will if no longer necessary thereafter.
• 16bit
  Those installation files won’t run in Windows XP.
• Other
  The Web is full of setup.exe related problems and solution attempts. Best suggestion would be to search for specific error messages / descriptions matching the individual problem.

Microsoft Installer (MSI) files often contain files you might want to use individually without actually installing everything by executing the main MSI setup file.

Users of Windows Mobile (WM) frequently run into this problem when they want to install an application only on their mobile device and not first on their computer.

If you have Windows Installer installed:

1. Open Command Prompt: Start > Run > “cmd”
2. Either go to the folder where the MSI file is located or use full path:
   msiexec /a path_to_MSI_file /qb targetdir=path_to_target_folder

For more information about msiexec execution:
Command-Line Switches for the Microsoft Windows Installer Tool