The silent installation with MSI is pain for me from days.
I am facing MSI 1603 (Fatal Error) Exception on my testing PCs. All of them are non-development machines and so they may not have .Net Framework installed.

There could be several reasons for the above mentined error as under ...

1. This error is known to occur on computers that do not have enough disk space for the installation.
I have almost more then 1 GB place clean.

2. The Windows Temp directory is not clean.
I have cleaned many of them manually but still the same error

3. A certain file on the machine is locked. To fix this, close all applications running in the background. Reboot computer and run the installation again.
I have rebooted the PC and tried too.

4. If you are using Windows 95,98,ME, 2000 or NT, the Windows Installer Service may not be properly installed on the machine. Update the system with the latest Windows Installer service.
I have downloaded the InstMsiA.exe, InstMsiW.exe and even the latest MSI Installer WindowsInstaller-KB884016-v2-x86.exe from Microsoft.

5. On Windows NT, 2000, or XP, make sure you have administrative privileges. To confirm you have administrative privileges, select Start > Control Panel > Administrative Tools > Computer Management. In the Computer Management dialog, click on System Tools > Local Users and Groups > Users. Right-click on the username and select Properties. In the properties dialog, select the Member Of tab and ensure it states 'Administrator'.
That I am checking for sure
I am using NSIS forum function only and that works fine, moreover I am the admin for the test PCs.

6. Use Microsoft Windows Installer Cleanup utility.
Did tried both with
msicuu.exe and MsiZap.exe

(I have done almost everything other then going directly to MS headoffice.)

Hey guys can you help me out on this?
Thanks in advance.
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Hi n_baua,

If you log the installation you will find which action that's causing the error.
Please give us some more info from the log to be able to proceed.
Answered 08/23/2006 by: AngelD
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity