ERROR 1603 when Loading Adobe CS4

http://www.adobeforums.com/webx/.59b6ebbd

Did you read your way through this:

Posting Virtuoso

Team Colleague

1,730 posts since Aug 2007

Reputation Points: 47

Solved Threads: 145

You can refer Microsoft.com

You may receive this error message if any one of the following conditions is true:

* The folder that you are trying to install the Windows Installer package to is encrypted.
* The drive that contains the folder that you are trying to install the Windows Installer package to is accessed as a substitute drive.
* The SYSTEM account does not have Full Control permissions on the folder that you are trying to install the Windows Installer package to. You notice the error message because the Windows Installer service uses the SYSTEM account to install software.

If you click on the link above they offer a few solutions.

Has anyone else had this problem? How did you resolve it?

francisabey

Junior Poster in Training

85 posts since Aug 2008

Reputation Points: 18

Solved Threads: 6

I am experienceing the same thing you went through, bought CS4 today at foothill college library anxious to install it...so far it has been a nightmare with that error 1604

Hello,

I am a student and recently bought a new windows laptop with Vista on it.

I also have bought the CS4 Adobe Master Suite for my computer.

When installing just TWO programs from the Adobe Creative Suite CS4: Photoshop and InDesign I keep getting "Error 1603" I did a google search for recommended ways to fix this.

I contacted some of my techie friends from school and have spend about 12 hours going round and round trying and still the error comes up.

I have done the following: cleared my registries, emptied my temp files, I have plenty of memory 500GB, I've run adobe clean script, CCleaner, bitcomet, took off all CS3 Adobe products, I've closed all applications, rebooted several times... Turned off my AdAware when installing Turned off McAfee & firewall when installing

I will appreciate any HELP and suggestions to install my Adobe Photoshop to my computer.

Thank you for your time!

Muggs Ballard [email]LavenderBees@aol.com[/email]

mac_sakay

Newbie Poster

1 post since Jan 2009

Reputation Points: 10

Solved Threads: 0

I am having the same problem. I'm using Vista and trying to install Photoshop, InDesign, and Illustrator CS4 and I get the same error on all of them...1603. I had Photoshop CS3 awhile back but I upgraded it to the trial version of CS4. I recently purchased CS4, so I uninstalled the CS3 product.

I have tried everything...my temp folder has been cleared, I have full access on the SYSTEM account, I created a new windows account to install from, I have used both the CS3 and CS4 installer clean-up utilities from Adobe...I have restarted my system in the diagnostic startup mode (from the msconfig window, with all non-microsoft services disabled), I have done a full scan with the disk check utility, and I have defragmented my drive. I have installed and uninstalled and did a number of combination of these things, all without luck. I have manually went into the registry and searched for all Adobe CS4 entries and I have deleted them (of course I backed it up first, though). Windows and all of my drivers are completely up to date. I have plenty of space on my drive to install to. I even copied everything to the hard drive and installed from there. No luck, with anything! Still the same annoying error of 1603! It always fails with Bridge CS4 and the actual program that I am trying to run (be it Photoshop, Illustrator, or InDesign). Every other component installs correctly though.

I have searched all over Google, Microsoft, and Adobe for some sort of different answer, other than the normal temp folder is full, SYSTEM account, blah blah blah. I can't seem to find any other answer!

I did laugh at something on Adobe's website though...it explained the 1603 answer and what to do about it. At the end of the list of things to do, it said you can install the programs on a different machine. Hm. Wow. Good thing I spent hundreds of dollars on these programs, only to have Adobe claim that their program sucks and we should just try it on a different machine because they can't offer us any real support.

Anybody have any solution? Advice? Anything?

Newbie Poster

15 posts since Mar 2009

Reputation Points: 10

Solved Threads: 0

http://kb.adobe.com/selfservice/viewContent.do?externalId=kb403911

What about this link:

It basically puts the blame on Google Desktop and tells you what to do to overcome Error 1603.

Posting Virtuoso

Team Colleague

1,730 posts since Aug 2007

Reputation Points: 47

Solved Threads: 145

Yeah, that was my first result on Google. I don't have Google Desktop and I uninstalled all of my Google products prior to this installation. Thanks for the suggestion though.

Newbie Poster

15 posts since Mar 2009

Reputation Points: 10

Solved Threads: 0

Another thought. Adobe uses InstallShield. I recently had a problem with the Update Manager portion of InstallShield. I discovered that under Vista for this particular piece of software (Systran - not Adobe), the Update Manager (ISUSPM.EXE) had to be run as Administrator.

So, outside chance here - have you tried running the install executable as Administrator? I've no idea whether or not spawned executables inherit the Administrator elevated privilege but that may be something we can go into later.

Let us know.

Posting Virtuoso

Team Colleague

1,730 posts since Aug 2007

Reputation Points: 47

Solved Threads: 145

I actually turned off the UAC while I installed it, just to make sure everything didn't require an administrator access. I am downloading and installing Windows Installer 4.5, which I guess wasn't automatically installed using the Windows Update. I'm going to restart and clean everything again, and I'll see if this helps at all.

Newbie Poster

15 posts since Mar 2009

Reputation Points: 10

Solved Threads: 0

I'm sure this is an Installshield problem although one can't rule out the propagation of an error, say in the Windows Installer package (if it's used by Adobe).

My Systran problem got sorted out very quickly by using the problem form on the Installshield web site. Maybe that's the next route to take after your further tries.

Posting Virtuoso

Team Colleague

1,730 posts since Aug 2007

Reputation Points: 47

Solved Threads: 145

i have this problem too :@

wt3rf5

Newbie Poster

2 posts since Mar 2009

Reputation Points: 10

Solved Threads: 0

i have this problem too :@

Ah! Let me know if you find a solution! I'm completely stuck!

Newbie Poster

15 posts since Mar 2009

Reputation Points: 10

Solved Threads: 0

I'm sure this is an Installshield problem although one can't rule out the propagation of an error, say in the Windows Installer package (if it's used by Adobe).

My Systran problem got sorted out very quickly by using the problem form on the Installshield web site. Maybe that's the next route to take after your further tries.

From my understandings, Adobe uses the Windows Installer service, not InstallShield. However, I did check my InstallShield and made sure everything was fine with it. I also looked on InstallShield's website and followed their suggestions, but it still doesn't work. I'm at a loss.

Newbie Poster

15 posts since Mar 2009

Reputation Points: 10

Solved Threads: 0

Did you see this fascinating thread?
http://www.adobeforums.com/webx/.59b77ab9

Anything of help there (you can ignore the upgrade from CS3 bit)?

Posting Virtuoso

Team Colleague

1,730 posts since Aug 2007

Reputation Points: 47

Solved Threads: 145

Did you see this fascinating thread? http://www.adobeforums.com/webx/.59b77ab9

Anything of help there (you can ignore the upgrade from CS3 bit)?

Success! Yay!

Everything that he posted about what he did was exactly what I had already done...except uninstalling the Bonjour software. I honestly had no idea what Bonjour was, so I always just left it there. But that seemed to do the trick. I also uninstalled all .NET frameworks and reinstalled each of them with a clean copy. I read somewhere that the framework could be damaged, somehow causing the Adobe installers to fail.

Regardless, the installer system reports a 1603 error while the Adobe Support Adviser reported a completely different error...when in reality, it was either Bonjour being installed or a corrupt copy of the .NET framework. Hopefully this helps someone else. Maybe it was just luck this time, though. ;-)

Thank you for your help, that forum saved me!

Newbie Poster

15 posts since Mar 2009

Reputation Points: 10

Solved Threads: 0

Ah! Let me know if you find a solution! I'm completely stuck!

thanks alot. I used AdobeCS3 Cleanup Script, and reinstalled Creative Suite CS4 and seems that the problem has been solved. But it's really weird. Adobe CS4 Cleanup Script didn't work for me. It says "There are no session to delete". :-/

Also after the reinstallation, Dreamweaver is corrupted! Menus texts are not visible and I can see only their codes in place of them. I'm really tired. :yawn:

wt3rf5

Newbie Poster

2 posts since Mar 2009

Reputation Points: 10

Solved Threads: 0

Did you see this fascinating thread? http://www.adobeforums.com/webx/.59b77ab9

Anything of help there (you can ignore the upgrade from CS3 bit)?

-----------------------------------------

Can`t find this thread any more.

------------------------------thanks alot. I used Adobe CS3 Cleanup Script, and reinstalled Creative Suite CS4 and seems that the problem has been solved. But it's really weird. Adobe CS4 Cleanup Script didn't work for me. It says "There are no session to delete".

Same thing here.

posjed

Newbie Poster

1 post since Aug 2009

Reputation Points: 10

Solved Threads: 0

Did you ever get this sorted out? I'm fighting it now...

I actually turned off the UAC while I installed it, just to make sure everything didn't require an administrator access. I am downloading and installing Windows Installer 4.5, which I guess wasn't automatically installed using the Windows Update. I'm going to restart and clean everything again, and I'll see if this helps at all.

HeatherInIowa

Newbie Poster

1 post since Oct 2009

Reputation Points: 10

Solved Threads: 0

The main point about this thread (which I can't find any more either, even with a crafty search) is that be uninstalling BONJOUR, the Error 1603 went away. It looks like they purged stuff pre October 2008.

How stupid.

Posting Virtuoso

Team Colleague

1,730 posts since Aug 2007

Reputation Points: 47

Solved Threads: 145