Participating Frequently

Question

Photoshop CS 5 crashes after updating and then using File --> Automate --> Batch

Forum|Forum|14 years ago
June 16, 2011
15 replies
29786 views

I am running Photoshop CS5 (build 12.0.4 x32) on my XP 32-bit machine and have done so without major problems until about a week ago.

Then all of a sudden when accessing File --> Automate --> Batch the program crashes and I have to force it shutting down manually after which I can restart Photoshop. When trying to access the batch command hereafter the same crash reappears rendering batch commands useless.

I thought about posting here but then decided to reinstall Photoshop again. This enables the fully working software including batch commands once again. However after a short while the update software asks to download and install some patches for all programs. After doing so the same problem happens again in regards to the batch command. Photoshop crashes when accessing it and won't work at all.

I now repeated this procedure twice and have no idea what to do about it.

Is there anybody that has had this experience or knows about a solution?

Do I have to contact Adobe with an error report?

Any help and comment is welcome and mostly appreciated.

This topic has been closed for replies.

A

Anonymous

Latest Epson response goes something like this. They have heard from Adobe and have been told by Adobe it's Epson's fault and are not going to do anything about it. Epson admits it might be their fault but have no plans to update drivers. So, basically all us consumers are being told to piss in the wind and just live with it.

Hudechrome

Known Participant

Yep. Just like my 3200 update...NOT!

A

Anonymous

Another issue has cropped up that is sort of related to this. Noel Carboni will be familiar with this since I've seen his posts about this in another forum. Explorer in Win 7 is locking files. This is giving one of my Photoshop plugins problems saveing files and problems with Capture One moving files.

This gives more credibility to Adobe that this is the scanner manufactures problem. This new problem is a Microsoft problem that they have had plenty of time to fix.

We all need to keep up the pressure on the scanner makers. And Microsoft!!!!!!!!!!

Noel Carboni

Legend

That problem, at least, may have some reasonable workarounds. I never see an issue with Explorer interfering with my file access, though I'd be hard-pressed to say which of the multiple system tweaks I've made is helping with it... Could be because I've disabled indexing, or that I've turned off the generation of Thumbs.db files, or one of several other NTFS tuning tweaks I've done, or even that I don't use UAC.

I'll be happy to describe these tweaks one by one if you'd like, and you can try to see if they work around the problems for you. Might be a good subject for a separate thread...

-Noel

A

Anonymous

I pointed this issue out just to show that Adobe is probably correct. Bugs in other programs cause problems in Photoshop, it's not their fault.

I think, in my mind anyway, this shows that this scanning problem is the manufactures fault and they need to take responsibility for fixing it. We need to keep the pressure up. The Epson rep I've been communicating with seems to be trying to get something done where as it seems the Euro Epson support has washed their hands of it. I've questioned my guy about the different stances between continents. Whether Japan listens is another issue.

The file problem would be good for another thread. I tried the Registry edit without luck. I have Home Premium so am limited as to what I can do according to the"Windows forum". I'm using a plugin that has an "action" that saves both a jpg and or tiff along with a PSD with one click. The file locking issue stalls the "action". It also keeps Capture One from moving files between folders. Extreme headache for me. Also, UAC is turned off since it interferes with my Monitor Calibration software. I'll try turning off indexing.

I'll post about this in that other thread on Microsoft.

Gixxxa75

Inspiring

I disabled my "twain plug in" a couple of weeks ago now to get the batch command to work, and to be honest I'm not really missing the functionality of being able to scan directly into the photoshop enviroment at all. The reason for this is that the Scanwizard pro software that came with my Microtek scanner has a little check box at the bottom which gives me the option to open the scanned file with the program of my choice automatically. So all Im losing is a bit of space on my hard drive from saving a tiff aswell as the psd file.

I know this doesnt solve anything if your existing scanner doesnt have this feature, and I still feel Adobe should fix the problem, as the conflict is causing

a very usefull feature of Photoshop to malfunction.But if the twain plug in is near the end of its life and is becoming too difficult to intergrate reliably ,then maybe this method, a standalone scanning program that works outside of photoshop and then opens the scan up in photoshop after it is saved is the way to go.

Hudechrome

Known Participant

That works so long as either the alternative has exactly the same scanning software or the substitute does an equal or better job.

All this is subjective, I know.

A

Anonymous

Here is Epson's response along with my reply. We consumers need to make as much noise with as many manufactures as we can or nothing is going to be done about this.

"If the scanner drivers work in old versions of CS without any issues, then it is something Adobe has changed in their program. As you have pointed out, it is not just Epson drivers that are having the same issue.

There are no plans for updating the driver at this time. Usually, drivers are only updated when a new operating system is released.

Best Regards,

Victor S.

Epson America, Inc."

"It is the new update from Adobe which I already pointed out. They are claiming that the update is making existing driver problems show up more often.

Adobe is sticking to their story that it is the manufactures fualt and not their problem. It is like putting a cheap tire on a car that can only go sixty miles an hour and it will be fine. Put that same tire on a Ferrari and go two hundred miles an hour and it will blow out.

If this is the first you have heard of this issue you are going to here a lot more. If what Adobe says is true things are only going to get worse. There are going to be a lot of angry consumers.

Chris Cox

Legend

Some low level support person at Epson is applying bad logic AND failing to read what they were told by Epson corporate (ie: they have bugs).

I'll follow up with the Epson driver managers, again.

What we really need is an open hardware spec for scanners so someone OTHER than the manufacturer can write drivers.

Hudechrome

Known Participant

"What we really need is an open hardware spec for scanners so someone OTHER than the manufacturer can write drivers."

Amen.

And they do NOT write new OS drivers for all their past scanners, even though they are quite capable producing results comparable in basic quality to the more recent versions. (3200 scanner).

A

Anonymous

Have you ever noticed how many weird problems you have when Adobe

has a new version??? I've been

using photoshop for years and after a couple of upgrades figured out it only happens when

there is a new upgrade.

I complained about this when CS5 came out and one of the Adobe people admitted their downloads are designed to make your ps run poorly during this time. I guess they think they are clever doing this with EVERY upgrade, but I have to say, I've almost had it with Adobe and their dishonest business practices. I am NOT going to rush and buy the upgrad because the program has stopped being reliabel.

It even effects lightroom. During a photo shoot yesterday my camera was tethered to lightroom. All of a sudden the photos started comming in black and white and the skin looked like they had some kind of disease. I restarted light room, rebooted my computer, and nothing changed. Adobe cost me about an hour of trying to get the photos to come in right so my client could see how her baby photos looked, which never happened, and I finally used the sync feature to make my photos look like they should from the first one that came in untouched. Imagine what my client thought!!!!!

I've been working all day on a product shoot project and things went fairly well until a couple of hours ago. I'm taking the background out of a TON of photos with the quick mask selection tool. All of a suden I can't see the brush size, which has happend before during their latest version crap. Rebooted 3 times, changed from 64 bit to the regular photoshop and nothing helped. So here i sit trying to finish my project with brushes that don't show up. Have you ever tried to work on a mask that you can't see the edges of the brush? What should have taken about 30 minutes to complete a photo is taking over an hour. Add that up with the 30 photos I have left to do. At this rate I'll still be sitting here trying to meet my deadline Sunday night with NO sleep and I'm sure there will be additional problems to deal with. Other things have gone wrong today but I'm so mad I can't think of what they were. But you can bet if your having problems you don't usually have with adobe products, you can thank them for what they send in their updates.

Adobe has no consideration for their loyal customers, evidently, or they wouldn 't do this to us PROFESSIONALS. I just don't understand why they would do this to all their users, which most are professionals and have deadlines. I should have kept tract over the years of how much time they have cost me pulling this stunt. And now, THEY WANT ME TO SPEND AT LEAST $199 TO FIX THE PROBLEM????? I don't like people messing with my photography business and that is exactly what Adobe has been doing for years, not to mention the money and time they have cost me because of the problems they SNEAK in with their updates.

THANK YOU ADOBE FOR HAVING SOOOO MUCH RESPECT FOR YOUR LOYAL CUSTOMERS. Talk to you in a few days when I manage to finish my project, that should have been finished this afternoon, and you are so happy to undermine! What a disappointment! How dare you use business practices like this. Adobe owes everyone a huge appology for all the stress and time they've caused their customers, not just me.

Noel Carboni

Legend

BCastelloe wrote:
...A scathing post including unfounded accusations...

Angry much, BCastelloe? That was pretty extreme.

Maybe things get screwed up because everyone and their brother tacks things onto Photoshop, in a bunch of ways they shouldn't. It's also pretty clear many 3rd party developers apparently debug their software into existence rather that doing good design.

Or maybe it's because you're trying to run a professional business using toys - by that I mean a cheap computer and video card with video drivers primarily designed to run video games. Even a computer with today's "top of the line" components costs only a few thousand dollars. Time was when businesses would only consider basing their livelihood on computers costing millions and manned by a staff of on-site support personnel.

And, let's not forget that the core of Photoshop dates back decades now. That's no excuse for poor performance, but it does bring to mind a WHOLE BUNCH of challenges the Adobe engineers need to overcome every time they make a new version. Imagine trying to make a new masterpiece out of a painting that has been completed 11 times before, instead of on a blank canvas, and you have to keep all the people who have ever liked the painting happy with the new one.

Philosophizing aside, it sounds like you have developed some specific system problems. If you'd like to try to get to the bottom of them (e.g., the missing cursor issue), please create a new post. I and others will be happy, I'm sure, to help you get to the point where your Photoshop works as well as ours.

-Noel

A

Anonymous

Yes it was extreme. I've been using photoshop for about 10 years and have

to go through this every upgrade. They've admitted to doing it. It's just

not something they should do to their customers and I want them to stop

doing it.

Barbara Ann Castelloe

www.barbaraanns.com

A

Anonymous

I should clarify that last post. it should read "scanners that work with the 12.0.4 update". I've never had a problem with any scanner until now either.

It's been suggested to uninstall the update. If the manufactures refuse to fix things does that mean we never apply any future updates or upgrade when CS6 comes out?

Noel Carboni

Legend

Ricardo1283 wrote:
It's been suggested to uninstall the update. If the manufactures refuse to fix things does that mean we never apply any future updates or upgrade when CS6 comes out?

That would be a logical conclusion, yes, if you make the assumption that Adobe isn't going to work with the scanner makers and get this worked out. But it is an obviously temporary measure.

Remember: "Doc! It hurts when I do this!". "Then don't DO THAT!"

Implied is: "Wait for a better update."

Somehow I suspect all the parties making software really DO want it all to work again and might be working on fixes behind the scenes.

-Noel

A

Anonymous

Thanks,

If they are working on it would be nice for all involved to post something on their websites letting consumers know.

It would let us know to just get back to work and wait. Manufactures and software companies wouldn't have to wast time answering a ton of inquires.

A

Anonymous

Lets try a different approach. Does anyone know of a

scanner - driver combination that does work with CS5?

Hudechrome

Known Participant

So far as I know, the Epson V700 does. I haven't used it myself, but all the Epsons I have used never had a driver problem with Photoshop. My 3200 does, but that's because Epson refuses to update it to the 64 bit OS. I do use it in CS5 by booting to XP. Works just fine.

M

MogDaaAuthor

Participating Frequently

Photoshop CS5 (build 12.0.4 x32) XP 32-bit machine - Epson GT-15000 scanner (latest driver for download from 2007)

Photoshop crashes at batch command use.

T

The_Digitiser

Inspiring

Is there a way you can roll back to 12.0.3 to see if it works okay?

Gixxxa75

Inspiring

Well He's right, it is the twain plug in.

I found the twain plug in at C:\Program Files\Adobe\Adobe Photoshop CS5\Plug-Ins\Import-Export\, then I put a "~" in front of the Twain_32.8BA file so it becomes ~Twain_32.8BA to disable it. Now I have batch processing back. I think the Im going to create a short cut to this file on my desktop and just edit the "~" in and out as needed depending what Im doing.

Full instructions here http://kb2.adobe.com/cps/408/kb408849.html

Chris Cox

Legend

No, as already discussed here: the problem is not in the TWAIN plugin.

The problem is in the TWAIN driver (third party code). Disabling the Photoshop TWAIN plugin just prevents Photoshop from calling the TWAIN drivers.

If the driver has a bug with batch, then it has a bug regardless.

That TWAIN driver will not work reliably until it is fixed.

Noel Carboni

Legend

One thing anyone here who is unable to use 12.0.4 and whose scanner worked with 12.0.3 could consider doing is this:

Uninstall Photoshop.
Reinstall 12.0.0.
Then update to 12.0.3 manually (and avoid further updates).

Yeah, I dislike not keeping up with the latest patch too, but if you're in this situation ask yourself this: Is there anything specific that you really need from Photoshop 12.0.4?

-Noel

Show more replies

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