Participant

Question

Photoshop CS6 configuration error 1

Forum|Forum|13 years ago
June 26, 2012
4 replies
157038 views

I'm on windows 7 64 bits and I have installed both 32 and 64 bits versions of Photoshop CS6 (trial). When I try to run the 64 bit version I get a configuration error (error 1) that tells me to uninstall and reinstall Photoshop. But after several reinstallations, I still get the same message.

Photoshop 32 bits works just fine, same for Adobe Bridge 32 and 64 bit so why is Photoshop 64bits not running ?

I tried to install it on my SSD where my OS is and also on my other hard drive (where the default location of program files is) but it doesn't change anything.

Also my computer is a month old so I didn't have older version of Photoshop installed prior to this.

Any solution ?

This topic has been closed for replies.

K

keng.suppanat@gmail.com

Participant

i have change my windows 7 (64 Bit) to windows 10 (64bit)

and i run photoshop cs6 but it show error 16

now it change to error 1

A

Alski7

Participant

Had the same problem here, and this thread clued me into the cause enough to come up with a slightly hacky but working solution:

I have 1 SSD and 3 HDDs, Windows 7 installed on C: [SSD] Photoshop installed on F: [HDD], Error 1 on launching Photoshop.

- Install Photoshop to a drive of your choice.

- Copy the entire contents of "C:\Program Files (x86)\Common Files" from your SSD/Windows drive (normally C:) to the same location on the drive on which Photoshop is installed, in my case F, so to "F:\Program Files (x86)\Common Files"

- Run Photoshop. Volla.

-You may wish to try only copying ":\Program Files (x86)\Common Files\ADOBE" but this didn't work for me, Photoshop must store some files outside the Adobe folder, copying the entire Common Files folder however worked a treat. Be careful if prompted to overwrite files though, on my machine "F:\Program Files (x86)\Common Files" did not exist, your system may be different.

Despite what Mr Carboni thinks, installing programs on different drives and partitions is older than the floppy disk, and >95% of the time presents no problem. The issue here is a bug within Photoshop where either:

- Photoshop's *installer* is paying attention to the windows registry keys at [Computer\HKEY_Local_mechine\Software\Microsoft\Windows\Currentversion] (which is the key that defines Program Files, X86 Program files, and Common Files locations) but Photoshop itself is ignoring that key, or more likely:

-Vice versa - that the Installer is ignoring that registry key defining file locations and so photoshop is looking for config files in the wrong place.

You can test this by editing the keys at that location from X: to C:, photoshop will start without haveing to copy any files as discribed above - HOWEVER - Do not edit the regestry if you don't know what your doing, and be aware that even if you do, changeing those keys will most likey break many other applications untill the keys are reset to their prior settings.

This should probably be bug reported but seeing as how from what I've heard this bug has been around since at least CS2 I'm not sure I have any faith it'll get fixed.

Noel Carboni

Legend

Alski7 wrote:
Despite what Mr Carboni thinks, installing programs on different drives and partitions is older than the floppy disk, and >95% of the time presents no problem.

I'm not disputing what you say at all. It's that remaining 5% that I'm talking about!

This time you found a way to further complicate things in order to work around a Photoshop bug. That no doubt took you time and effort, and who knows, it may lead to other problems down the line. And it won't work around a bug with another app.

All I'm saying is that if you assume applications are going to have these kinds of problems - and they do because not all programmers know or follow all the "rules" - you'll be better off in the long run, and you'll get better performance overall to boot. If I didn't actually DO these things myself I certainly wouldn't feel comfortable in commenting. But I do, and it works.

In no way am I forgiving Adobe for not properly coding their software... All I'm saying is that If you set yourself up for a greater likelihood of potential failure, when you achieve it part of the responsibility is clearly yours.

-Noel

A

Alski7

Participant

In principle I agree, though I also think the responsibility lies with the programmers to either follow Operating System conventions such as checking the default folder locations and obeying, or (as a lot of installers do anyway) ignoring them completely provided the location is possible, not a half & half botch job that will always lead to a failed installation.

In an ideal world, we'd all have a single SSD large enough for all our needs, but right now I'm running a system with ~6TB, that would be about £10,000 worth in 1TB SSDs, but say I'd be happy with just 512GB for Windows 7 and installed programs, that's still more than 5x the cost for 1/2 the storage, and I don't need the added performance and can't justify the cost of it, until SSD catches up in price and density such a disk configuration (which has always been popular) is only going to become more common and it shouldn't be on the user to confine themselves to very narrow system configurations, which is pretty much the antithesis of PCs as a concept.

Also: bare in mind the cause of this is not that we're running an OS and Applications split between two disks - the problem is purely a coding issue, had I long ago decided when I installed windows not to change the default Program Files drive, but instead manually changed the path on every single program installer I ever ran, I would still have my Windows install and my program files on separate drives and all (including Photoshop) would run flawlessly as now - the issue is that a programming error on abodes part is not making proper sense of certain windows registry keys that are different from a typical install in order to save a few keystrokes every time I install something

Noel Carboni

Legend

What exceptional things have you done to relocate stuff that's normally expected to be on the system drive off the too-small SSD you bought? Photoshop is not good with that kind of activity.

-Noel

C

Crimson_PandoraAuthor

Participant

I don't remember exactly, but I copied the users and program files folders to the other drive and edited the registry accordingly. And until now, I did not have any problem installing games or softwares…

Is there any way to know if there was an error during the installation ?

B

Byoshimura

Participant

I have this same issue, where I have a SSD for system and set all the Adobe stuff to install on a HDD. I can launch the 32bit version of PS but not the 64bit version.

The whole changing user file locations and updating system setting is a big pain in the but, most programs shortcuts end up broken because of this. I wish there was a more trouble free solution of running the OS off a fast but small SSD, while not breaking things by moving the user files elsewhere.

A

Anonymous

When you install do you accept the default locations, or do you move some files after installation to "make it more tidy?".

Have you tried to rest preferences?

C

Crimson_PandoraAuthor

Participant

At the first installation I changed the default location, but seeing that it wasn't working I installed it at the default location and it still didn't work. I didn't move any file after installation either.

I didn't reset preferences because I didn't have photoshop before that. But each time I uninstalled photoshop to reinstall it later I did check the "delete preferences" box just in case.

A

Anonymous

Since you moved some files the uninstall might not get them. Would suggest you uninstall and run Adobe Script Cleaner to get missed pieces. Then re-install.

To reset prefrences to default start PS and IMMEDIATELY hold down ctrl + alt + shift keys. Should get reset window.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded