נסה את ההסבר בקישור לאיתור.

http://www.msigeek.com/715/how-to-troubleshoot-the-error-1603-fatal-error-during-installation

Step 1: Generate a verbose log file named msi*.log in the %temp% directory the next time the setup package is executed. (Click here to know more ways to generate log)

msiexec /i <msipath>setup.msi /l*v c:\temp\msi.log

Step 2: Open the verbose log in a text editor such as notepad and search for the string “return value 3″. In nearly all cases, this will take us to the section in the verbose log that lists the action that failed that initially caused setup to rollback.

Step 3: Review the contents of the log file immediately above the “return value 3″ string to determine which custom action or standard action failed. Depending on which action is failing, We will need to proceed to more detailed debugging from here.

One can find that the biggest hurdle to debugging a failed setup is often zeroing in on which part of the setup is actually failing, and this trick of searching for “return value 3″ ends up helping speed this process up in nearly all cases. Of course, it does not work in 100% of scenarios.

You can find some ways of troubleshooting the logs here –

http://www.msigeek.com/261/identifying-installation-failure-through-cas-using-msi-logs

http://www.msigeek.com/257/interpreting-windows-installer-logs

את החלק הזה לא ממש הבנתי איך לעשות

עשיתי חיפוש בגוגל להסברים אבל הוא לא מובן כל כך