Well, maybe not. 1st things first, what do those "close" to this error say about 1603? "Well, we know he grew up in a decent neighborhood. https://service.mcafee.com/FAQDocument.aspx?id=TS101331 0 Login to vote ActionsLogin or register to post comments SymNewComer Understanding Error 1603: Fatal Error During Installation - Comment:14 Oct 2014 : Link Hi All, I got the 1603 Learn More Ghost Solution Suite 3.0 - "How-to" Videos We have created several "How To" videos and posted links on this page. He was quickly becoming the loner that we know today. "He's probably the hardest working error code out there" says Nils Sille, a Sys Admin and part-time error code bounty hunter. More about the author
please 0 Login to vote ActionsLogin or register to post comments Feld Spar Understanding Error 1603: Fatal Error During Installation - Comment:02 Mar 2014 : Link I followed the steps in You can read more about this parsing tool (called wilogutl.exe) by clicking here. MSI (c) (D8:44) [20:23:41:794]: Doing action: Fatal_Error Action 20:23:41: Fatal_Error. Found three basic reasons of Error 1603 mentioned here... https://blogs.msdn.microsoft.com/astebner/2005/08/01/how-to-locate-the-cause-of-error-code-1603-in-a-verbose-msi-log-file/
Depending on which action is failing, I will proceed to more detailed debugging from here I find that the biggest hurdle to debugging a failed setup is often zeroing in on Read on to learn how to sidestep this speed bump. The machine has Office 2003, Visual Studio.NET and some MSDNs installed.
In the other 3 of the log files, I see an error in the ServiceModelReg.exe custom action. CMDLINE: C:WINDOWSMicrosoft.NETFrameworkv1.0.3705RegAsm.exe C:WINDOWSMicrosoft.NETFrameworkv1.0.3705System.Data.dll
MSI (s) (2C!70) [17:39:05:999]: Closing MSIHANDLE (42) of type 790531 for thread 2416
MSI (s) (2C!70) [17:39:06:078]: Closing MSIHANDLE (41) of type 790531 for thread 2416Reply Aaron Stebner says: September 9, 2008 at 7:03 pm Hi Melamason - You sent me some log files via email, and in one of them, I see the 1402 access Exit Code 1603 Sccm Impossible d’ouvrir la clé HKEY_LOCAL_MACHINESoftwareClasses.xpsPersistentHandler.
Action ended 20:23:46: INSTALL. Msi Error Codes hr: 0x800b0100
2009-07-29 03:49:48, Error CBS Pkgmgr: Failed installing selectable updates for: Windows Foundation, hr: 0x800b0100
2009-07-29 03:49:48, Info The specific temporary folders for a machine can be determined by accessing the DOS prompt and typing set. this page MSI returned error code 1603
[01/21/09,17:39:54] Microsoft .NET Framework 3.0SP1 x86:  Error code 1603 for this component means "Erreur irrécupérable lors de l'installation." ( Traduction "Fatal Error during the installation")
The following is the probable list of known causes for this error to occur: Short file name creation is disabled on the target machine. Error 1603 Windows 7 Forget the sensationalism. There is a problem with this Windows Installer package. MSI returned error code 1603
[01/21/09,19:19:28] WapUI:  DepCheck indicates Microsoft .NET Framework 3.0 SP2 x86 is not installed.
[01/21/09,19:31:05] Microsoft .NET Framework 3.0 SP2 x86:  Error: Installation failed for
Restart the computer. In this case, the log file named %temp%dd_WF_3.0_x86retMSI*.txt should contain the exact error information for this failure. Installation Success Or Error Status 1603 Windows 7 His given name is: ERROR_INSTALL_FAILURE. How To Fix Error 1603 It is also possible that this will only fail during setup.
Do i have to go through the OptionalFeatures.exe?
P.S. Can you try to re-run CheckSUR and see if it shows any additional errors and try to work around those as well?