Member Avatar for OSUjjj444

Presently I am trying to download itunes from Apple on to my Dell Laptop (with Windows XP). I have ran into many problems that have caused my download and instillation to fail.

One of the primary problems is that during the installing an error message pops-up that tells me there is a fatal error in the Windows InstallShiled (error 1603).

How should I fill this error in the InstallShield?

  • 5 Contributors
  • 5 Replies
  • 269 Views
  • 9 Months Discussion Span
  • Latest Post Latest Post by DjLizard

Dani AI

Generated

Error 1603 is a generic InstallShield/MSI “fatal error” — the log is the only reliable way to know why the installer failed. Several replies here point to useful ideas: flagged partial installs, noted service/COM-related blockers, and others linked InstallShield/iTunes notes. If those steps have already been tried, the short diagnostic-first workflow below is intended for a Windows XP–era MSI/InstallShield installer like the iTunes packages discussed in this thread.

Start with quick checks: reboot to clear pending file-renames, confirm the system drive has free space, stop any running Apple/iTunes processes, and disable third‑party antivirus/real‑time scanners while troubleshooting. Run the installer with full administrator rights (right‑click -> Run as...) rather than double-clicking from a limited account.

Re-register Windows Installer and capture a verbose install log to see the real error:

msiexec /unregister
msiexec /regserver

msiexec /i "C:\path\to\iTunes.msi" /l*v "C:\Temp\iTunesInstall.log"

Open the generated log and search for “Return value 3”; read the lines immediately above that entry — they typically name the actual cause (access denied, file in use, locked registry key, etc.). Also check Event Viewer (Start -> Run -> eventvwr.msc -> Application log) for MsiInstaller error entries at the time of failure.

If the log shows access problems, verify permissions on %TEMP% and C:\Windows\Temp (Administrators and SYSTEM should have Full Control — on XP disable Simple File Sharing to see the Security tab). If file-in-use is indicated, perform a clean boot via msconfig (hide Microsoft services, disable remaining services/startups) and retry. Common root causes are locked files, insufficient privileges, pending reboot, antivirus interference, or a corrupted installer cache — the verbose log will point to which.

Collect the exact log lines around the failure (the “Return value 3” block and any preceding “error” lines) for precise diagnosis. Avoid unverified “fix” executables from unknown sites; prefer logs-first troubleshooting.

Recommended Answers

All 5 Replies

Member Avatar for caperjack

check this OUT

Member Avatar for hawkida

Presently I am trying to download itunes from Apple on to my Dell Laptop (with Windows XP). I have ran into many problems that have caused my download and instillation to fail.

One of the primary problems is that during the installing an error message pops-up that tells me there is a fatal error in the Windows InstallShiled (error 1603).

How should I fill this error in the InstallShield?

I have a fix listed here:

Member Avatar for flubberz

Presently I am trying to download itunes from Apple on to my Dell Laptop (with Windows XP). I have ran into many problems that have caused my download and instillation to fail.

One of the primary problems is that during the installing an error message pops-up that tells me there is a fatal error in the Windows InstallShiled (error 1603).

How should I fill this error in the InstallShield?

Hey there,

I had the same prob AND tried many things. The only thing which worked is by installing windows installer cleanup utility and removing the product you are trying to install. In your case ITUNES. That's it. now u can reinstall the product.

tc
flubber

Member Avatar for flubberz

You can download windows install cleanup utility from

take care

Member Avatar for DjLizard

Another issue that most people overlook is with COM+.

Start > Run > services.msc
See if "DCOM Server Process Launcher" is Started and set to Automatic. If not, set them that way. If it won't start, then run my program, and checkmark everything in box #5 and hit GO (this will re-register the DLLs necessary for DCOM SPL, among other things). Then try to start DCOM Server Process Launcher again.

Also make sure that COM+ Event System is not disabled. Start it and set it to Manualif it is not. COM+ System Application should also be set to Manual.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.